Incident with Git Operations
At a glance · GitHub's status
ResolvedLasted 1 h 43 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 degraded service affecting GitHub Enterprise Cloud Japan, starting 20:57 UTC on 3 Nov. GitHub marked it resolved at 22:41 UTC after 1 h 43 min. GitHub has since published a post-incident report.
GitHub says
GitHub's latest update, , in short excerpts.
On November 3, 2026, between 15:00 UTC and 22:37 UTC, Git operations over HTTPS on GitHub.com were degraded.
Timeline
Times in UTC, GitHub's own where it gives them.
3 Nov
GitHubFirst public postFrom GitHub's own incident history, before our archive started.
+1 h 44 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 November 3, 2026, between 15:00 UTC and 22:37 UTC, Git operations over HTTPS on GitHub.com were degraded.
Resolved ·
This incident has been resolved.
Investigating ·
The degradation has been mitigated.
Investigating ·
We are investigating reports of degraded performance for Git Operations
Last updated