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

Internal congestion separated AWS's control network from its data network in December 2021 — a polite way of saying the dashboard that tells you the dashboard is broken was also broken, and you found out about the outage from Twitter, which was also on AWS, which is a sentence that should never have been possible. API errors, stretched latencies, monitoring reporting on itself like a doctor who has fainted mid-diagnosis. The canonical illustration of why "watch us-east-1 from us-east-1" is not a monitoring strategy — it's a coincidence generator wearing a pager. Three flavours at once: outright 500s, requests that succeed after eight seconds of silent contemplation, and the occasional normal response to keep you guessing. Your client gets to decide which of three parallel universes each request belongs to. Good luck.

Source: AWS post-event summaries, December 2021 · 2021-12-07

Replay it

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

// 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:500 Headers:map[] Body:{"message":"Internal error"} Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}} {Weight:35 Signature:{Status:200 Headers:map[] Body: Corrupt: Delay:0x69e720af2ba0 Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}} {Weight:20 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-003 — Elevated latency + partial 5xx (AWS us-east-1, Nov 2020) FD-2026-090 — Backbone congestion black hole (Cloudflare, Jul 2020) 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)