What this tests

timeouts

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

On the 4th of October 2021, Facebook withdrew its BGP routes and conceptually deleted itself from the internet's map. Six hours. DNS gone, anycast gone, and — according to reports that read like a sitcom pitch — the badge readers on the buildings where you'd go to fix it, gone too. An outage so thorough it ate the repair tools, the repair team, and the repair team's lunch. From a client's chair it doesn't even look like an error. There's no status code for "the destination has been reclassified as rumour". SYN packets drift into the void like prayers to a god who resigned. This specimen accepts your connection and then contemplates that void indefinitely — the closest HTTP gets to "there is no there there". If your client lacks a read timeout it will still be waiting when the sun expands, which, to be fair, is roughly how long six hours felt on Hacker News.

Source: Meta engineering — more details about the October 4 outage · 2021-10-04

Replay it

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

// response appears here

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-025 — Edge DNS unreachable (Akamai, Jul 2021) FD-2026-043 — Datacenter literally on fire (OVH, Mar 2021) FD-2026-107 — Slow response stream (1 byte per second, forever-ish) FD-2026-003 — Elevated latency + partial 5xx (AWS us-east-1, Nov 2020) FD-2026-016 — Slow but correct response FD-2026-017 — Connection accepted, never replies