GitHub Copilot incident
Grok 4.6 and Grok 4.7 Service Issues
Resolved after 41 min.
- Started
- Ended
- Worst state
- Degraded
- On GitHub Copilot’s status page
- Source
- Components
- Copilot AI Model Providers
Timeline
- GitHub Copilot status page · Reported Grok 4.6 and Grok 4.7 Service Issues
- GitHub Copilot status page · Investigating We are investigating reports of degraded performance for Copilot AI Model Providers
- GitHub Copilot status page · Investigating We are experiencing degraded availability for the Grok 4.6 and Grok 4.7 models in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting 'Auto' to continue using Copilot.
- GitHub Copilot status page · Monitoring The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.
- GitHub Copilot status page · Resolved Between 23:28 and 00:23 UTC on October 27, 2026, GitHub Copilot experienced degradation affecting Grok 4.6 and Grok 4.7 models. Users encountered elevated error rates when using these models. The degradation was caused by an issue with an upstream model provider. GitHub engineers detected the issue through automated monitoring and coordinated with the provider. Our automated model-warning system activated in-product warnings for affected models during the incident. Service returned to normal after the provider implemented a mitigation.
Cite this incident
Site Qwality, “Grok 4.6 and Grok 4.7 Service Issues,” Oct 23, 2026, https://siteqwality.com/is-copilot-down/incidents/copilot-202610232341/
Free to quote with a link to this page.