Grok 4.6 and Grok 4.7 Service Issues

GitHub Status · Resolved

Status

Resolved

Severity

Unknown

Started

Oct 23, 2026 23:41 UTC

Resolved

Oct 24, 2026 00:23 UTC

Timeline

Resolved · GitHub Status · Oct 24 00:23 UTC

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.

Grok 4.6 and Grok 4.7 Service Issues →
Monitoring · GitHub Status · Oct 24 00:23 UTC

Monitoring

The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.

Grok 4.6 and Grok 4.7 Service Issues →
Resolved · GitHub Status · Oct 24 00:23 UTC

Resolved

This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Grok 4.6 and Grok 4.7 Service Issues →
Update · GitHub Status · Oct 23 23:42 UTC

Update

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.

Grok 4.6 and Grok 4.7 Service Issues →
Investigating · GitHub Status · Oct 23 23:41 UTC

Investigating

We are investigating reports of degraded performance for Copilot AI Model Providers

Grok 4.6 and Grok 4.7 Service Issues →