Updated 1:17 p.m. Eastern on November 19, 2026
GitHub says the incident involving impacted performance for some of its services has been resolved, according to its latest official update.
What is affected
GitHub web sessions stopped renewing based on recent activity, causing users to be signed out when their sessions expired due to inactivity.
Official update timeline
We are investigating reports of impacted performance for some GitHub services.
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.
The degradation has been mitigated. We are monitoring to ensure stability.
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.













