Grok 4.6 and Grok 4.7 Service Issues

What to do

• Check whether you use GitHub Copilot AI Model Providers. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 42m it lasted.

  Anything that failed between 2026-10-23 23:41 UTC and 2026-10-24 00:23 UTC may need a replay.

• Subscribe to GitHub's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=github works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from GitHub 4

1. investigatingOct 23, 2026, 11:41 PM UTC

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

   provider

2. investigatingOct 23, 2026, 11:42 PM UTC

   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.

   provider

3. monitoringOct 24, 2026, 12:23 AM UTC

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

   provider

4. resolvedOct 24, 2026, 12:23 AM UTC

   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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.