What this tests

monitoringretry-logic

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

A network maintenance window severed GitHub's east and west coast datacenters for 43 seconds. Forty-three seconds. The orchestrator layer, doing exactly what it was designed to do, promoted a stale MySQL primary on the wrong side of the partition — and the recovery, rebuilding a split-brain database topology by hand, took twenty-four hours of degraded service. Forty-three seconds in, a full day out. The ratio is the incident. Client-side it looked like a site that was technically up and spiritually absent: webhooks delayed, pages slow, writes failing — the degraded-everything pattern where nothing is quite broken enough to fail your health check and everything is broken enough to ruin your deploy. Composite: elevated latency, intermittent 500s, occasional clean success — the shape of an incident that is "resolved" three times before it is actually resolved, as anyone who has ever watched a status page will recognize in their bones.

Source: GitHub engineering — October 21 post-incident analysis · 2018-10-21

Replay it

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

// 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:40 Signature:{Status:200 Headers:map[] Body: Corrupt: Delay:0x69e720bde4e0 Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}} {Weight:40 Signature:{Status:500 Headers:map[] Body:{"message":"Internal server error"} 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-002 — CDN edge degradation (Fastly, June 2021) 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-089 — Launch-day capacity collapse (Pokémon GO, Jul 2016) FD-2026-003 — Elevated latency + partial 5xx (AWS us-east-1, Nov 2020)