Incident with GitHub Actions
At a glance · GitHub's status
ResolvedLasted 5 h 9 min
- First posted
- on GitHub Enterprise Cloud data residency status
- Ended
- · marked resolved
- Affects
- GitHub Enterprise Cloud Japan
- Edited
- Not since we first saw it
- Source
- GitHub Enterprise Cloud data residency status · checked just now
In short
GitHub reported a partial outage affecting GitHub Enterprise Cloud Japan, starting 23:34 UTC on 19 Jul. GitHub marked it resolved at 04:44 UTC on 20 Jul after 5 h 9 min. GitHub has since published a post-incident report.
GitHub says
GitHub's latest update, , in short excerpts.
Between July 19, 2026, at 23:05 UTC and July 20, 2026, at 03:55 UTC, Actions self-hosted and larger runners were unable to connect to GitHub.
Timeline
Times in UTC, GitHub's own where it gives them.
19 Jul
GitHubFirst public postFrom GitHub's own incident history, before our archive started.
20 Jul+5 h 10 min
GitHubResolved
What GitHub changed
GitHub adds updates to its incidents. We save every version (checked every minute) and list what changed. Quotes are short excerpts. The full text is on GitHub's page.
One version so far. If GitHub edits it, each change shows here with what was removed and added.
First version we captured ·
As first seen: postmortem · 1 service
- Status
- postmortem
- Services
- GitHub Enterprise Cloud Japan
Seen by us · GitHub's timestamp · GitHub's page
Affected services
Official updates
Posted by GitHub Enterprise Cloud data residency status, newest first. The newest are quoted in their first sentence; the full text of each is on GitHub's page.
Post-incident report ·
Between July 19, 2026, at 23:05 UTC and July 20, 2026, at 03:55 UTC, Actions self-hosted and larger runners were unable to connect to GitHub.
Resolved ·
This incident has been resolved.
Investigating ·
Actions has fully recovered, and we will continue to monitor the platform to ensure stability.
Investigating ·
The degradation affecting Actions has been mitigated.
Investigating ·
We’re seeing recovery across all impacted Actions runners.
Investigating ·
Issues, API Requests, and Pages have recovered.
Investigating ·
API Requests is operating normally.
Investigating ·
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…
Investigating ·
API Requests is experiencing degraded availability.
Investigating ·
We have identified the cause of failures in GitHub Actions and are working to restore service.
Show 2 earlier updates
Investigating ·
Investigating ·
Last updated