cloudflare/pingora

A library for building fast, reliable and evolvable network services.

Owned by Cloudflare

View on GitHub ↗Jump to charts ↓

cloudflare/pingora has 27k+ stars and 1.5k+ forks on GitHub, is written in Rust, and was last pushed on Oct 17, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 48 minutes ago
Added to GitGenius on February 28th, 2026
Created on May 5th, 2023
Open Issues & Pull Requests: 315 (+0)
GitHub issues: Enabled
Number of forks: 1,775
Total Stargazers: 27,640 (+1)
Total Subscribers: 190 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.8 days
Mean response time: 38.6 days
90th percentile: 84.1 days
Tracked items: 347

Maintainer activity

5 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

Roughly one issue in three opened in the past year never receives a reply. 98% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "documentation" is answered fastest, typically in about 13 hours, while "Accepted" waits about 4 days. 30% of tracked open issues have had no activity in three months. Only 41% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 182
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 346 days
Stale 30+ days: 134
Stale 90+ days: 119

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 1
Events in 7 days: 3

Top labels

  • enhancement (144)
  • question (76)
  • bug (74)
  • stale (54)
  • Accepted (22)
  • dependencies (22)
  • documentation (22)
  • ergonomics (17)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Pingora is a Rust framework developed and open-sourced by Cloudflare for building fast, reliable, and programmable network services. The framework has been battle-tested in production at Cloudflare, handling more than 40 million Internet requests per second for several years before being released as an open-source project. This production pedigree makes it a mature choice for organizations building performance-critical networking infrastructure.

The core functionality centers on HTTP proxying and load balancing capabilities. Pingora supports HTTP 1 and 2 end-to-end proxying, with TLS termination available through multiple backends including OpenSSL, BoringSSL, s2n-tls, and experimental rustls support. The framework also handles gRPC and WebSocket proxying, making it suitable for diverse protocol requirements. Graceful reload functionality allows updates without dropping connections, and the system provides customizable load balancing and failover strategies to meet specific deployment needs.

The repository is organized as a workspace containing multiple specialized crates. The main Pingora crate serves as the public-facing entry point, while Pingora-core defines the underlying protocols and traits. Pingora-proxy contains the HTTP proxy logic and APIs, with supporting crates handling specific concerns like error types, HTTP headers, SSL extensions for different backends, consistent hashing via the Ketama algorithm, efficient counting for rate limiting, and load balancing extensions. Additional crates provide in-memory caching with cache stampede prevention, timeout management, and the TinyUfo caching algorithm. The project explicitly notes that caching integration remains experimental with volatile APIs.

From a development perspective, the repository maintains active engagement with its community. The project overlaps contributors with several other repositories including github/gh-aw, solo-io/gloo, and longhorn/longhorn, suggesting cross-pollination within the broader systems programming community.

The framework targets developers prioritizing security, performance, and customization. As a memory-safe Rust alternative to C/C++ networking services, it addresses security concerns inherent in systems programming. The asynchronous Rust foundation ensures both speed and reliability, while the highly programmable APIs allow extensive customization for specific use cases. System support focuses on Linux as the tier-one environment, with best-effort Unix compatibility for development purposes. The project maintains a rolling minimum supported Rust version policy of six months, currently at version 1.84, and requires Clang and Perl 5 for building certain crates with external dependencies.