What this tests

semantics

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

RFC 7168 defines status 418 — "I'm a teapot" — for requests a teapot cannot fulfill because it is, and cannot stress this enough, a teapot. It was an April Fools' joke in 1998 and it's now more load-bearing than most of your error handling: real APIs return it, Google famously served it for years, and it survived a formal campaign to have it removed from HTTP libraries on the grounds that jokes shouldn't have status codes. The jokes won. Every client must answer the question: what do you do with a 418? It's a 4xx, so stop. But it's also meaningless, so... what was the error? There wasn't one. The response is a compliance test for "does your error handling handle errors that are technically correct and spiritually absurd". Clients that fall through to a generic "unexpected status" path pass. Clients that crash on an unmapped status code have learned something about the world's sense of humour, which is that the world's sense of humour is also load-bearing.

Source: RFC 7168 — The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances · 2014-04-01

Replay it

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

// response appears here

Signature

{Status:418 Headers:map[] Body:{"error":"I\u0027m a teapot","short_and_stout":true} Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}

Keep digging

FD-2026-004 — GitHub secondary rate limit FD-2026-010 — Gateway timeout from the edge (Cloudflare 522 pattern) FD-2026-023 — Global 502s from a bad WAF rule (Cloudflare, Jul 2019) FD-2026-029 — Production database deleted, backups broken (GitLab, Jan 2017) FD-2026-030 — Dependency vanishes from the registry (left-pad, Mar 2016) FD-2026-048 — Origin unreachable (Cloudflare 523)