← Back to GitHub History
minor✓ Resolved

Disruption with some GitHub services

GitHub•
Status
resolved
Duration
1h 11m
Updates
4
Coverage
0 articles

INCIDENT TIMELINE

✓ Resolved
This incident has been resolved.
resolved
Between November 5, 2026, at 18:02 UTC and November 19, 2026, at 18:05 UTC, GitHub users experienced unexpected expiration of their web browser sessions despite continued activity, requiring them to login. An authentication change introduced an issue that caused web requests to bypass the session activity updates and cookie renewal that normally extend session lifetime. Affected sessions consequently expired when they reached their initial expiration time.<br /><br />We mitigated the incident by deploying a fix to ensure that continued web activity renews session expiration and browser cookies.<br /><br />We are adding monitoring to detect unexpected drops in session renewal activity, helping us catch similar issues sooner and reduce their impact on users.
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
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.<br /><br />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.<br /><br />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.
investigating
We are investigating reports of impacted performance for some GitHub services.

📊 TECHNICAL DETAILS

Internal ID
7c049c76-3f69-4967-aca6-d72d6d7b72a5
External ID
m310qbkfm3ww
🕐 Started
🔄 Last Updated
✓ Resolved
MINOR
Impact Level
1h 11m
Total Duration
4
Status Updates
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed