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
Docker Hub announced pull limits — 100 per six hours for anonymous users — and overnight every CI pipeline on Earth discovered it had an anonymous user. Builds that had pulled the same base image merrily for years began failing at 429 with TOOMANYREQUESTS, and the industry's response, to its credit, was a collective "wait, that costs money?" The signature detail: it's not your code being limited, it's your IP, shared with every CI worker, every teammate's laptop, and quite possibly a thousand other NAT'd strangers you'll never meet. Your budget is a commons. The commons has been grazed bare by somebody else's cron job. Classic tragedy. A flat 429 with the house JSON format. Clients that cache layers or use a pull-through registry dodge it; clients that retry immediately discover the limit resets in hours, not seconds — a Retry-After measured in geological CI time.
Source: Docker — rate limit announcement and documentation · 2020-11-01
Replay it
curl -i https://faultydata.com/r/FD-2026-045
// response appears hereSignature
{Status:429 Headers:map[] Body:{"errors":[{"code":"TOOMANYREQUESTS","message":"You have reached your unauthenticated pull rate limit."}]} 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)