What this tests
retry-logic
Point your client at this specimen and find out — before prod does — whether it backs off, retries, and knows when to stop.
Anatomy
One morning the API decided everyone was now on a much smaller plan — undocumented limits, vague error bodies, no consistent Retry-After, and a decade of third-party apps discovering their quota had evaporated overnight, like a pub changing its happy hour by simply removing the chairs. Not a bug. A business decision. Your client cannot tell the difference, which is rather the point. The 429 here is hard and curt: RFC 7807 problem-details JSON if you're lucky, nothing useful if you're not. No warning, no grace period, no migration path — the API equivalent of a landlord changing the locks and mailing you the new rate card. Backoff strategies tuned for honest rate limiters — the kind that say "try again in 30" — do nothing here because there is no 30. There is only the limit, unspecified, possibly different tomorrow, a bit like life.
Source: Twitter API changes and rate limiting, early 2023 · 2023-02-02
Replay it
curl -i https://faultydata.com/r/FD-2026-033
// response appears hereSignature
{Status:429 Headers:map[] Body:{"title":"Too Many Requests","detail":"Too Many Requests","type":"about:blank","status":429} Corrupt: 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-027 — Signing-key rollover breaks token validation (Azure AD, Mar 2021) FD-2026-032 — Capacity-collapse 503s (Healthcare.gov launch, Oct 2013)