What this tests
semanticsmonitoring
Point your client at this specimen and find out — before prod does — whether it interprets status codes and content types correctly, or makes things up.
Anatomy
The edge is fine. The edge is always fine. It's your origin that's unreachable — the proxy knocked and nobody answered, so it serves its own branded 523 in a friendly HTML page, which your API client receives because intermediaries cannot tell robots from humans and frankly have stopped trying. The operational horror: from the client's side, 523 is indistinguishable from "the service has ceased" — but the service is up! It's behind the curtain, working perfectly, unaware it has been pronounced dead by its own bouncer. The failure is between the edge and the origin, in the part of the network nobody on the incident call can see. Clients that log status codes get a number the on-call engineer will have to Google — which is half the educational value of this catalogue, really.
Replay it
curl -i https://faultydata.com/r/FD-2026-048
// response appears hereSignature
{Status:523 Headers:map[Content-Type:text/html; charset=UTF-8 Server:cloudflare] Body:<html><body><h1>Error 523</h1><p>Origin is unreachable</p><p>Cloudflare Ray ID: deadbeef-LHR</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-091 — Control plane loses its buildings (Cloudflare, Nov 2023) FD-2026-096 — The endpoint that never came back (Code Spaces, Jun 2014) FD-2026-094 — Stale crew-scheduling data melts operations (Southwest, Dec 2022) FD-2026-103 — Zombie health check (200 while dead inside) FD-2026-105 — HTTP 520 — the Cloudflare unknown-error junk drawer