GitHub outage, 8 November 2026
Increase in timeouts for some unauthenticated users
- Started
- Resolved
- 8 Nov 2026, 12:32 UTC (after 1 h 56 min)
- Impact
- Minor
- Affected
- API Requests
Is this still happening?
No. GitHub marked this incident resolved on 8 Nov 2026, 12:32 UTC, 1 h 56 min after it began.
Right now: GitHub reports degraded performance on some systems. (as of 13 Nov, 20:53 UTC) Live GitHub status
At a glance
- GitHub rated this a minor incident.
- It was resolved after 1 h 56 min. That is longer than a typical GitHub incident: the median of the 55 other resolved ones we recorded is 1 h 8 min.
- GitHub had 26 other incidents in the 30 days before it.
- 5 earlier incidents look like the same kind of problem (same affected part or wording); the most recent was on 4 Nov 2026.
Our summary from the GitHub incidents we have recorded since 31 Aug 2026 - how we count.
GitHub has said a root cause analysis will follow. We add it to this page when it is posted on the status page.
Last update from GitHub
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Similar GitHub incidents
Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.
-
, resolved after 2 h
-
, resolved after 31 min
-
, resolved after 9 min
Incident with Actions, Issues, API Requests and Pull Requests
-
, resolved after 11 h 2 min
-
, resolved after 18 h 44 min
Other recent GitHub incidents
Something wrong on this page?
Thanks - your report is on its way to us. We read every one.