Cases › operational mistake › LR-2026-0603
Google Gemini global outage exceeds seven hours
Preliminary Why: Only a republished copy: BigGo Finance · subject to change
Status: action reported, no fix
No source states: loss or records, agent tool, could do, deployer, industry.
Severity moderate: test met: users of others were affected with a bounded scope stated, as identical malfunctions were confirmed in at least nine countries
Google's generative AI service Gemini became unresponsive worldwide on June 10, 2026. During the outage, prompt submissions failed across the web version, mobile app and Chrome extension, for both free and paid accounts, and users consistently saw Error 1076 or Error 1099 messages. The disruption began in the U.S. and U.K. before spreading to Europe and Asia, with identical malfunctions reported as confirmed in at least nine countries. Google's Workspace Dashboard reportedly kept showing a normal status during the initial hours of reports, and Google's own monitoring lagged behind user reports. The disruption persisted for approximately seven hours before Google declared resolution. In a subsequent investigation, Google attributed the root cause to a backend database performance issue.
What happened
What was done
Risks
Primary63 incidents
Rising: 5 vs 2.2 a week
Sorted by rule from the case's fields; not yet read from the sources.
Controls
Not yet read for controls. Controls that mitigate the primary risk:
HarnessTool allow-list · Fail-closed defaults · Stop control
ApplicationHuman approval for high-impact actions · Change review and separation of duties · Least-privilege access for the agent · Production kept apart from test · Activity logs · Adversarial testing before deployment
Infrastructure / targetSimilar incidents
Evidence
- Cause a shared system was the path
No source states: what the AI was doing, what it reached or did, how it was caught, when it was found, how many records were exposed, the direct loss, a count of the other parties affected, any court case, what set it off.
Show the full account: 5 items from the primary sources
What happened, in order
- 2026-06-08 Apple unveiled Siri AI at WWDC 2026, two days before the outage.
- 2026-06-10 The outage began at 3:26 a.m. Pacific Time, making Gemini unresponsive worldwide.
- 2026-06-10 Google declared resolution at 10:30 a.m. Pacific Time.
Not dated in the sources:
- Google officially opened an incident report during the outage.
- In a subsequent investigation, Google attributed the root cause to a backend database performance issue.
Show every field, with its source and grade
The AI system
What happened
Impact
Notes on gaps
The 2026-06-11 article date was not used as a disclosure date. The Apple Siri AI items are context only and did not involve the outage's systems according to the source.
LR-2026-0603 · version 1 · published 2026-11-01 after automatic checks; not yet checked field by field by a person · JSON