MicrosoftRadarIndependent status for Microsoft services

Grok 4.6 and Grok 4.7 Service Issues

ResolvedResolved1 version

Facts

Source
GitHub Status · original
Started
(21 days ago)
Ended
· lasted 42 min
How it ended
Microsoft marked it resolved.
First captured by us
Last changed
(43 min ago)
Affected services
GitHub Copilot AI model providers

Last text from Microsoft

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.<br /><br />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.

Quoted from GitHub Status (source), captured . Reproduced for reporting and archival purposes.

Official updates

Posted by GitHub Status, newest first.

  1. 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.<br /><br />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.

  2. Monitoring

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

  3. 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.

  4. Investigating

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

What Microsoft changed

Microsoft edits the text of an incident in place. We keep every version we capture (checked every minute) and highlight the difference. Removed text is struck through, added text is marked.

  1. First version we captured

    Captured · Microsoft's own timestamp · revision q058vrk1
    Original text as we first saw it

    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.<br /><br />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.