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 response is 200, well-formed, correctly typed — and wrong. A cache layer served a response that's twenty-four hours old, the Age header is right there admitting it, and nothing about the bytes tells you the data is a museum exhibit. The origin updated yesterday. The cache didn't get the memo. The memo is what the cache serves. This is the stealth fault: nothing looks broken, because nothing is broken — mechanically. The failure is semantic, temporal, a lie told by omission at the layer between your client and the truth. Clients that ignore Age, X-Cache, and Last-Modified will cheerfully consume history as fact. Clients that respect them get the answer to a question someone asked yesterday. The specimen serves a valid body stamped with Age: 86400. If your client doesn't notice, it just joined the long and honourable tradition of systems confidently acting on stale data — the same tradition responsible for at least one airline pricing fiasco and innumerable "it says it's in stock" support tickets.

Replay it

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

// response appears here

Signature

{Status:200 Headers:map[Age:86400 Cache-Control:max-age=900 X-Cache:HIT] Body:{"status":"operational","updated_at":"yesterday, technically"} 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-094 — Stale crew-scheduling data melts operations (Southwest, Dec 2022) FD-2026-096 — The endpoint that never came back (Code Spaces, Jun 2014) FD-2026-103 — Zombie health check (200 while dead inside)