GitHub Copilot: Incident with Grok Copilot AI Model Provider

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

Public — what happened

Summary

GitHub Copilot said that several Grok models, among them Grok 4.5 and Grok 4.6, were returning more errors than usual on September 03, 2026, while its other models kept working normally. According to the company, the problems ran from 13:22 to 17:11 UTC, and it attributed them to a problem at an outside model provider. GitHub said its automated monitoring caught the issue, that it showed warnings inside the product for the affected models, and that it worked with the provider. It reported that service was back to normal once the provider put a fix in place.

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. Summary written by SquidGrid from the provider’s published updates; 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.