Live  /  GitHub  /  Incident

GitHub: Disruption with some Copilot services

GitHub · github.comCritical outageResolved2026-10-28 15:24 UTC
Public — what happened

Summary

GitHub said some Copilot services were degraded starting at 14:12 UTC on 2026-10-28, with several AI models unavailable or less reliable in Copilot products and code editors. The company said the problem came from an upstream model provider and advised people to switch to a different model in the meantime. By 14:55 UTC GitHub said it had found the root cause, and at 15:15 UTC it said a mitigation was in place and recovery was beginning. The last update, at 15:24 UTC, said Copilot was still showing degraded performance and the investigation was continuing.

Affected

Copilot

As listed on GitHub’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach GitHub 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: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the GitHub report →

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