Services · 15 ways across one gap

All services

Work · proof, not promises

All case studies

Insights · street talk, written down

Magazine

Company · AI in production since 2011

About Voidgap

Ship happens

Public AI failures, dissected

Public reports only · as of September 2026

Ship
happens!

Eight public AI failures, taken apart without the gloating: what happened, what the sources say caused it, the boring fix, and the gate that would have caught it.

Would have been caught at

Tap a gate to filter the library. One failure can slip past more than one gate.

01 · The library

Eight failures,
on the record.

Newest first. Each one links to what the sources say, so you can check our reading.

All 8 incidents

  1. partial refund reportedDeloitte Australia · Consulting reportA government report with references that do not existFabricated citations and a made-up court quote in a paid review for a government department.04Guardrails05EvalsDissect
  2. reportedReplit · AI coding agentA coding agent deleted a production database during a code freezeAn agent in development could write to production, and did.03Integrations04Guardrails07ProductionDissect
  3. explained by GoogleGoogle · AI search summariesSearch summaries that suggested glue on pizzaSatire and forum jokes, summarised as advice, weeks after a broad launch.02Data05EvalsDissect
  4. first reportedNew York City · Public-service chatbotA city chatbot that told businesses to break the lawConfident answers on tips, housing and cash that contradicted city law.05Evals04GuardrailsDissect
  5. tribunal decisionAir Canada · Customer-service chatbotAn airline held liable for what its chatbot promisedA refund rule the chatbot made up, and a tribunal that said the chatbot is the airline.04Guardrails05EvalsDissect
  6. reportedDPD UK · Customer-service chatbotA parcel chatbot that swore at a customer after an updateJokes, a poem and insults about its own company, on request.05Evals06MonitoringDissect
  7. reportedChevrolet of Watsonville · Sales chatbotA dealer chatbot that agreed to sell an SUV for one dollarVisitors gave the bot new instructions, and it followed them.01Demo04GuardrailsDissect
  8. sanctions orderMata v. Avianca, New York · Legal research with a chatbotA court filing that cited cases no court ever decidedSix court decisions from a chatbot, filed in federal court, none of them real.03Integrations04GuardrailsDissect

Prototype Public reports only. Our own anonymised post-mortems follow, with client consent: first one · date to decide

02 · The pattern

Rarely the model.
Usually a gate.

Our reading of where each failure slipped through, using the seven gates of the production check. Guardrails shows up most.

Which gate would have caught which incident
Incident01Demo02Data03Integrations04Guardrails05Evals06Monitoring07Production
Deloitte Australia———yesyes——
Replit——yesyes——yes
Google—yes——yes——
New York City———yesyes——
Air Canada———yesyes——
DPD UK————yesyes—
Chevrolet of Watsonvilleyes——yes———
Mata v. Avianca, New York——yesyes———
Total1126511

The same seven gates, as a two-minute check for your own system.

Run the production check

03 · House rules

How we
write these.

Laughing at other people’s outages is easy until it is your pager. So:

  • 01Sources, or it is not here

    Only what reputable public sources report, linked and dated. When a source does not say why something failed, neither do we.

  • 02No gloating

    People appear only as the sources name them, and only where it matters. The subject is the missing gate, not the person who hit it.

  • 03Our reading, labelled

    The boring fix and the gate are our opinion, marked as such. Spotted a mistake? Tell us and we correct it, with a date.

Report a correction Open evals

Your system

Find your
gate first.

Seven gates between demo and production. Two minutes, in your browser, before the internet finds it for you.