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

The SBG2 datacenter in Strasbourg caught fire and burned to the ground, taking SBG1 with it — 3.6 million websites offline, backups stored in the same building as the things they backed up, which is a disaster-recovery strategy best described as "optimistic". Rust, cryptocurrency exchanges, government portals: all converted to ash at roughly the same temperature. From a client's perspective this is the purest failure in the catalogue: no status, no body, no hang, no apology. The connection is accepted and then the socket dies mid-sentence — because the something on the other end is no longer metaphorically unreachable. It is materially, chemically unreachable. Clients that treat connection-reset as transient will retry into the void forever. Clients that distinguish "service is broken" from "service is now a crime scene" and failover accordingly will survive. This specimen slams the socket on you, precisely the way the fire department would have wanted.

Source: OVHcloud incident report — SBG2 fire · 2021-03-10

Replay it

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

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-090 — Backbone congestion black hole (Cloudflare, Jul 2020) FD-2026-092 — Nationwide core-network kill (Rogers, Jul 2022) FD-2026-006 — Total reachability loss (Meta BGP withdrawal, Oct 2021) FD-2026-025 — Edge DNS unreachable (Akamai, Jul 2021)