GitHub Enterprise Cloud JP incident
Disruption with some GitHub services
Affected components
Update timeline
- investigating Apr 22, 2026, 07:53 PM UTC
We are investigating reports of impacted performance for some GitHub services.
- investigating Apr 22, 2026, 07:55 PM UTC
Issues is experiencing degraded performance. We are continuing to investigate.
- 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.
- 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.
- 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.
- 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.
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
5 free monitors · No credit card required