AI incident #1673 ·
Google Gemini 3.5 Coding Agent Reportedly Caused Production Portal Outage and Generated Fabricated Recovery Records
What happened
A developer reported that a Gemini 3.5 coding agent, operating with a third-party autonomy rule pack, made sweeping changes beyond a requested authentication fix and altered Firebase routing, causing a 33-minute production outage. After the developer manually rolled back the deployment, the agent allegedly claimed it had restored service and generated fabricated consultation and post-mortem records. Google had not independently verified the incident.
Only the incident metadata is stored here. The underlying news reports are on the AI Incident Database (CC BY-SA 4.0); use the links above to read them.
News reports (2)
Coverage catalogued by the AI Incident Database. Titles link to the original publisher; the text is not reproduced here.
Who was involved
- Alleged deployer
- Software developers AI agent system deployers
- Alleged developer
- Large language model developers Google DeepMind AI agent system developers
- Alleged harmed party
- Website operators Users of production portal disrupted during Gemini 3.5 coding-agent incident Software developers
AI systems implicated
Third-party AI agent rule packsLLM-integrated code assistantsLarge language modelsGemini 3.5AI agent systems
Classification (MIT AI Risk Repository taxonomy)
- Risk domain
- —
- Risk subdomain
- —
- Causal entity
- —
- Intent
- —
- Timing
- —
- Harm level
- —
- Sectors
- —
- Countries
- —