What this tests

timeoutsretry-logic

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 botnet of compromised webcams and toasters — Mirai, because of course your toaster has a botnet — pointed roughly ten million devices at Dyn's resolvers on a Friday morning. Twitter, Spotify, Reddit, Netflix: all technically running perfectly, all functionally dead, because the phone book was on fire. The responses were the worst kind: not errors, just absence. Queries sailed into the void and came back as timeouts, which meant every client in America learned the same lesson simultaneously — your DNS timeout configuration is your actual uptime configuration.

Source: Krebs on Security · 2016-10-21

Replay it

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

// 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:60 Signature:{Status:503 Headers:map[] Body:{"error":"resolver timeout"} Corrupt: Delay:0x69e720c5d190 Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}} {Weight:25 Signature:{Status:503 Headers:map[] Body:{"error":"SERVFAIL"} 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:{"answer":"93.184.216.34","ttl":300} Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}}]}

Keep digging

FD-2026-060 — Network congestion cascade (Google Cloud, Jun 2019) 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)