GitHub Restores Core Services After 8-Hour Outage Hit Actions, APIs and Copilot
Updated
Updated · InfoWorld · Aug 18
GitHub Restores Core Services After 8-Hour Outage Hit Actions, APIs and Copilot
3 articles · Updated · InfoWorld · Aug 18
Summary
GitHub marked the incident resolved at 9:15 p.m. UTC after nearly eight hours of disruption across Actions, pull requests, APIs, Git operations, Webhooks and Copilot.
Error rates peaked at about 20% for GitHub’s web experience and API traffic, while archive and raw repository downloads saw roughly 50% failures and authentication systems also broke down.
A problematic component was identified by 4:36 p.m. UTC, but recovery was uneven: Git operations degraded again, APIs briefly slipped back, and Copilot authentication problems lingered after other services improved.
GitHub partially disabled authentication-token retries to reduce sporadic login failures, yet it still has not said what failed or why one component disrupted so many linked developer workflows.
The outage underscored GitHub’s role as enterprise development infrastructure, where simultaneous failures in code hosting, automation and integrations can stall software delivery even without a full platform shutdown.