Incident with several GitHub Services
At a glance · GitHub's status
ResolvedLasted 1 h 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 09:29 UTC on 13 Sep. GitHub marked it resolved at 10:44 UTC after 1 h 15 min. GitHub has since published a post-incident report.
GitHub says
GitHub's latest update, , in short excerpts.
On September 13, 2026, between 08:43 and 10:44 UTC, GitHub experienced degraded availability across approximately 28 services, including Issues, Pull Requests, Actions, Codespaces, Pages, Notifications…
Timeline
Times in UTC, GitHub's own where it gives them.
13 Sep
GitHubFirst public postFrom GitHub's own incident history, before our archive started.
+1 h 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 ·
On September 13, 2026, between 08:43 and 10:44 UTC, GitHub experienced degraded availability across approximately 28 services, including Issues, Pull Requests, Actions, Codespaces, Pages, Notifications…
Resolved ·
This incident has been resolved.
Investigating ·
We have reduced load on this cluster with internal load-shedding and are seeing signs of recovery but continue to monitor
Investigating ·
We're seeing increased database replication delays on collab which is causing increased error rates in authorization endpoints and follow-on increased error rates across the system…
Investigating ·
We are investigating reports of impacted performance for some GitHub services.
Last updated