GitHub outage on November 19, 2026: Disruption with some GitHub services
GitHub reported an incident affecting GitHub for 1 hour 11 minutes on 19 November 2026, from 17:06 to 18:17 UTC.
Resolved
Official incident reported by GitHub
- Started
- 17:06
- 19 Nov 2026 UTC
- Resolved
- 18:17
- 19 Nov 2026 UTC
- Duration
- 1h 11m
- 1 hour 11 minutes
- Impact
- Minor
- as rated by GitHub
- Updates
- 4
- posted by GitHub
Timeline
All times UTC.
Official incident from GitHub
Disruption with some GitHub services
-
Official
Investigating
We are investigating reports of impacted performance for some GitHub services.
-
Official
Monitoring
Starting around 18:02 UTC on November 5, GitHub web sessions stopped being renewed based on recent activity, so users were signed out when their sessions expired due to inactivity. These sign-outs were caused by a bug in session renewal, not due to a security incident. We believe we fixed the bug at 05:23 UTC on November 19, and sessions created since then should renew as usual. We’re continuing to monitor the situation. If you had an inactive session from that period, you may still find that you’re signed out when you return to GitHub. If that happens, all you need to do is sign back in.
-
Official
Monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
-
Official
Resolved
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.
"Official" rows are quoted from GitHub's public status page, www.githubstatus.com. Very long posts are shortened.
What our checkpoints saw
HostTracker's checkpoints, which test github.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live GitHub status shows what our checks see right now.
Does your product depend on GitHub?
An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.
You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.
Independent measurement by HostTracker. Not affiliated with GitHub. Official updates are quoted from GitHub's public status page and remain GitHub's own words.