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

An intrusion forced Sony to take PSN offline, and it stayed offline for twenty-three days — not a blip, a full billing cycle. Seventy- seven million accounts' worth of personal data walked out the door while users stared at a maintenance page that said, in effect, "technical difficulties, back soon" for three and a half weeks. "Soon" did a lot of work in that sentence. The signature is a polite 503 with a maintenance HTML body — the calmest possible face over a catastrophe, which is exactly how real extended outages present. No error details, no ETA, no admission that "soon" means "we're rebuilding the entire trust model". Clients that retry maintenance pages on a fixed schedule survive fine and learn nothing. Clients that distinguish "transient fault" from "the service has entered a period of reflection" and degrade gracefully are the ones worth having. Twenty-three days is a long time to keep a retry loop warm.

Source: Sony — PlayStation Network outage official statement, April 2011 · 2011-04-20

Replay it

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

// response appears here

Signature

{Status:503 Headers:map[Retry-After:3600] Body:<html><body><h1>Maintenance</h1><p>We are currently performing maintenance. Thank you for your patience.</p></body></html> 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-050 — 420 Enhance Your Calm (Twitter API v1.1) 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)