‹ Back to incident history

Disruption with some GitHub services

ResolvedMinor incidentGitHub
Friday, November 20, 2026 01:06 – Friday, November 20, 2026 02:17 (1 hr 11 min)
Updates
ResolvedFriday, November 20, 2026 02:17

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.

MonitoringFriday, November 20, 2026 02:05

The degradation has been mitigated. We are monitoring to ensure stability.

MonitoringFriday, November 20, 2026 01:43

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.

InvestigatingFriday, November 20, 2026 01:06

We are investigating reports of impacted performance for some GitHub services.

Incident data from the GitHub official status page:Read the official incident

About this data

Where does the incident data for GitHub come from?

Data comes from the GitHub official status page, syncs every 5 minutes, and covers 90 days. The detail page links to the original report.

How do I read the component status bars?

Each block is one day. Green means no issue was reported, yellow means degraded performance, red means a major outage, and gray means no data. Availability covers the last 90 days.

Why is history missing for some services?

Only services with a public official status page are included.

How is duration calculated?

Duration runs from the official start time to recovery, or to the current time for ongoing incidents. Incidents spanning multiple days appear on each affected day.

See the full service list and live status in the status overview