GitHub Copilot: Incident with Grok Copilot AI Model Provider

GitHub Copilot · github.comImpact: minorResolved2026-09-03 17:11 UTC

Public — what happened

Summary

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.

Timeline

Started — 2026-09-03 14:17 UTC
Last update — 2026-09-03 17:11 UTC
Resolved — 2026-09-03 17:11 UTC

Source of record: provider status page. Mirrored as reported; times in UTC.

With SquidGrid — where it starts on the route

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach GitHub Copilot against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see

Customers get the live Provider Assessment Report for GitHub Copilot: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the GitHub Copilot report →

Related: GitHub Copilot status & history. SquidGrid is not affiliated with GitHub Copilot.