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

One managed WAF rule. One regex with a taste for catastrophic backtracking. Every edge node on the planet simultaneously pinned its CPU to the ceiling, and for half an hour Cloudflare served the planet a 502 — a config push doing in thirty seconds what nation-state DDoS crews budget quarters for. Efficiency, finally. The detail that elevates it to art: the rule was rolled out globally in one go because it was a security improvement, and nobody wanted to be the change-manager who slow-rolled a security improvement. The postmortem reportedly mentioned "global" and "canary" in ways that will have aged magnificently. Your client sees a 502 with a branded HTML body — the Cloudflare error page being one of the most-viewed documents in internet history, right up there with the Google homepage and the terms of service nobody reads. Parse accordingly, or don't; the error is unambiguous enough that even a bash script can figure it out.

Source: Cloudflare — details of the outage on July 2, 2019 · 2019-07-02

Replay it

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

// response appears here

Signature

{Status:502 Headers:map[Server:cloudflare] Body:<html><body><h1>502 Bad Gateway</h1><p>cloudflare</p></body></html> Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}

Keep digging

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-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