GitHub Partial Outage Today — Pull Requests Affected (March 2, 2026)

Update: GitHub is currently experiencing a partial outage affecting Pull Requests. Check current GitHub status →

GitHub's Pull Requests component degraded to Partial Outage earlier today. Here's what we know and what you can do while the incident is ongoing.

What's Affected

GitHub has confirmed degraded performance on Pull Requests. This means:

• PR creation may fail or be slow
• PR reviews and comments may not load reliably
• Merge operations could time out or fail
• CI/CD pipelines that trigger on PR events may not fire
• GitHub Actions workflows tied to pull_request events may be delayed

Other GitHub components (Git operations, Issues, Actions, API) appear to be operational at this time.

What's Still Working

• git push / git pull / git clone — Git operations are unaffected
• GitHub Issues — Operational
• GitHub Actions (manually triggered or push-triggered) — Operational
• GitHub Pages — Operational
• GitHub API — Largely operational

What To Do Right Now

For engineering teams:

1. Don't force-merge or manually approve PRs during the outage — you risk creating merge conflicts or missing checks when the system restores
2. Continue working locally — commit and push normally, your code is safe
3. Communicate clearly — let your team know PRs are affected before someone spends 30 minutes debugging a "broken" review tool
4. Monitor GitHub status — statusfield.com/services/github updates every 5 minutes

For CI/CD pipelines:

If your pipeline depends on pull_request webhook events, you may need to trigger runs manually or via push events until the incident resolves. Most modern CI systems (GitHub Actions, CircleCI, etc.) will queue pending jobs and process them when service recovers.

For teams with urgent releases:

If you have a production fix waiting on a PR merge, consider whether you can:

• Merge directly to your release branch via command line (if your branch protection rules allow)
• Temporarily bypass PR requirements for a critical hotfix
• Coordinate with your team to watch for service recovery and merge immediately when it restores

Why GitHub Outages Hit PRs So Hard

Pull Requests are one of GitHub's most complex features — they sit at the intersection of Git data, code review workflows, CI/CD integrations, and notification systems. When any of those underlying systems experiences degradation, PRs are often the first component to show symptoms.

This also means PR outages can mask themselves as other problems: your CI isn't broken, your branch isn't misconfigured — GitHub's review infrastructure is simply under load or experiencing a fault.

How Long Will It Last?

Based on GitHub's historical incident data, partial outages affecting individual components typically resolve within 30–90 minutes. GitHub is usually transparent about recovery timelines once they post an incident update.

We'll continue monitoring and will update this post when the incident resolves.

Never Be Caught Off Guard Again

This incident is a good reminder: if you find out about GitHub outages from your users or from a failed pipeline rather than an alert, you're responding instead of preparing.

Monitor GitHub on Statusfield → and get instant notifications the moment any component changes status — before your team notices.

---

Last updated: March 2, 2026. View live GitHub status