GitHub Enterprise Cloud JP incident

Incident with Pull Requests: High percentage of 500s

Minor Resolved View vendor source →
Started
Mar 31, 2026, 03:05 PM UTC
Resolved
Apr 01, 2026, 01:11 PM UTC
Duration
22h 5m
Detected by Pingoru
Mar 31, 2026, 03:05 PM UTC

Affected components

prod-jpw-01 - Pull Requests (Pull Requests)

Update timeline

  1. investigating Mar 31, 2026, 03:05 PM UTC

    We are investigating reports of degraded performance for Pull Requests

  2. investigating Mar 31, 2026, 03:06 PM UTC

    We are seeing a higher than average number of 500s due to timeouts across GitHub services. We have a potential mitigation in flight and are continuing to investigate.

  3. investigating Mar 31, 2026, 03:39 PM UTC

    We are investigating increased 500 errors affecting GitHub services. You may experience intermittent failures when using Pull Requests and other features. We are actively working to identify and resolve the underlying cause.

  4. investigating Mar 31, 2026, 04:15 PM UTC

    We are continuing to investigate increased 500 errors affecting GitHub services. You may experience intermittent failures when using Pull Requests and other features. We are actively working to identify and resolve the underlying cause.

  5. investigating Mar 31, 2026, 04:35 PM UTC

    We are seeing recovery in latency and timeouts of requests related to pull requests, even though 500s are still elevated. While we are continuing to investigate, we are applying a mitigation and expect further recovery after it is applied.

  6. investigating Mar 31, 2026, 05:16 PM UTC

    We identified an issue causing increased errors when accessing Pull Requests. The mitigation is being applied across our infrastructure and we will continue to provide updates as the mitigation rolls out.

  7. investigating Mar 31, 2026, 06:42 PM UTC

    We continue to experience elevated error rates affecting Pull Requests. An earlier fix resolved one component of the issue, but some users may still encounter intermittent timeouts when viewing or interacting with pull requests. Our teams are actively investigating the remaining causes.

  8. investigating Mar 31, 2026, 07:28 PM UTC

    Error rates remain elevated across multiple pull request endpoints. We are pursuing multiple potential mitigations.

  9. investigating Mar 31, 2026, 09:12 PM UTC

    We continue to see a small subset of repositories experiencing timeouts and elevated latency in Pull Requests, affecting under 1% of requests.

  10. investigating Mar 31, 2026, 09:16 PM UTC

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

  11. resolved Mar 31, 2026, 09:23 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.

  12. investigating Mar 31, 2026, 09:24 PM UTC

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

  13. investigating Mar 31, 2026, 09:28 PM UTC

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

  14. investigating Mar 31, 2026, 10:12 PM UTC

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

  15. resolved Apr 01, 2026, 01:11 PM UTC

    This incident was resolved on Mar 31, 2026 but unintentionally reopened. There is no impact at this time, we apologize for the confusion.

Looking to track GitHub Enterprise Cloud JP downtime and outages?

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

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

5 free monitors · No credit card required