GitHub: Disruption with Gemini 2.5 Pro and Gemini 2.0 Flash in Copilot
Gemini outage, Sep 29, 2025 · 9 vendors, 9 incidents
GitHub’s incident blames Gemini as the cause. (hop 1, posted +8 min vs the first vendor naming Gemini)
“…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…”
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 --> h1
me["GitHub (this incident)<br/>posted +8 min"]:::me
h1 --- meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Timeline of updates
- resolved
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 with our upstream provider. Approximately 24% of requests failed, affecting 56% of users during this period. No other models were impacted. GitHub notified the upstream provider of the problem as soon as it was detected. The issue was resolved after the upstream provider rolled back a recent change that caused the disruption. GitHub will continue to enhance our monitoring and alerting systems to reduce the time it takes to detect and mitigate similar issues in the future.
From GitHub’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Impact, status and times are the vendor’s own, as last archived. View on www.githubstatus.com (opens in new tab).