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
A status code Cloudflare invented because the real upstream did something so weird there was no number for it — empty responses, malformed headers, connections that reset mid-handshake. The 5xx bucket's junk drawer: officially "unknown error," colloquially "the origin did a thing and we're not explaining it." Clients see it constantly in the wild and handle it badly, because it's not in any RFC and half the retry libraries don't classify it as retryable. Spoiler: it's a 5xx. It is extremely retryable.
Replay it
curl -i https://faultydata.com/r/FD-2026-105
// response appears hereSignature
{Status:520 Headers:map[CF-RAY:8f00beef-LHR Content-Type:text/html Server:cloudflare] Body:<html><body><h1>520</h1><p>Web server is returning an unknown error</p></body></html> 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-096 — The endpoint that never came back (Code Spaces, Jun 2014) FD-2026-103 — Zombie health check (200 while dead inside) FD-2026-054 — Stale cache serving yesterday's answer