← registry

FD-2026-017 Connection accepted, never replies

latency severe timeouthang

Anatomy

The TCP handshake completes and then silence — no response, no RST, nothing. The purest test of whether a client has a real read/idle timeout versus only a connect timeout. Capped server-side at 60s.

Replay it

curl -i https://faultydata.com/r/FD-2026-017
// response appears here

Signature

{Status:0 Headers:map[] Body: Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:true Phases:[]}