GitHub Copilot: Incident with Copilot AI Model Providers

GitHub Copilot · github.comImpact: criticalResolved2026-08-27 12:12 UTC

Public — what happened

Summary

GitHub Copilot said that on August 27, 2026, from roughly 09:20 to 12:14 UTC, the Kimi K3 model in Copilot was degraded, with users seeing more errors than usual when using it. The company said other models were not affected and attributed the problem to an issue at its upstream provider. According to GitHub, the provider applied a fix that resolved it, and GitHub said it is working with that provider to make the service more resilient. The incident was rated critical and is marked resolved.

Timeline

Started — 2026-08-27 10:04 UTC
Last update — 2026-08-27 12:12 UTC
Resolved — 2026-08-27 12:12 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.