This is strictly a violation of the TCP specification
Aug 12, 2016Marek Majkowski

Summary
This post details the debugging of a rare 522 error, tracing it back to a subtle issue where an application leaking sockets in the CLOSE_WAIT state on the loopback interface caused connection timeouts for new connections. It highlights how this application-level problem, not a network issue, can lead to symptoms that appear to violate TCP specifications, impacting Cloudflare's edge connectivity.
More from the Data Infrastructure & Analytics trail
- Introducing Cloudflare Basin: an open, serverless data platform, now generally available
- Introducing the Billable Usage API: programmatic cost visibility for Cloudflare
- Announcing the Monetization Gateway: charge for any resource behind Cloudflare via x402
- How we built Cloudflare's data platform and an AI agent on top of it
- Iran's Internet is partially restored, Cloudflare Radar data shows