What this tests
retry-logicparsing
Point your client at this specimen and find out — before prod does — whether it backs off, retries, and knows when to stop.
Anatomy
Provisioned for a fraction of actual load and launched on live television: nearly every request errored or timed out on day one of Healthcare.gov. The canonical "it worked in staging", where staging was six VMs, three optimistic interns, and a load test that was, charitably, aspirational. What the client receives is a bare 503 — no Retry-After, no error schema, no JSON body, not even a branded apology page. Just a door slammed in the face of a hundred-million-person queue. The emptiest possible way of saying no: not even a body to parse, just status and silence. This specimen exists to test your client's behaviour when the server has absolutely nothing to say. Some clients handle it fine. Some clients crash trying to JSON.parse an empty string, which is a bit like fainting because a mime stopped performing.
Source: US HHS / congressional testimony on HealthCare.gov launch · 2013-10-01
Replay it
curl -i https://faultydata.com/r/FD-2026-032
// response appears hereSignature
{Status:503 Headers:map[] Body: Corrupt:empty Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}
Keep digging
FD-2026-001 — Stripe-style rate limit FD-2026-004 — GitHub secondary rate limit FD-2026-005 — Token expires mid-session (Entra ID pattern) FD-2026-009 — Provider overloaded (OpenAI-style 529) FD-2026-010 — Gateway timeout from the edge (Cloudflare 522 pattern) FD-2026-027 — Signing-key rollover breaks token validation (Azure AD, Mar 2021)