GitHub Enterprise Cloud JP incident
Incident with GitHub Actions
GitHub Enterprise Cloud JP experienced a major incident on July 19, 2026 affecting prod-jpw-01 - API Requests (API Requests) and prod-jpw-01 - Actions (Actions), lasting 5h 9m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 19, 2026, 11:34 PM UTC
We are investigating reports of degraded performance for Actions
- investigating Jul 19, 2026, 11:37 PM UTC
We are investigating degraded availability for GitHub Actions on github.com and in GHEC DR stamps. New workflows may delay or fail to start, and ongoing runs may fail. We will provide more information as soon as we can.
- investigating Jul 19, 2026, 11:57 PM UTC
We have identified the cause of failures in GitHub Actions and are working to restore service.
- investigating Jul 20, 2026, 12:07 AM UTC
API Requests is experiencing degraded availability. We are continuing to investigate.
- investigating Jul 20, 2026, 01:11 AM UTC
We continue to work on mitigative efforts to restore Actions workflow runners, and have observed that the extended downtime has started to cause knock-on effects to other services. A separate incident was opened before we understood they were related. We will continue to post updates on this...
- investigating Jul 20, 2026, 02:34 AM UTC
API Requests is operating normally.
- investigating Jul 20, 2026, 02:43 AM UTC
Issues, API Requests, and Pages have recovered. We are continuing to work on restoring GitHub Actions jobs using self-hosted or larger-hosted runners.
- investigating Jul 20, 2026, 03:27 AM UTC
We’re seeing recovery across all impacted Actions runners. The team is continuing to monitor for global recovery.
- investigating Jul 20, 2026, 03:34 AM UTC
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
- investigating Jul 20, 2026, 04:43 AM UTC
Actions has fully recovered, and we will continue to monitor the platform to ensure stability.
- resolved Jul 20, 2026, 04:44 AM 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.