‹ Back to incident history

Project updates delayed

ResolvedMinor incidentGitHub
Thursday, October 22, 2026 23:28 – Friday, October 23, 2026 10:30 (11 hr 2 min)
Affected components
API Requests
Issues
Pull Requests
Actions
Packages
Updates
ResolvedFriday, October 23, 2026 10:30

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.

MonitoringFriday, October 23, 2026 08:55

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

InvestigatingFriday, October 23, 2026 07:48

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.

InvestigatingFriday, October 23, 2026 06:07

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.

InvestigatingFriday, October 23, 2026 04:46

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.

InvestigatingFriday, October 23, 2026 03:56

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.

InvestigatingFriday, October 23, 2026 03:04

Some updates in GitHub Projects are still delayed. We're continuing mitigation work and monitoring.

InvestigatingFriday, October 23, 2026 02:26

The other affected services have recovered. <br /><br />We're continuing to investigate GitHub Projects and verify that normal operation has been restored.

InvestigatingFriday, October 23, 2026 01:43

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.

InvestigatingFriday, October 23, 2026 01:41

Actions, Issues, Packages and Pull Requests are operating normally.

InvestigatingFriday, October 23, 2026 01:16

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.

InvestigatingFriday, October 23, 2026 00:41

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.

InvestigatingFriday, October 23, 2026 00:35

API Requests is operating normally.

InvestigatingFriday, October 23, 2026 00:28

Packages is experiencing degraded performance. We are continuing to investigate.

InvestigatingFriday, October 23, 2026 00:26

API Requests is experiencing degraded performance. We are continuing to investigate.

InvestigatingFriday, October 23, 2026 00:08

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.

InvestigatingThursday, October 22, 2026 23:33

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.

InvestigatingThursday, October 22, 2026 23:28

We are investigating reports of degraded performance for Actions, Issues and Pull Requests

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