What this tests

monitoringsemantics

Point your client at this specimen and find out — before prod does — whether it surfaces a real signal, or reports green while users suffer.

Anatomy

An attacker got into Code Spaces' AWS console, demanded ransom, and when refused deleted everything — machines, volumes, snapshots, and crucially the backups, which lived in the same account as the things they were backing up. The company announced it was closing within twelve hours. It remains the canonical proof that "the backups are in the cloud" is not a sentence, it is a location. The signature is a 410 Gone, permanently. Not a 503 implying a future; a headstone. The only specimen in the registry where the correct handling is to update your DR plan.

Source: InfoWorld · 2014-06-01

Replay it

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

// response appears here

Signature

{Status:410 Headers:map[Content-Type:application/json] Body:{"error":"gone","detail":"service permanently discontinued; backups deleted with the data they were protecting"} Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}

Keep digging

FD-2026-023 — Global 502s from a bad WAF rule (Cloudflare, Jul 2019) FD-2026-048 — Origin unreachable (Cloudflare 523) FD-2026-091 — Control plane loses its buildings (Cloudflare, Nov 2023) FD-2026-094 — Stale crew-scheduling data melts operations (Southwest, Dec 2022) FD-2026-103 — Zombie health check (200 while dead inside) FD-2026-105 — HTTP 520 — the Cloudflare unknown-error junk drawer