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 server cheerfully sends 256 bytes of a response it promised would be much larger — Content-Length already committed, mind you, the contract signed in triplicate — then wanders off to do something else, forever. The first chunk arrives. The rest of the body has entered a monastery and taken a vow. This is nastier than never-responds, because it looks like progress. A great many clients time out headers diligently, relax into the body-read phase like a man putting his feet up at the dentist, and then wait with the patience of a saint for bytes that have emigrated. Watch your streaming handlers especially — the ones that read in a loop and check nothing else. They will sit on that socket like a hen on a marble, convinced that with a little more time, something is bound to hatch.

Replay it

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

// response appears here

Signature

{Status:200 Headers:map[] Body: Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:256 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-025 — Edge DNS unreachable (Akamai, Jul 2021) FD-2026-043 — Datacenter literally on fire (OVH, Mar 2021) FD-2026-057 — Drip-fed response body