What this tests

timeoutsmonitoring

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 misconfigured router in Atlanta announced routes it had no business announcing, traffic got sucked into a backbone that couldn't hold it, and for twenty-seven minutes Cloudflare — a company whose entire job is being reachable — was not. The postmortem's memorable detail: some of their own status infrastructure lived behind the same congested paths, so for a while even the "we are investigating" page needed investigating. The signature is partial reachability: some requests get through, some get eaten, and the client cannot tell the difference between "the site is down" and "the road to the site is down" — because there isn't one.

Source: Cloudflare blog · 2020-07-17

Replay it

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

// 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:45 Signature:{Status:502 Headers:map[Content-Type:text/html] Body:<html><body>502 Bad Gateway</body></html> Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}} {Weight:30 Signature:{Status:504 Headers:map[] Body:upstream timeout Corrupt: Delay:0x69e720c5d6c0 Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}} {Weight:25 Signature:{Status:200 Headers:map[] Body:{"status":"through — this time"} Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}}]}

Keep digging

FD-2026-003 — Elevated latency + partial 5xx (AWS us-east-1, Nov 2020) FD-2026-022 — AWS console/API errors (us-east-1, Dec 2021) FD-2026-043 — Datacenter literally on fire (OVH, Mar 2021) FD-2026-092 — Nationwide core-network kill (Rogers, Jul 2022) FD-2026-002 — CDN edge degradation (Fastly, June 2021) FD-2026-021 — S3 us-east-1 subsystem removal (AWS, Feb 2017)