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
A winter storm hit, flights cancelled, and Southwest's crew scheduling systems — ancient by aviation standards, which is saying something — could not track where anyone actually was. The systems kept cheerfully returning data; the data was just confidently, operationally wrong, and crews ended up phoning in manually to tell the airline where they were standing. 16,700 flights cancelled. The worst response an API can give isn't an error — it's a confident, well-formed, stale answer. Everything 200s. Everything lies.
Source: Wikipedia · 2022-12-26
Replay it
curl -i https://faultydata.com/r/FD-2026-094
// response appears hereSignature
{Status:200 Headers:map[Content-Type:application/json Last-Modified:Mon, 19 Dec 2022 00:00:00 GMT X-Data-Freshness:stale] Body:{"flight":2982,"crew_assigned":"DEN","actual_crew_location":"a different state","schedule_version":"2022-12-19","confident":true} 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-035 — Stack trace in the error body FD-2026-046 — Dependency self-sabotage (colors.js, Jan 2022)