What this tests

semanticsretry-logic

Point your client at this specimen and find out — before prod does — whether it interprets status codes and content types correctly, or makes things up.

Anatomy

Twitter API v1.1, in an act of documentation comedy for which they have never been forgiven, rate-limited clients with HTTP 420 — "Enhance Your Calm", a status code borrowed from a joke RFC and deployed in production at one of the largest APIs on Earth. Clients written to switch on 429 got... 420, a number their enum didn't have, and reacted with the full range of outcomes from "fine" to "unhandled status code exception in the retry middleware". It is the single greatest argument that "5xx means retry, 4xx means stop" was always a polite fiction. The vendors will make up status codes. Your client must be ready for a rate limit delivered by the number four hundred and twenty, because someone, somewhere, thought it was funny. They were right, but that's not the point. Enhance your calm. Then check your status-code handling.

Source: Twitter API v1.1 error codes documentation (archived) · 2012-10-26

Replay it

curl -i https://faultydata.com/r/FD-2026-050

// response appears here

Signature

{Status:420 Headers:map[] Body:{"errors":[{"code":88,"message":"Rate limit exceeded"}]} Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}

Keep digging

FD-2026-004 — GitHub secondary rate limit FD-2026-065 — Indefinite maintenance page (PlayStation Network, Apr 2011) FD-2026-063 — Queue collapse under demand (Ticketmaster Eras presale, Nov 2022) FD-2026-098 — Power surge kills the data centre, recovery kills the airline (British Airways, May 2017) FD-2026-001 — Stripe-style rate limit FD-2026-005 — Token expires mid-session (Entra ID pattern)