GitHub search is degraded

Update timeline

1. investigating Apr 27, 2026, 04:31 PM UTC

   We are investigating reports of degraded performance for Actions

2. investigating Apr 27, 2026, 04:33 PM UTC

   Customers across GitHub are experiencing failures with searches. Examples include: workflow run failures, projects failing to load, and timed out search requests. This is due to an ongoing infrastructure issue that we have been investigating.

3. investigating Apr 27, 2026, 04:36 PM UTC

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

4. investigating Apr 27, 2026, 04:39 PM UTC

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

5. investigating Apr 27, 2026, 04:53 PM UTC

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

6. investigating Apr 27, 2026, 05:35 PM UTC

   Users are experiencing intermittent failures to view issues, pull requests, projects and Actions workflow runs. We are still investigating and attempting mitigations. We will provide further updates.

7. investigating Apr 27, 2026, 06:17 PM UTC

   We're continuing to see connectivity issues reaching elasticsearch. Impact on downstream services will be intermittent as we find the root cause

8. investigating Apr 27, 2026, 06:19 PM UTC

   Pull Requests is experiencing degraded availability. We are continuing to investigate.

9. investigating Apr 27, 2026, 07:50 PM UTC

   We have identified the source of the additional load causing stress on our ElasticSearch clusters. We have disabled the source of that load and are seeing signs of recovery

10. investigating Apr 27, 2026, 08:06 PM UTC

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

11. investigating Apr 27, 2026, 09:32 PM UTC

    We've applied a mitigation and continuing to monitor

12. monitoring Apr 27, 2026, 09:33 PM UTC

    The degradation affecting Actions, Issues, Packages and Pull Requests has been mitigated. We are monitoring to ensure stability.

13. monitoring Apr 27, 2026, 10:35 PM UTC

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

14. monitoring Apr 27, 2026, 10:44 PM UTC

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

15. resolved Apr 27, 2026, 10:46 PM UTC

    This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.