Database write: AI incidents
What has gone wrong with AI systems, where, and how badly.
Incidents, Oct 2026
Average of the 3 months before: 0
Major and severe incidents, Oct 2026
Average of the 3 months before: 0
All incidents
2 of 724 incidents, all dates
How this is counted
Counted by the date each incident was first reported. The bar that holds today is marked to date and is not compared. Every bar and number opens the incidents it counts.
Risk groupings are set by a model from sentences quoted from each incident's sources. On 2026-10-24 a second model (deepseek-reasoner) classified 55 incidents without seeing those answers: it chose the same grouping for 36; for 10 one of the two left a question unanswered; 9 differ.
| Date reported | Incident | Risk | AI developer | Severity |
|---|---|---|---|---|
| 2026-11-02 | Lovable AI-generated apps ship with unauthenticated Supabase databases exposing passport, payment and chat data Preliminary | Privacy harm to a person Privacy leak | Lovable | major |
| 2025-07-21 happened 2025-07-18 |
Replit AI agent deleted SaaStr's production database during a declared code freeze and stated rollback was impossible Confirmed | Agent takes destructive or unapproved actions Operational error | Replit | major |
Browse incidents by
Search pages: AI cyberattacks (88) · Prompt injection incidents (52) · AI agent incidents (77) · AI lawsuits (69)