Standings
| # | Client | Overall | transport | wire | retry-logic | Cards |
|---|---|---|---|---|---|---|
| 1 | java okhttp okhttp 4.12.0 |
A+ 95/72 | A 94 | C 77 | A+ 100 | retry-logic transport wire |
| 2 | node fetch undici (bundled) 24.21.0 |
A 93/72 | A 91 | A+ 100 | A+ 100 | retry-logic transport wire |
| 3 | python httpx httpx 0.27.2 |
A 91/72 | B 89 | B 88 | A+ 96 | retry-logic transport wire |
| 4 | go net/http stdlib net/http 0.2.0 |
A 90/72 | B 89 | C 77 | A+ 96 | retry-logic transport wire |
| 5 | node axios axios 1.13.2 |
A 90/72 | B 89 | A+ 100 | A+ 96 | retry-logic transport wire |
| 6 | python aiohttp aiohttp 3.10.11 |
A 90/72 | B 89 | B 88 | A+ 96 | retry-logic transport wire |
| 7 | python requests requests 2.32.5 |
A 90/72 | B 88 | B 88 | A+ 100 | retry-logic transport wire |
| 8 | rust reqwest reqwest blocking 0.12.28 |
B 88/72 | B 88 | B 88 | A+ 96 | retry-logic transport wire |
| 9 | node undici undici 7.10.0 |
B 87/72 | B 84 | B 88 | A+ 96 | retry-logic transport wire |
| 10 | node ky ky 1.8.2 |
B 84/72 | B 83 | B 88 | C 76 | retry-logic transport wire |
| 11 | node got got 14.6.6 |
B 83/72 | B 81 | B 88 | B 83 | retry-logic transport wire |
| 12 | python urllib3 urllib3 2.2.3 |
B 81/72 | C 79 | B 88 | B 80 | retry-logic transport wire |
| 13 | curl builtin 7.76.1 |
F 29/72 | F 13 | D 66 | F 43 | retry-logic transport wire |
Every exhibit, every client
✓ survived · ✗ failed · · not run — hover a cell for the detail; click a suite name above for the full report card.
| specimen | java okhttp | node fetch | python httpx | go net/http | node axios | python aiohttp | python requests | rust reqwest | node undici | node ky | node got | python urllib3 | curl |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| FD-2026-001Stripe-style rate limit | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ | ✗ | ✗ | ✗ |
| FD-2026-002CDN edge degradation (Fastly, June 2021) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| FD-2026-004GitHub secondary rate limit | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-005Token expires mid-session (Entra ID pattern) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-006Total reachability loss (Meta BGP withdrawal, Oct 2021) | ✓ | ✗ | ✓ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✓ | ✗ | ✗ | ✗ |
| FD-2026-007Recovering outage (Slack, Jan 2021) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-008WAF challenge page instead of JSON (Cloudflare pattern) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-009Provider overloaded (OpenAI-style 529) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ | ✗ | ✗ | ✗ |
| FD-2026-010Gateway timeout from the edge (Cloudflare 522 pattern) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-011Truncated JSON body | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-012Malformed JSON (trailing comma) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-016Slow but correct response | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| FD-2026-017Connection accepted, never replies | ✓ | ✗ | ✓ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✓ | ✗ | ✗ | ✗ |
| FD-2026-018Partial body then stall | ✓ | ✗ | ✓ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
| FD-2026-020Infinite redirect loop | ✓ | ✓ | ✗ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ | ✗ | ✓ | ✓ | ✗ |
| FD-2026-021S3 us-east-1 subsystem removal (AWS, Feb 2017) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| FD-2026-023Global 502s from a bad WAF rule (Cloudflare, Jul 2019) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-024Network config rollback storm (Cloudflare, Jun 2022) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| FD-2026-025Edge DNS unreachable (Akamai, Jul 2021) | ✓ | ✗ | ✓ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✓ | ✗ | ✗ | ✗ |
| FD-2026-026Global authentication outage (Google, Dec 2020) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| FD-2026-027Signing-key rollover breaks token validation (Azure AD, Mar 2021) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-028Malformed channel file update (CrowdStrike, Jul 2024) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-029Production database deleted, backups broken (GitLab, Jan 2017) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-030Dependency vanishes from the registry (left-pad, Mar 2016) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-031Multi-week partial outage (Atlassian, Apr 2022) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-032Capacity-collapse 503s (Healthcare.gov launch, Oct 2013) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-033Sudden platform rate limit (Twitter/X API, 2023) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-035Stack trace in the error body | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-038Lying rate-limit headers | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ | ✓ | ✗ |
| FD-2026-041Retry-After as HTTP-date | ✓ | ✓ | ✗ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ | ✓ | ✗ | ✗ |
| FD-2026-043Datacenter literally on fire (OVH, Mar 2021) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| FD-2026-044Three-day outage from a consensus bug (Roblox, Oct 2021) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| FD-2026-045Image pull rate limit (Docker Hub, Nov 2020) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-047Guru Meditation (Varnish cache failure) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-048Origin unreachable (Cloudflare 523) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-049Load balancer gives up waiting (ALB/ELB 504) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-050420 Enhance Your Calm (Twitter API v1.1) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-051I'm a teapot (HTTP 418, HTCPCP/RFC 7168) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-057Drip-fed response body | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| FD-2026-059East-west network partition (GitHub, Oct 2018) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| FD-2026-060Network congestion cascade (Google Cloud, Jun 2019) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| FD-2026-063Queue collapse under demand (Ticketmaster Eras presale, Nov 2022) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| FD-2026-064Corrupted database file grounds aviation (FAA NOTAM, Jan 2023) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-065Indefinite maintenance page (PlayStation Network, Apr 2011) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ | ✗ | ✗ | ✗ |
| FD-2026-066Captive portal interception (HTTP 511) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-067Legally unavailable (HTTP 451, geo-block) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-069Unsolicited 304 to an unconditional request | ✗ | ✓ | ✗ | ✗ | ✓ | ✗ | ✗ | ✗ | ✗ | ✓ | ✗ | ✗ | ✗ |
| FD-2026-070Content-Length lies (body shorter than declared) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| FD-2026-071204 No Content... with content | ✓ | ✓ | ✓ | ✓ | ✗ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| FD-2026-073Retry-After: 0 (storm bait) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-074NUL bytes embedded in JSON | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-075UTF-8 truncated mid-codepoint | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-080HTTP/0.9-style response (body, no status line) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ | ✓ | ✓ | ✓ |
| FD-2026-081Response dies mid-headers | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-082Two responses, one connection (response splitting) | ✗ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-083HTTP 402 Payment Required | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-085Redirect chain that ends in a 404 | ✓ | ✓ | ✗ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-087200 OK, body never arrived | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-088DNS provider drowns in DDoS (Dyn, Oct 2016) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| FD-2026-089Launch-day capacity collapse (Pokémon GO, Jul 2016) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ | ✓ |
| FD-2026-091Control plane loses its buildings (Cloudflare, Nov 2023) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-092Nationwide core-network kill (Rogers, Jul 2022) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| FD-2026-093Routing-table overload blackout (Optus, Nov 2023) | ✓ | ✓ | ✓ | ✗ | ✗ | ✗ | ✓ | ✗ | ✓ | ✓ | ✓ | ✓ | ✓ |
| FD-2026-096The endpoint that never came back (Code Spaces, Jun 2014) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-097Trading halt by infrastructure (Robinhood, Mar 2020) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ | ✗ | ✓ | ✓ |
| FD-2026-098Power surge kills the data centre, recovery kills the airline (British Airways, May 2017) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| FD-2026-099Redirect loop | ✓ | ✓ | ✗ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ | ✗ | ✓ | ✗ | ✗ |
| FD-2026-100Conflicting duplicate Content-Length headers | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| FD-2026-102Rate-limit headers that lie | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ | ✗ | ✗ | ✗ |
| FD-2026-104HTTP 508 Loop Detected | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-105HTTP 520 — the Cloudflare unknown-error junk drawer | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| FD-2026-107Slow response stream (1 byte per second, forever-ish) | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
How this was measured
| what | how |
|---|---|
| runner | fd fd 0.2.0 — docs. One battery per client per suite; the server grades, not the client. |
| endpoint | The direct line faultydata.com:8443, so wire-level exhibits arrive unedited. TLS verified; no proxy in between. |
| deadline | 30s per exhibit. A client still waiting when fd's deadline hits is killed and failed — that is the "no timeout of its own" verdict. |
| client settings | Each adapter uses the library's defaults: whatever timeout, retry, and redirect policy it ships with. Adapters live in leaderboard/clients/ in the repo; copy one and change it to grade your configuration instead. |
| integrity | Batteries are sealed after each run — the report cards linked above are frozen and cannot be edited after the fact. |
| reproduce | leaderboard/run.sh re-runs the whole board; leaderboard/emit.py rebuilds this page's data from the report cards. |