What this tests

retry-logictimeouts

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

Anatomy

A config change meant for a handful of servers was applied to a great many more, network capacity in the eastern US collapsed, and for four hours YouTube, Gmail, and a meaningful slice of everything built on GCP — including, delightfully, several companies whose entire pitch was "we're not on GCP" — degraded in unison. Turns out everyone is on GCP, spiritually. The signature is congestion, not death: requests that succeed after a geological delay, requests that fail fast, requests that succeed normally, interleaved with no pattern a health check can summarize. It is the failure mode where "is it up?" is the wrong question and "is it worth waiting for?" is the right one. Your client either has a latency budget or it has faith. This specimen tests which.

Source: Google Cloud incident 19009 — June 2, 2019 · 2019-06-02

Replay it

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

// 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:45 Signature:{Status:200 Headers:map[] Body: Corrupt: Delay:0x69e720bde740 Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}} {Weight:35 Signature:{Status:503 Headers:map[] Body:<html><body><h1>503 Service Unavailable</h1></body></html> Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}} {Weight:20 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-088 — DNS provider drowns in DDoS (Dyn, Oct 2016) FD-2026-093 — Routing-table overload blackout (Optus, Nov 2023) FD-2026-097 — Trading halt by infrastructure (Robinhood, Mar 2020) FD-2026-049 — Load balancer gives up waiting (ALB/ELB 504) FD-2026-002 — CDN edge degradation (Fastly, June 2021) FD-2026-003 — Elevated latency + partial 5xx (AWS us-east-1, Nov 2020)