Skip to main content
GitHub

Incident with Pull Requests /pulls

Degraded Lasted 2h 53m · started · GitHub's page

Level
confirmed
Worst impact
Degraded
Components
Pull Requests
Regions
us
Down Index
24of 100

What to do

  • Check whether you use GitHub Pull Requests in us. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 2h 53m it lasted.

    Anything that failed between 2026-03-02 19:11 UTC and 2026-03-02 22:04 UTC may need a replay.
  • Subscribe to GitHub's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=github works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from GitHub 6

  1. investigating

    We are investigating reports of degraded performance for Pull Requests

    provider

  2. investigating

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

    provider

  3. investigating

    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.

    provider

  4. investigating

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

    provider

  5. investigating

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

    provider

  6. resolved

    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.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-013fc808cd

Is GitHub still down?

No, this incident was resolved 2026-03-02 22:04 UTC. For GitHub's live state, see https://down.guide/github.

How long did it last?

2h 53m, from 2026-03-02 19:11 UTC to 2026-03-02 22:04 UTC, by the times GitHub posted.

What was affected?

GitHub named Pull Requests in us.

What caused it?

GitHub hasn't published a root cause. If it does, it shows here.

Where does this come from?

GitHub's official status page, https://www.githubstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.