GitHub outage on 6 October 2026
CriticalAn email when it goes down, and when it’s back.
“Several services are degraded”
On 6 October, GitHub had an outage logged from 19:59 to 23:41 UTC (3 h 42 min), but its status page reported that Pull Requests, Webhooks and Issues were degraded only briefly. Webhooks recovered by 20:04 and Pull Requests by 20:12. After that, the status page said only enterprise migrations stayed paused while a mitigation was deployed, and the incident was resolved at 23:40 with no cause stated yet. Cursor, one.com, SurveyMonkey and Asana also reported problems at the same time.
GitHub’s own incident page ↗- When
- 19:59–23:41 UTC
- How long
- 3 h 42 min
- Incident open on its page
- 19:57–23:40 UTC
- Components affected
- 2
- GitHub, 30 days before
- 3 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 140 lesser-known services. Problems at the same time are a clue, never proof that one caused another.
Timeline
Times in UTC
- Investigating
- Webhooks: degraded performance
- Pull Requests: degraded performance
- Webhooks: back to normal
- Pull Requests: back to normal
- Fix in place, monitoring
- Investigating
- 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.