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

Ticketmaster put 3.5 billion requests' worth of demand through a system built for a fraction of it — presale codes plus bots plus actual humans — and the queue, designed to smooth load, collapsed under it. Verified fans queued for hours and got kicked anyway; the general sale was cancelled outright. The failure wasn't the 503s, it was the queue position that kept changing. The client-visible shape: intermittent success behind a wall of "you're in queue" responses — a 200 that means "not yet", a 503 that means "never", and no header or field that reliably distinguishes them. It's a rate limiter wearing a ticket stub. Clients that treat every 200 as success will harvest queue pages and call it data. Clients that check the body's queue state survive. Clients that retry through it are part of the 3.5 billion, which is a statistic and also a moral position.

Source: Ticketmaster statement on Taylor Swift presale (archived); US Senate hearing testimony · 2022-11-15

Replay it

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

// response appears here

Signature

{Status:0 Headers:map[] Body: Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[{Weight:60 Signature:{Status:200 Headers:map[] Body:{"queue":{"position":24732,"wait_seconds":1800,"status":"waiting"},"note":"you are in a queue. your request has not succeeded."} Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}} {Weight:30 Signature:{Status:503 Headers:map[] Body:{"error":"service unavailable","queue":"collapsed"} Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}} {Weight:10 Signature:{Status:200 Headers:map[] Body: Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}}]}

Keep digging

FD-2026-098 — Power surge kills the data centre, recovery kills the airline (British Airways, May 2017) FD-2026-004 — GitHub secondary rate limit FD-2026-050 — 420 Enhance Your Calm (Twitter API v1.1) FD-2026-065 — Indefinite maintenance page (PlayStation Network, Apr 2011) FD-2026-002 — CDN edge degradation (Fastly, June 2021) FD-2026-021 — S3 us-east-1 subsystem removal (AWS, Feb 2017)