GitHub Copilot reported this minor-impact incident on its official status page on Sep 3, 2026, 14:17 UTC. It was resolved after 2h 54m.
Right now GitHub Copilot is operational. Live GitHub Copilot status →
Between 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.
The issues with our upstream model provider have been resolved, and Grok models are once again available in Copilot products and IDE surfaces.<br />We will continue monitoring to ensure stability, but mitigation is complete.
The Grok 4.5 model has degraded availability as well. We are working with the upstream provider to resolve the issue.
We 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.<br />
We are investigating reports of degraded performance for Copilot AI Model Providers
Our 5-minute checks didn't record a change in GitHub Copilot's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
GitHub Copilot reported 15 incidents in the last 90 days, 5 of them major or critical. A typical incident lasted 1h 14m. See GitHub Copilot's uptime and incident history