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

The response arrives byte by byte, like a ransom note assembled one letter at a time — 1KB of JSON delivered at 128 bytes a second. Not slow in the latency sense; slow in the "the body is still arriving" sense, which is a different and more insidious species of slow. This is the signature of a backend streaming a result it hasn't finished computing, or a proxy buffer that's decided to release the response at a rate it considers reasonable. The headers arrived on time. The body is taking the scenic route. Every byte is correct; the delivery schedule is a hostage negotiation. Clients that read bodies with no overall deadline will sit here for the full eight seconds — which is nothing, until it's eight seconds times ten thousand concurrent requests, at which point it's a connection pool with no connections left and a pager with a fresh battery.

Replay it

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

// response appears here

Signature

{Status:200 Headers:map[] Body: Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:0x69e720bde110 StallAfter:0 Hang:false Reset:false Raw: Phases:[]}

Keep digging

FD-2026-006 — Total reachability loss (Meta BGP withdrawal, Oct 2021) FD-2026-016 — Slow but correct response FD-2026-017 — Connection accepted, never replies FD-2026-018 — Partial body then stall FD-2026-025 — Edge DNS unreachable (Akamai, Jul 2021) FD-2026-043 — Datacenter literally on fire (OVH, Mar 2021)