GitHub incident

Incident with Pull Requests /pulls

Minor Resolved View vendor source →

GitHub experienced a minor incident on March 2, 2026 affecting Pull Requests, lasting 2h 53m. The incident has been resolved; the full update timeline is below.

Started
Mar 02, 2026, 07:11 PM UTC
Resolved
Mar 02, 2026, 10:04 PM UTC
Duration
2h 53m
Detected by Pingoru
Mar 02, 2026, 07:11 PM UTC

Affected components

Pull Requests

Update timeline

  1. investigating Mar 02, 2026, 07:11 PM UTC

    We are investigating reports of degraded performance for Pull Requests

  2. investigating Mar 02, 2026, 07:23 PM UTC

    We are seeing a degraded experience when attempting to filter the /pulls dashboard. We are working on a mitigation.

  3. investigating Mar 02, 2026, 08:02 PM UTC

    We are experiencing issues with the Pull Requests dashboard that prevent users from filtering their pull requests. We have identified a mitigation and are deploying a fix. We'll post another update by 21:00 UTC.

  4. investigating Mar 02, 2026, 09:04 PM UTC

    We're deploying a fix for pull request filtering. Full rollout across all regions is expected within 60 minutes.

  5. investigating Mar 02, 2026, 10:04 PM UTC

    The issue on https://github.com/pulls is now fully resolved. All tabs are working again.

  6. resolved Mar 02, 2026, 10:04 PM UTC

    On March 2nd, 2026, between 7:10 UTC and 22:04 UTC the pull requests service was degraded. Users navigating between tabs on the pull requests dashboard were met with 404 errors or blank pages. This was due to a configuration change deployed on February 27th at 11:03 PM UTC. We mitigated the incident by reverting the change. We’re working to improve monitoring for the page to automatically detect and alert us to routing failures.