Resolved
GitHub · degraded service
Incident with Grok Copilot AI Model Provider
Posted 3 Sep 14:17 UTC, last seen today 11:33 UTC.
What it affected
As the provider names itWhat the provider posted
Newest first- 3 Sep 17:11 UTCResolvedBetween 13:22 and 17:11 UTC on September 03, 2026, GitHub Copilot experienced degradation affecting several Grok models, including Grok 4.5 and Grok 4.6. Users encountered elevated error rates, but other models were not affected. The degradation was caused by an issue with an upstream model provider. GitHub engineers detected the issue through automated monitoring, displayed in-product warnings for the affected models, and coordinated with the provider. Service returned to normal after the provider implemented a mitigation.
- 3 Sep 17:11 UTCUpdateThe issues with our upstream model provider have been resolved, and Grok models are once again available in Copilot products and IDE surfaces.We will continue monitoring to ensure stability, but mitigation is complete.
- 3 Sep 14:22 UTCUpdateThe Grok 4.5 model has degraded availability as well. We are working with the upstream provider to resolve the issue.
- 3 Sep 14:20 UTCUpdateWe are experiencing degraded availability for the Grok 4.6 model in Copilot Chat, VS Code and other Copilot products. This is due to an issue with an upstream model provider. We are working with them to resolve the issue.
- 3 Sep 14:17 UTCInvestigatingWe are investigating reports of degraded performance for Copilot AI Model Providers
Around it
From the sources ChangeIntel reads; a match in time is not a causeElsewhere at the same time
- Anthropic (Claude) Elevated errors for multiple models
- OpenAI Elevated errors across ChatGPT and Codex
Earlier incidents in the 14 days before
- GitHub: Delays in commit processingService incident · 1 Sep
- GitHub: Elevated rate of errors for OpenAI models provided by CopilotService incident · 31 Aug
- GitHub: Incident with Copilot AI Model ProvidersService incident · 27 Aug
- GitHub: Disruption with GitHub BillingService incident · 26 Aug
- GitHub: Incident with Actions and Pull RequestsService incident · 26 Aug
What changed
First observed 14 Oct 2026No field changes in the recorded history.
Cite this recorded revision to keep the same title, summary, facts and links when the page changes.
A day selects the latest observation by the end of that UTC day; today's selection can change until midnight. History starts when this installation records it.
Keep track
- Service status now: every provider ChangeIntel reads, with ongoing incidents first.
- Status RSS feed: new and ended incidents as they happen.
- Everything about GitHub: its changes, known issues and incidents on one timeline.