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

A developer unpublished an eleven-line string-padding function over a naming dispute, and within minutes half the JavaScript ecosystem couldn't build — Babel, React, Node itself, all face-planted on a dependency the size of a haiku. The registry dutifully returned 404 for a URI that had worked for years. The supply chain turned out to be a single, very short string. The horror isn't the dependency — it's the discovery that your build was a house of cards and one of the cards was a function that pads strings with spaces, a function you could have written on a napkin, a function that in some sense you already had. Your client sees a registry-shaped 404 with a JSON body. The specimen's real payload is the lesson: pin your dependencies, cache your artifacts, and never build a cathedral on a library named left-pad.

Source: npm blog — kik, left-pad, and npm · 2016-03-23

Replay it

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

// response appears here

Signature

{Status:404 Headers:map[Content-Type:application/json] Body:{"error":"Not found","reason":"document not found","name":"left-pad"} 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-048 — Origin unreachable (Cloudflare 523) FD-2026-050 — 420 Enhance Your Calm (Twitter API v1.1)