GitHub outage, 13 November 2026
Incident with Pull Requests
- Started
- Resolved
- 13 Nov 2026, 18:29 UTC (after 2 h 42 min)
- Impact
- Major
- Affected
- Pull Requests
Is this still happening?
No. GitHub marked this incident resolved on 13 Nov 2026, 18:29 UTC, 2 h 42 min after it began.
Right now: GitHub reports degraded performance on some systems. (as of 13 Nov, 20:51 UTC) Live GitHub status
At a glance
- GitHub rated this a major incident (partial outage).
- It was resolved after 2 h 42 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 34 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 10 Nov 2026.
- GitHub said a root cause analysis would follow; it has not appeared on the status page yet.
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 1 h 44 min
-
, resolved after 2 h
-
, resolved after 9 min
Incident with Actions, Issues, API Requests and Pull Requests
-
, resolved after 4 h 30 min
-
, resolved after 7 h 54 min
Other recent GitHub incidents
Something wrong on this page?
Thanks - your report is on its way to us. We read every one.