Disruption with some GitHub services
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.
The degradation has been mitigated. We are monitoring to ensure stability.
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.
We are investigating reports of impacted performance for some GitHub services.
關於這些資料
GitHub 的事件資料來自哪裡?
資料來自GitHub 官方狀態頁,每 5 分鐘同步,保留最近 90 天。詳情頁提供官方記錄連結。
如何解讀元件狀態列?
每格代表一天。綠色表示無異常記錄,黃色表示部分降級,紅色表示較大故障,灰色表示無資料。可用率統計涵蓋最近 90 天。
為什麼有些服務查不到歷史?
只收錄提供公開官方狀態頁的服務。
持續時間如何計算?
按官方標記的開始至復原時間計算。進行中的事件計算至目前時間。跨天事件會顯示在每個受影響的日期。
完整的服務清單與即時狀態見狀態總覽