What this tests

retry-logicmonitoring

Point your client at this specimen and find out — before prod does — whether it backs off, retries, and knows when to stop.

Anatomy

On the 8th of June 2021, a dormant bug in Fastly's code woke up, stretched, and took down what felt like half the visible internet. Amazon, Reddit, GOV.UK, the New York Times — all simultaneously replaced by whatever error page a CDN picks when it has stopped picking. One customer deploying a perfectly valid config triggered it. One. Like a butterfly flapping its wings, if the butterfly had root access. The interesting bit isn't the bug, it's the blast radius. Thousands of perfectly healthy origin servers sat there, innocent as lambs, while the layer in front of them turned to soup. Your uptime was immaculate. Your availability was somebody else's YAML file. This specimen models the degraded phase: mostly errors, the occasional success — just enough signal to keep your retry logic hopeful and your load balancer flapping like a deckchair in a hurricane. Arguably worse than total death, because now the incident call has *options* to argue about.

Source: Fastly summary of June 8 outage · 2021-06-08

Replay it

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

// response appears here

Signature

{Status:0 Headers:map[] Body: Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[{Weight:85 Signature:{Status:503 Headers:map[] Body:{"error":"Error 503 Service Unavailable","detail":"Varnish cache server"} Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}} {Weight:15 Signature:{Status:200 Headers:map[] Body: Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}}]}

Keep digging

FD-2026-021 — S3 us-east-1 subsystem removal (AWS, Feb 2017) FD-2026-024 — Network config rollback storm (Cloudflare, Jun 2022) FD-2026-044 — Three-day outage from a consensus bug (Roblox, Oct 2021) FD-2026-059 — East-west network partition (GitHub, Oct 2018) FD-2026-089 — Launch-day capacity collapse (Pokémon GO, Jul 2016) FD-2026-003 — Elevated latency + partial 5xx (AWS us-east-1, Nov 2020)