What this tests

timeoutsmonitoring

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

A maintenance change on Rogers' core network deleted a routing filter, which cascaded into knocking out a quarter of Canada's internet — phone service, banking, Interac payments, 911 access, the lot — for the better part of a day. The emergency broadcast system worked fine, which was fortunate because nothing else did. The signature is the purest one in the collection: the connection simply dies. No status, no body, no apology. One day the socket is there; the next it has been terminated mid-sentence by a change management process that skipped a checkbox.

Source: Wikipedia · 2022-07-08

Replay it

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

This exhibit breaks the connection itself, so replay it on the direct line (port 8443), where nothing sits between you and the bytes. On the main site the web server in front tidies the wreckage into a polite 502, and the button below will show you exactly that.

// response appears here

Signature

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

Keep digging

FD-2026-003 — Elevated latency + partial 5xx (AWS us-east-1, Nov 2020) FD-2026-022 — AWS console/API errors (us-east-1, Dec 2021) FD-2026-043 — Datacenter literally on fire (OVH, Mar 2021) FD-2026-090 — Backbone congestion black hole (Cloudflare, Jul 2020) FD-2026-002 — CDN edge degradation (Fastly, June 2021) FD-2026-006 — Total reachability loss (Meta BGP withdrawal, Oct 2021)