GitHub Copilot problems on 19 November 2026
| Status | Resolved |
|---|---|
| Worst verdict | Some users report problems |
| Started | |
| Ended | |
| Duration | 1 h 11 min |
| Official incident | Disruption with some GitHub services |
Timeline
-
We started seeing problems. Our verdict: Some users report problems.
- · official updateDisruption with some GitHub services (investigating): “We are investigating reports of impacted performance for some GitHub services.” Source
- · official updateDisruption with 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. 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…” Source
- · official updateDisruption with some GitHub services (monitoring): “The degradation has been mitigated. We are monitoring to ensure stability.” Source
-
Looking normal again. We'll keep watching for 15 minutes before closing this.
-
Everything has looked normal for 15 minutes, so we marked this incident as resolved.
Times are shown in your local time zone. “Official update” entries quote GitHub's status page; follow the source link for the full text.
How we track incidents
We open an incident when GitHub Copilot stops looking normal or GitHub posts an official incident, and close it after 15 minutes with everything back to normal. More about our method.