GitHub outage on 30 October 2026
CriticalAn email when it goes down, and when it’s back.
“Disruption with GitHub services”
GitHub had a disruption on 30 October that lasted about 32 minutes, from 14:32 to 15:04 UTC, with its status page showing degraded performance for Issues from 14:36 to 14:45 and for Pages from 14:39 to 14:49. The status page's updates gave a different window, reporting a burst of errors across numerous services between 14:21 and 14:30, before the incident was opened. They mentioned a "temporarily overloaded component" and said the root cause was still under investigation. MoonPay, Musixmatch, OpenAI and Clever also reported problems at around the same time.
GitHub’s own incident page ↗- When
- 14:32–15:04 UTC
- How long
- 32 min
- Incident open on its page
- 14:31–15:02 UTC
- Components affected
- 2
- GitHub, 30 days before
- 8 other outages
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 87 lesser-known services. Problems at the same time are a clue, never proof that one caused another.
Timeline
Times in UTC
- Investigating
- Issues: degraded performance
- Pages: degraded performance
- Issues: back to normal
- Fix in place, monitoring
- 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.