GitHub incident

Incident with Pull Requests

Minor Resolved View vendor source →
Started
Apr 23, 2026, 09:43 PM UTC
Resolved
Apr 23, 2026, 09:43 PM UTC
Duration
Detected by Pingoru
Apr 23, 2026, 09:43 PM UTC

Affected components

Pull Requests

Update timeline

  1. investigating Apr 23, 2026, 07:50 PM UTC

    We are investigating reports of degraded performance for Pull Requests

  2. investigating Apr 23, 2026, 07:58 PM UTC

    We have identified a regression in merge queue behavior present when squash merging or rebasing. We have identified the root-cause and are in the process of reverting the change.

  3. investigating Apr 23, 2026, 08:47 PM UTC

    Pull Requests is operating normally.

  4. investigating Apr 23, 2026, 09:18 PM UTC

    We have resolved a regression present when using merge queue with either squash merges or rebases. If you use merge queue in this configuration, some pull requests may have been merged incorrectly between 2026-04-23 16:05-20:43 UTC. This behavior is still present in GitHub Enterprise Cloud with Data Residency, and we are rolling out the same fix.

  5. resolved Apr 23, 2026, 09:43 PM UTC

    This incident has been resolved and we've contacted repository administrators via email who have impacted branches. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will also be shared as soon as it is available.

Looking to track GitHub downtime and outages?

Pingoru polls GitHub's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when GitHub reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track GitHub alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring GitHub for free

5 free monitors · No credit card required