CompaniesGitHub CopilotIncidents
GitHub Copilot: Disruption with some GitHub services
Timeline of updates
- 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.
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. - monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
- resolvedEdited
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.
We mitigated the incident by deploying a fix to ensure that continued web activity renews session expiration and browser cookies.
We are adding monitoring to detect unexpected drops in session renewal activity, helping us catch similar issues sooner and reduce their impact on users.
Changes Rewindex caught on this incident
- Incident updated: Disruption with some GitHub services
- Incident updated: Disruption with some GitHub services
- Incident updated: Disruption with some GitHub services
- Incident silently edited: Disruption with some GitHub services
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-11-19 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
8ae5a7844ffc16d7…Version 2 captured
In the 2026-11-19 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
a5955fa3e5c9f492…Version 3 captured
In the 2026-11-19 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
d90866762150467e…Version 4 captured
In the 2026-11-19 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
dff68265ae823982…
Rewindex captured a newer version after the last checkpoint; the next run () commits it.
Impact, status and times are the vendor’s own, as last archived. View on www.githubstatus.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by GitHub Copilot, started 2026-11-19 17:06 UTC, resolved after 1.2 h, 4 update(s); edited after publishing.
- Title
- Disruption with some GitHub services
- Vendor
- GitHub Copilot
- Date
- URL
- https://rewindex.com/company/github-copilot/incidents/m310qbkfm3ww
GitHub Copilot profileRecent GitHub Copilot incidentsAll outages on November 19, 2026GitHub Copilot in November 2026MarkdownJSON