TEterabyteoff·Sep 18, 2026
You got me! I keep meaning to do this.
https://github.com/cloudflare/pingora/issues/1014
I have now solved the problem once and for all
In Saving another 100TB of RAMcloudflare
pingora
Rust2023–2026
cloudflare / pingora
pingora
A library for building fast, reliable and evolvable network services.
17Distinct people
18Mentions
0Explicit recommenders
27.9KGitHub stars
What to know before exploring
What it is
A library for building fast, reliable and evolvable network services.
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 11:56:56 AM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year18 dated mentions
Observed mentions: 2023-05-11 21:22:32 UTC to 2026-09-18 21:34:34 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 10 | 3 | 7 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 3 | 0 | 3 |
What Hacker News says
18 sourcesI was curious for the same thing, so I quickly (with an agent) threw support for .rs scripts together on my fork:
https://github.com/tekacs/zeroserve/commit/b33f261615d20d55b...
It does leave me wondering about other runtimes that could be used as the go-between though, because at the point of compiling Rust, an approach like Cloudflare's Pingora (https://github.com/cloudflare/pingora) which I've tried using before... in _theory_ should be a 'nicer' solution - just historically awkward when I've tried using it the way that I'd have liked. Wish it were more library-shaped!
In Zeroserve: A zero-config web server you can script with eBPFPingora looks good https://github.com/cloudflare/pingora
In Nobody likes lag: How to make low-latency dev sandboxesIf one actually looks at the current pingora API, it has limited ability to initialize async components at startup - the current pattern seems to be to lazily initialize on first call. An obvious downside of this is that a service can startup in a broken state. e.g. https://github.com/cloudflare/pingora/issues/169
I can imagine that this could easily lead to less visibility into issues.
In Cloudflare outage on November 18, 2025 post mortemDo people think of CF as a leader in terms of solutions that are "open, collaborative, standardized, and shared across many organizations"? My impression is that their open source work is mostly Cloudflare-specific client libraries and the occasional passion project from their engineers. Quiche may be a counter example, but it's a rare exception.
Examples:
Pingora claims to be battle-tested, but I have a hard time believing that it's to the same level of quality as whatever Cloudflare runs internally. https://github.com/cloudflare/pingora/issues/601
https://blog.cloudflare.com/introducing-oxy/ was not open source.
Small parts of Oxy were open sourced as "foundations" but the repo gives off the impression of a checkbox for someone rather than a serious commitment to building CF's own services on top of it — not "open, collaborative, standa
Read the rest
rdized, and shared across many organizations".
At least in the Cloudflare case, if you look at the postmortem (https://blog.cloudflare.com/resolving-a-request-smuggling-vu...) and the commit that fixed the bug (https://github.com/cloudflare/pingora/commit/fda3317ec822678...), it's significantly more complicated than "they didn't read the RFC", and a conclusion that a diligent engineer would never ever make this kind of mistake does not seem justified.
In HTTP/1.1 must die: the desync endgamehttps://github.com/cloudflare/pingora seems to be focused on providing a library/framework
In Show HN: I built a memory-safe web server in Rust> But the business benefits that it brings aren't coming from Rust. They are coming from the fact that it's a modern architecture.
This is moving the goalposts. Your original post said
> I'm not sure there is enough pain for them to get replaced anytime soon.
Yet, here one of them is, being replaced at a company that powers ~10% of the traffic on the Internet.
But beyond that, your links:
> 1. "Pingora is Not an Nginx Replacement" https://navendu.me/posts/pingora/
Here's what the start of the post actually says:
> Think of Pingora as an engine that can power a car while you have to build the car yourself. Nginx is a complete car you can drive. River is a faster, safer, and an easily customizable car.
The title is being pedantic for effect. It doesn't say what you say it's saying.
> 2. you still put it behind ha-proxy https://github.com/c
Read the rest
loudflare/pingora/issues/132
This is an issue opened by someone on an open source repository. They aren't talking about how Cloudflare itself uses it, but about how they want to use it.
> so for anyone who dislikes the "constant upgrade treadmill", this won't help much.
Similar to above, this is moving the goalposts. Sure, that might be true, but it's unrelated to the original topic.
> But the main advantages of Pingora - which are the reason why CloudFlare is using it now - have nothing to do with Rust.
This is not what Cloudflare themselves would say. They chose Rust for very specific reasons when building Pingora: (repeating the link from above) https://blog.cloudflare.com/how-we-built-pingora-the-proxy-t...
> We chose Rust as the language of the project because it can do what C can do in a memory safe way without compromising performance.
Cloudflare has been a vocal proponent of Rust for years now. Many years ago, they suffered a very serious bug, CloudBleed, that Rust would have prevented. And so they've been using Rust instead of C and C++ for a long time.
They of course would also very much agree that the architecture matters, but that doesn't mean that the implementation language doesn't matter either. If they chose to implement Pingora in, say, Ruby, that wouldn't have accomplished their goals.
That sounds like a great project :) but
1. "Pingora is Not an Nginx Replacement"
https://navendu.me/posts/pingora/
2. you still put it behind ha-proxy
https://github.com/cloudflare/pingora/issues/132
3. https://github.com/cloudflare/pingora says "Pingora keeps a rolling MSRV (minimum supported Rust version) policy of 6 months." so for anyone who dislikes the "constant upgrade treadmill", this won't help much.
So my summary would be that Pingora is a great Rust library which one day might be used for replacing nginx and/or ha-proxy.
But the main advantages of Pingora - which are the reason why CloudFlare is using it now - have nothing to do with Rust. Obviously, a software architecture designed in 2022 can take advantage of modern hardware in a way that an architecture from 2004 cannot. (Yes, nginx is that old). Intel's TBB library brough
Read the rest
t "work-stealing" to C++ around 10 years ago. The other big improvement in Pingora is moving from multi-process to multi-threading pools. Again, C++ had thread pools for years.
So Pingora is probably great and it's written in Rust. But the business benefits that it brings aren't coming from Rust. They are coming from the fact that it's a modern architecture.
What he said is true, AWS uses Rust heavily in some of AWS core systems https://aws.amazon.com/blogs/devops/why-aws-is-the-best-plac....
Some of the open source projects you can find are AWS Firecracker https://github.com/firecracker-microvm/firecracker and Cloudflare Pingora https://github.com/cloudflare/pingora
In I'm funding Ladybird because I can't fund FirefoxPingora Restart Without Downtime
1 points · Open discussionThis is also called a framework:
https://github.com/cloudflare/pingora
Pingora is actually fast and small (it does not require a JS engine). Way faster and smaller than Hono.
If you want something to be really fast: do not use RegExes.
In HonoJS: Small, simple, and ultrafast web framework for the EdgesPingora 0.1.0 – First Public Release
3 points · Open discussionSo it looks like they are intending this more as a framework that you build your own custom proxy on top of for your team/company. So you just extend the conf for your custom filters and then you add the wrapper systemd Service.
I might try wrapping it in an envoy style service as a weekend project and just dockerizing it, seems pretty straightforward.
They have a recommended systemd config: https://github.com/cloudflare/pingora/blob/8797329225018c4d0...
And their conf support: https://github.com/cloudflare/pingora/blob/8797329225018c4d0...
In Cloudflare Makes Pingora Rust Framework Open-SourceIf anyone else was interested this is how you implement filters: https://github.com/cloudflare/pingora/blob/main/docs/user_gu...
Then there’s docs on the request phases here: https://github.com/cloudflare/pingora/blob/main/docs/user_gu...
In Cloudflare Makes Pingora Rust Framework Open-SourceShowing the 15 most recent of 18 sources. Enable JavaScript to search and browse every indexed mention.