GitHub Copilot: Disruption with some GitHub services

GitHub Copilot · github.comImpact: minorResolved2026-09-15 20:00 UTC

Public — what happened

Summary

On September 15, 2026 between 15:30 and 20:00 UTC, some Copilot code reviews on pull requests failed to complete. The cause was increased latency in an internal caching service that GitHub Copilot Code Review relies on to coordinate its review jobs. This caused a timeout in lock acquisition, which interrupted the job. We reverted the change to the internal caching service and restored normal operation by 20:00 UTC.<br /><br />We sincerely apologize for the disruption.

Timeline

Started — 2026-09-15 19:11 UTC
Last update — 2026-09-15 20:00 UTC
Resolved — 2026-09-15 20:00 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.