GitHub outage on 7 October 2026
CriticalAn email when it goes down, and when it’s back.
“Incident with Git Operations, Pull Requests and Actions”
On 7 October, GitHub had a critical outage affecting Git Operations, Pull Requests, Actions and Webhooks, with Issues also degraded; its status page incident ran from 15:14 to 16:25 UTC. The status page said the widespread impact occurred between 15:06 and 15:16 UTC, and all components were marked mitigated by 15:49, though Git Operations degraded again at 15:35 after briefly returning to normal. Litmus and Cursor also had problems at the same time.
GitHub’s own incident page ↗- When
- 15:44–16:25 UTC
- How long
- 41 min
- Incident open on its page
- 15:14–16:25 UTC
- Components affected
- 5
- GitHub, 30 days before
- 4 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 150 lesser-known services. Problems at the same time are a clue, never proof that one caused another.
Timeline
Times in UTC
- Investigating
- Git Operations: major outage
- Actions: major outage
- Pull Requests: major outage
- Webhooks: degraded performance
- Issues: degraded performance
- Webhooks: major outage
- Git Operations: degraded performance
- Pull Requests: degraded performance
- Git Operations: back to normal
- Webhooks: degraded performance
- Pull Requests: back to normal
- Actions: back to normal
- Git Operations: degraded performance
- Issues: back to normal
- Git Operations: back to normal
- Webhooks: back to normal
- Fix in place, monitoring
- 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.