What this tests
timeoutsretry-logic
Point your client at this specimen and find out — before prod does — whether it has a timeout, and whether the timeout has a timeout.
Anatomy
A routine software upgrade at an upstream peer flooded Optus's routers with more BGP route announcements than their safety limits allowed, the routers did the sensible thing and shut down to protect themselves, and ten million Australians woke up to a carrier that had collectively decided to take the day off. Roughly twelve hours for a full recovery. From the client's side it presents as degraded-to-dead: long pauses, intermittent 503s, occasional silence. The network equivalent of a fuse that blows every time you fix it.
Source: Wikipedia · 2023-11-08
Replay it
curl -i https://faultydata.com/r/FD-2026-093
// response appears hereSignature
{Status:0 Headers:map[] Body: Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[{Weight:50 Signature:{Status:503 Headers:map[] Body:upstream overloaded 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:route convergence in progress Corrupt: Delay:0x69e720c5dd10 Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}} {Weight:20 Signature:{Status:0 Headers:map[] Body: Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:true Reset:false Raw: Phases:[]}}]}
Keep digging
FD-2026-060 — Network congestion cascade (Google Cloud, Jun 2019) FD-2026-088 — DNS provider drowns in DDoS (Dyn, Oct 2016) FD-2026-097 — Trading halt by infrastructure (Robinhood, Mar 2020) FD-2026-049 — Load balancer gives up waiting (ALB/ELB 504) FD-2026-002 — CDN edge degradation (Fastly, June 2021) FD-2026-003 — Elevated latency + partial 5xx (AWS us-east-1, Nov 2020)