GitHub-wide outage left Copilot degraded for hours after core git services recovered

GitHub / Microsoft (Copilot users worldwide)·GitHub CopilotFixed

A GitHub-wide incident starting at 13:40 UTC pushed repository-download error rates to about 50% and degraded Copilot alongside Issues, Actions and API traffic; when GitHub declared seven services mitigated at 16:59 UTC, Copilot was not among them and stayed impaired — specifically Copilot authentication — until the incident closed at 21:15 UTC.

Blast radius

7 hours 36 minutes of impact end to end; Copilot's authentication issues persisted roughly 6 hours 44 minutes after being first flagged, well after most core git/API services had already recovered, part of a string of repeated GitHub outages through 2026.

Root cause

Copilot sits on its own authentication/service dependency chain distinct from core git hosting, so it did not recover in step with services GitHub marked mitigated; GitHub has separately acknowledged that AI-assisted coding and agentic workflow traffic has been adding strain to its infrastructure.

How it was caught

GitHub's own status page tracked the incident through dozens of public updates as it evolved and partially relapsed.

What changed

GitHub said it was making structural changes intended to permanently remove recurring failure modes, following similar outages earlier in August 2026.

Take-awayDon't assume your coding agent is back just because the platform's core status goes green — monitor the agent's own auth/service path separately, since it can lag or fail independently.