What visitors reported during this incident
No visitor reports were filed for this incident.
Having problems with GitHub now? Check the current statusAffected services
Updates (5)
- Sep 3, 2026, 05:11 PMIncident with Grok Copilot AI Model Provider
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.
GitHub ↗ - Sep 3, 2026, 05:11 PMIncident with Grok Copilot AI Model Provider
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.
GitHub ↗ - Sep 3, 2026, 02:22 PMIncident with Grok Copilot AI Model Provider
The Grok 4.5 model has degraded availability as well. We are working with the upstream provider to resolve the issue.
GitHub ↗ - Sep 3, 2026, 02:20 PMIncident with Grok Copilot AI Model Provider
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 />
GitHub ↗ - Sep 3, 2026, 02:17 PMIncident with Grok Copilot AI Model Provider
We are investigating reports of degraded performance for Copilot AI Model Providers
GitHub ↗
What to do next
- Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
- Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
- Watch the provider going forward. Follow GitHub's status feed →
GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.