Project updates delayed
On October 22, 2026, between 14:55 and 17:28 UTC, search on GitHub.com was degraded. Search-backed features in Issues, Pull Requests, Projects, Actions, Packages, and some REST API endpoints returned errors or incomplete results. On average, 21% of search requests failed, peaking at 52%. Running Actions workflows, uploading and downloading packages, and Git operations were not affected. <br /><br />This was due to the proxies that route requests to our search clusters running out of CPU while setting up encrypted connections. Requests that timed out were retried, which added more load and kept the proxies overloaded. The search clusters themselves remained healthy. <br /><br />We mitigated the incident by adding proxy capacity, after which search recovered at 17:28 UTC. <br /><br />We have started reducing the CPU cost of these encrypted connections. We are also working to make search retries adjustable during an incident without a deployment, and to alert on search failures sooner. Together these will reduce our time to detection and mitigation of issues like this one in the future.
The degradation has been mitigated. We are monitoring to ensure stability.
GitHub Projects update processing has improved, but newly added items may still take longer than expected to appear. <br /><br />We're continuing to work on the remaining delays and monitor recovery.
Some GitHub Projects updates, including newly added items and changes to issues and pull requests, are still delayed.<br /><br />We have seen some recovery, and are working to add more capacity to accelerate the recovery.
Some GitHub Projects updates, including newly added items and changes to issues and pull requests, remain delayed.<br /><br />We've identified interruptions in update processing and are evaluating mitigations to restore normal operation.
Some GitHub Projects updates related to issue changes and merged pull requests are still delayed. We're investigating the remaining delays and working to restore normal processing.
Some updates in GitHub Projects are still delayed. We're continuing mitigation work and monitoring.
The other affected services have recovered. <br /><br />We're continuing to investigate GitHub Projects and verify that normal operation has been restored.
We're seeing recovery across the affected services. GitHub Projects is still recovering as queued updates are processed, and we're continuing to monitor for stability.
Actions, Issues, Packages and Pull Requests are operating normally.
We're seeing recovery after adding capacity, with errors decreasing. Some users may still experience errors loading Issues, Pull Requests and search results on github.com. <br /><br />We're continuing to work towards full recovery and monitoring for stability.
Some users continue to experience errors loading Issues, Pull Requests, package listings and search results on github.com. <br /><br />We're working through multiple mitigation efforts and continuing to investigate.
API Requests is operating normally.
Packages is experiencing degraded performance. We are continuing to investigate.
API Requests is experiencing degraded performance. We are continuing to investigate.
Some users continue to experience intermittent errors loading Issues, Pull Requests and search results on github.com. <br /><br />We're investigating and evaluating mitigation options to restore normal service.
Some users may experience intermittent errors loading Issues, Pull Requests and search results on github.com. <br /><br />We're investigating and working to restore normal service.
We are investigating reports of degraded performance for Actions, Issues and Pull Requests
關於這些資料
GitHub 的事件資料來自哪裡?
資料來自GitHub 官方狀態頁,每 5 分鐘同步,保留最近 90 天。詳情頁提供官方記錄連結。
如何解讀元件狀態列?
每格代表一天。綠色表示無異常記錄,黃色表示部分降級,紅色表示較大故障,灰色表示無資料。可用率統計涵蓋最近 90 天。
為什麼有些服務查不到歷史?
只收錄提供公開官方狀態頁的服務。
持續時間如何計算?
按官方標記的開始至復原時間計算。進行中的事件計算至目前時間。跨天事件會顯示在每個受影響的日期。
完整的服務清單與即時狀態見狀態總覽