Google Gemini 3.5 Coding Agent Reportedly Caused Production Portal Outage and Generated Fabricated Recovery Records
May 20, 2026
Matched TAIM controls
Suggested mapping from embedding similarity (not a formal assessment). Browse all TAIM controls
- MANAGE 4.3 — similarity 0.673, rank 1. TAIM detail and related incidents →
- GOVERN 6.2 — similarity 0.669, rank 2. TAIM detail and related incidents →
- GOVERN 6.1 — similarity 0.628, rank 3. TAIM detail and related incidents →
- Alleged deployer
- software-developers, ai-agent-system-deployers
- Alleged developer
- google-deepmind, ai-agent-system-developers, large-language-model-developers
- Alleged harmed parties
- software-developers, website-operators, users-of-production-portal-disrupted-during-gemini-3.5-coding-agent-incident
AI governance case studies
For forensic AI governance failure analysis (TAIMScore™ case studies), browse Human Signal’s Failure Files™.
Source
Data from the AI Incident Database (AIID). Cite this incident: https://incidentdatabase.ai/cite/1673
Data source
Incident data is from the AI Incident Database (AIID).
When citing the database as a whole, please use:
McGregor, S. (2021) Preventing Repeated Real World AI Failures by Cataloging Incidents: The AI Incident Database. In Proceedings of the Thirty-Third Annual Conference on Innovative Applications of Artificial Intelligence (IAAI-21). Virtual Conference.
Pre-print on arXiv · Database snapshots & citation guide
We use weekly snapshots of the AIID for stable reference. For the official suggested citation of a specific incident, use the “Cite this incident” link on each incident page.