Incident 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.
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
About this data
Where does the incident data for GitHub come from?
Data comes from the GitHub official status page, syncs every 5 minutes, and covers 90 days. The detail page links to the original report.
How do I read the component status bars?
Each block is one day. Green means no issue was reported, yellow means degraded performance, red means a major outage, and gray means no data. Availability covers the last 90 days.
Why is history missing for some services?
Only services with a public official status page are included.
How is duration calculated?
Duration runs from the official start time to recovery, or to the current time for ongoing incidents. Incidents spanning multiple days appear on each affected day.
See the full service list and live status in the status overview