GitHub incident: Incident with Grok Copilot AI Model Provider

Affected components

• Copilot AI Model Providers

1. resolvedSep 3, 2026, 17:11 UTC

   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.

2. investigatingSep 3, 2026, 17:11 UTC

   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.

3. investigatingSep 3, 2026, 14:22 UTC

   The Grok 4.5 model has degraded availability as well. We are working with the upstream provider to resolve the issue.

4. investigatingSep 3, 2026, 14:20 UTC

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

5. investigatingSep 3, 2026, 14:17 UTC

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

What APIStatus.watch saw

Our 5-minute checks didn't record a change in GitHub's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Cursor: Investigating service degradationCritical · Sep 3, 2026, 13:41 UTC
• Intercom: Fin failures in Australia regionCritical · Sep 3, 2026, 14:29 UTC
• Elasticsearch: Replication bug causing slow recoveriesMajor · Sep 1, 2026, 08:16 UTC
• OVHcloud: [GLOBAL][Databases] - MongoDB incident notificationMajor · Sep 3, 2026, 10:18 UTC
• Anthropic: Elevated errors for multiple modelsMajor · Sep 3, 2026, 13:26 UTC
• Cursor: Elevated errors for Anthropic ModelsMajor · Sep 3, 2026, 14:17 UTC
• Discord: Some servers unavailableMajor · Sep 3, 2026, 14:35 UTC
• MongoDB Atlas: Impaired Cluster operations in AWS me-central-1 and AWS me-south-1Major · Sep 3, 2026, 16:44 UTC
• OVHcloud: [EU-SOUTH-MIL][Containers & Orchestration] - Managed Private Registry incident notificationMinor · Aug 26, 2026, 15:00 UTC
• Snowflake: INC20000150Minor · Aug 28, 2026, 00:07 UTC

How often does GitHub have incidents?

GitHub reported 49 incidents in the last 90 days, 15 of them major or critical. A typical incident lasted 1h 16m. See GitHub's uptime and incident history