What this tests

timeoutsloops

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 headers arrive instantly — a crisp 200 OK, a confident Content-Type: application/json — and then the body starts arriving one byte per second. Not stalled. Not dead. Just hydrating at the speed of geological processes, each byte resetting whatever idle timer your client thought would save it. This is the response-side mirror of the Slow JSON Stream attack: research showed that 64 inbound connections dripping request bodies at 1 B/s will flatten PHP, Flask, Rails and Kestrel in minutes — because almost nothing configures a minimum body data rate. Your HTTP client has the same blind spot. Its timeout covers connecting, or the whole response, or headers — but a body that never stops dribbling and never completes sails under all of them while pinning a connection pool slot. The fix nobody writes by default: a minimum-bytes-per-second floor on body reads. If your client survives this exhibit, it has one.

Source: Daniel Alfocea — Slow JSON Stream research · 2026-06-27

Replay it

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

// response appears here

Signature

{Status:200 Headers:map[Content-Type:application/json] Body: Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:0x69e720ccd810 StallAfter:0 Hang:false Reset:false Raw: Phases:[]}

Keep digging

FD-2026-006 — Total reachability loss (Meta BGP withdrawal, Oct 2021) FD-2026-025 — Edge DNS unreachable (Akamai, Jul 2021) FD-2026-043 — Datacenter literally on fire (OVH, Mar 2021) 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