GitHub Copilot incident
Disruption with some GitHub services
Started
November 19, 2026 at 05:06 PM UTC
Duration
1h 11m
Resolved
November 19, 2026 at 06:17 PM UTC
Updates timeline
- Investigating
We are investigating reports of impacted performance for some GitHub services.
- 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.
- Monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
- 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.
Get an email the next time GitHub Copilot goes down
Outage alerts for GitHub Copilot, straight to your inbox. No account needed, unsubscribe in every email.
Watching more than one service? A free account covers 5 services + a daily digest — and Pro is currently free.
Live GitHub Copilot status
Current indicator + 24h latency
All incidents
Cross-service timeline
Subscribe via RSS
Atom feed for any reader