GitHub Enterprise Cloud JP Outage History

GitHub Enterprise Cloud JP is up right now

There were 7 GitHub Enterprise Cloud JP outages since March 31, 2026 totaling 31h 17m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://jp.githubstatus.com/posts/dashboard

Minor April 23, 2026

Incident with Pull Requests

Detected by Pingoru
Apr 23, 2026, 07:50 PM UTC
Resolved
Apr 23, 2026, 09:43 PM UTC
Duration
1h 52m
Affected: prod-jpw-01 - Pull Requests (Pull Requests)
Timeline · 4 updates
  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, 09:43 PM UTC

    Pull Requests is operating normally.

  4. resolved Apr 23, 2026, 09:43 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.

Read the full incident report →

Minor April 23, 2026

Disruption with users unable to start Claude and Codex agent task from the web

Detected by Pingoru
Apr 23, 2026, 07:29 PM UTC
Resolved
Apr 23, 2026, 07:42 PM UTC
Duration
13m
Timeline · 3 updates
  1. investigating Apr 23, 2026, 07:29 PM UTC

    We are investigating reports of impacted performance for some GitHub services.

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

    We have identified the root cause of the issue and are working on mitigation.

  3. resolved Apr 23, 2026, 07:42 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.

Read the full incident report →

Minor April 22, 2026

Disruption with some GitHub services

Detected by Pingoru
Apr 22, 2026, 07:53 PM UTC
Resolved
Apr 22, 2026, 10:43 PM UTC
Duration
2h 50m
Affected: prod-jpw-01 - Issues (Issues)
Timeline · 6 updates
  1. investigating Apr 22, 2026, 07:53 PM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. investigating Apr 22, 2026, 07:55 PM UTC

    Issues is experiencing degraded performance. We are continuing to investigate.

  3. investigating Apr 22, 2026, 08:02 PM UTC

    Copilot @-mentions on pull requests are currently not being processed by Copilot Cloud Agent. We have found the issue and are investigating remediations.

  4. investigating Apr 22, 2026, 08:37 PM UTC

    We have identified the root cause of the disruption affecting Copilot Coding Agent and Issues. Copilot @-mentions on pull requests are not being processed, and some issue-related functionality may be degraded. A fix has been developed and is being applied.

  5. investigating Apr 22, 2026, 10:09 PM UTC

    We have identified the root cause of the disruption affecting Copilot Coding Agent and Issues. A fix is being deployed.

  6. resolved Apr 22, 2026, 10:43 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.

Read the full incident report →

Major April 22, 2026

Disruption with Copilot chat and Copilot Coding Agent

Detected by Pingoru
Apr 22, 2026, 03:35 PM UTC
Resolved
Apr 22, 2026, 07:18 PM UTC
Duration
3h 42m
Timeline · 8 updates
  1. investigating Apr 22, 2026, 03:35 PM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. investigating Apr 22, 2026, 03:43 PM UTC

    We are aware of users seeing errors interacting with Copilot chat on github.com and Copilot cloud agent. We have identified the cause and are investigating remediations.

  3. investigating Apr 22, 2026, 04:24 PM UTC

    We continue to work on mitigation for Copilot chat and cloud agent.

  4. investigating Apr 22, 2026, 04:58 PM UTC

    Mitigation is progressing for Copilot chat and cloud agent.

  5. investigating Apr 22, 2026, 05:40 PM UTC

    Mitigation is progressing for Copilot chat and cloud agent recovery.

  6. investigating Apr 22, 2026, 05:49 PM UTC

    We are now seeing recovery for Copilot cloud agent.

  7. investigating Apr 22, 2026, 06:05 PM UTC

    Copilot cloud agent and chat are mitigated for github.com.

  8. resolved Apr 22, 2026, 07:18 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.

Read the full incident report →

Minor April 10, 2026

Problems with third-party Claude and Codex Agent sessions not being listed in the agents tab dashboard

Detected by Pingoru
Apr 10, 2026, 01:07 PM UTC
Resolved
Apr 10, 2026, 01:28 PM UTC
Duration
21m
Timeline · 3 updates
  1. investigating Apr 10, 2026, 01:07 PM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. investigating Apr 10, 2026, 01:08 PM UTC

    We are investigating third party Claude and Codex Cloud Agent sessions not being listed in the agents tab dashboard.

  3. resolved Apr 10, 2026, 01:28 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.

Read the full incident report →

Minor April 2, 2026

Copilot Coding Agent failing to start some jobs

Detected by Pingoru
Apr 02, 2026, 04:18 PM UTC
Resolved
Apr 02, 2026, 04:30 PM UTC
Duration
12m
Timeline · 3 updates
  1. investigating Apr 02, 2026, 04:18 PM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. investigating Apr 02, 2026, 04:28 PM UTC

    When assigning tasks to Copilot Cloud Agent, the task will appear to be working, but may not actually be running. We are investigating.

  3. resolved Apr 02, 2026, 04:30 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.

Read the full incident report →

Minor March 31, 2026

Incident with Pull Requests: High percentage of 500s

Detected by Pingoru
Mar 31, 2026, 03:05 PM UTC
Resolved
Apr 01, 2026, 01:11 PM UTC
Duration
22h 5m
Affected: prod-jpw-01 - Pull Requests (Pull Requests)
Timeline · 15 updates
  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.

Read the full incident report →

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