Incident triggering Actions runs in data residency environments
At a glance · GitHub's status
ResolvedLasted 15 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 1 min ago
In short
GitHub reported a partial outage affecting GitHub Enterprise Cloud Japan, starting 22:16 UTC on 1 Jul. GitHub marked it resolved at 22:32 UTC after 15 min. GitHub has since published a post-incident report.
GitHub says
GitHub's latest update, , in short excerpts.
From 21:16 UTC to 22:32 UTC on July 1, the creation of new merge commits for pull requests failed for customers using GitHub Enterprise Cloud…
Timeline
Times in UTC, GitHub's own where it gives them.
1 Jul
GitHubFirst public postFrom GitHub's own incident history, before our archive started.
+16 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 ·
From 21:16 UTC to 22:32 UTC on July 1, the creation of new merge commits for pull requests failed for customers using GitHub Enterprise Cloud…
Resolved ·
This incident has been resolved.
Investigating ·
The degradation affecting Actions has been mitigated.
Investigating ·
We are investigating reports of degraded performance for Actions
Last updated