RewindexOutage eventsSep 29, 2025
Gemini outage, Sep 29, 2025
9 vendors posted 8 incidents between 18:00 and 20:00 UTC, against about 6 incidents from 5 vendors in the same hours on an ordinary week. 4 vendors named Gemini in 3 incidents (3 of them blamed it). Vendors reported a Gemini outage; Gemini’s own incident for this date is not in the archive.
Observed, not verified. A line means a vendor’s incident named another vendor, or started in the same window. It is not a proven cause.
Times are UTC; lags are from when the first vendor named Gemini.
- first vendor named Gemini 18:31
How it spread
Vendors that named Gemini, grouped by when they posted, and vendors that blamed one of the vendors Gemini took down. Solid lines: the vendor named the other. Dashed: same window, not named.
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Gemini<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>4 vendors, 3 blamed Gemini<br/>Sentry, GitHub, GitHub Copilot, Optimizely"]:::blames
root --> h1Vendors that named Gemini
In their own words. “Blames” means a causal phrase sits next to the name (“due to”, “upstream provider”…).
Within an hour
3 vendors
- Incident, no impact listed
+0 min
Names Gemini
SentrySeer Features erroring intermittently
…Seer Features erroring intermittently Gemini-powered Seer features seem to be working normally.…
- Minor incident
+8 min
Blames Gemini
GitHuband GitHub CopilotDisruption with Gemini 2.5 Pro and Gemini 2.0 Flash in Copilot
…Disruption with Gemini 2.5 Pro and Gemini 2.0 Flash in Copilot On September 29, 2025, between 17:53 and 18:42 UTC, the Copilot service experienced a degradation of the Gemini 2.5 model due to an issue…
- Major incident
+30 min
Blames Gemini
OptimizelyOpal outage due to Google Gemini availability issue
…Opal outage due to Google Gemini availability issue This issue has been resolved. Thank you for your patience.…
Same window, did not name anyone
5 incidents started during the event without naming Gemini or another vendor. Some are part of it, some are a normal day’s background (about 6 in these hours).
Show all 5
- −24 minMinor incident
- −15 minMinor incident
- −14 minMinor incident
- −8 minMajor incident
- +4 minMajor incident
Detected automatically from 8 status pages opening incidents in the peak hour (normally at most 6). Mentions are matched by name in each incident’s title and updates, then classified as cause, location or integration; quoted text is the vendor’s. Vendors that share one status page are shown once.