What this tests
retry-logicsemantics
Point your client at this specimen and find out — before prod does — whether it backs off, retries, and knows when to stop.
Anatomy
GitHub's secondary rate limit is a 403, not a 429 — the API equivalent of being ejected through the kitchen door while the front of house insists nothing happened. A Retry-After that sometimes shows up, sometimes lies, and a body that politely declines to explain what you did wrong. It's a restraining order written by a lawyer with a sense of humour. "Abuse detection" is doing the judging, and the definition of abuse is entirely theirs — parallel requests, enthusiastic polling, scrapers doing scraper things. Your client did nothing wrong. It merely did nothing wrong at scale, which is the same thing. Code that only handles 429 sails straight past this, files it under "permissions problem", and pages someone at 4am who will stare at the response like a man reading a suicide note written in his own handwriting. The docs technically mentioned it. On a page nobody finished reading.
Replay it
curl -i https://faultydata.com/r/FD-2026-004
// response appears hereSignature
{Status:403 Headers:map[Retry-After:60 X-RateLimit-Remaining:0] Body:{"message":"You have exceeded a secondary rate limit. Please wait a few minutes before you try again.","documentation_url":"https://docs.github.com/en/rest/overview/resources-in-the-rest-api#secondary-rate-limits"} Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}
Keep digging
FD-2026-050 — 420 Enhance Your Calm (Twitter API v1.1) 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)