GitHub outage on 10 November 2026
CriticalAn email when it goes down, and when it’s back.
“Incident with Git Operations and Pull Requests”
GitHub had a critical outage on 10 November from 16:11 to 17:55 UTC (1 h 44 min), with Pull Requests affected throughout and Git operations showing elevated response times. According to GitHub's status page, Actions had a major outage from 16:26 to 17:28 UTC, which delayed workflows triggered from pull requests, while pull request delays and failures continued until the incident was resolved; no cause was given. GoDaddy, Procore, HubSpot and Webflow also reported problems at the same time, and GitHub had three other outages in the three days before.
GitHub’s own incident page ↗- When
- 16:11–17:55 UTC
- How long
- 1 h 44 min
- Incident open on its page
- 16:10–17:55 UTC
- Components affected
- 2
- GitHub, 30 days before
- 11 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 171 lesser-known services. Problems at the same time are a clue, never proof that one caused another.
Timeline
Times in UTC
- Investigating
- Pull Requests: degraded performance
- Actions: degraded performance
- Pull Requests: major outage
- Actions: partial outage
- Pull Requests: degraded performance
- Actions: back to normal
- Resolved
- Pull Requests: back to normal
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.