GitHub outage on 5 October 2026
CriticalAn email when it goes down, and when it’s back.
“Incident with Actions”
On 5 October, GitHub had a critical outage affecting Actions and GitHub-hosted runners, with jobs delayed or failing to start, from 19:13 to 22:50 UTC (3 h 38 min). The status page's final update said impact began at 18:48 and that Actions recovered by 21:54. It also reported intermittent errors in repository lists, licensing and billing pages, Copilot features and Pages until 22:49, and said the cause was a partial networking failure between datacenter and cloud services. Zapier, BigCommerce, Intercom and Gusto also reported problems during the same period.
GitHub’s own incident page ↗- When
- 19:13–22:50 UTC
- How long
- 3 h 38 min
- Incident open on its page
- 19:11–22:49 UTC
- Components affected
- 2
- GitHub, 30 days before
- 1 other outage
What broke when
From GitHub’s own status page: when it moved each component into trouble, and back.
At the same time
Started in the hour before or during it
And 162 lesser-known services. Problems at the same time are a clue, never proof that one caused another.
Timeline
Times in UTC
- Investigating
- Actions: degraded performance
- Actions: major outage
- Pages: degraded performance
- Actions: degraded performance
- Actions: back to normal
- Pages: back to normal
- Resolved
Where this comes from
Stackpulse reads GitHub’s official status page at www.githubstatus.com every minute. The times above are when it reported the problem; the summary is written from its updates and checked against them.
Stackpulse isn’t affiliated with GitHub. Names and logos belong to their owners.