Incident with Pull Requests: High percentage of 500s
At a glance · GitHub's status
ResolvedLasted 22 h 5 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 15:05 UTC on 31 Mar. GitHub marked it resolved at 13:11 UTC on 1 Apr after 22 h 5 min. GitHub has since published a post-incident report.
GitHub says
GitHub's latest update, , in short excerpts.
On Monday March 31st, 2026, between 13:53 UTC and 21:23 UTC the Pull Requests service experienced elevated latency and failures.
Timeline
Times in UTC, GitHub's own where it gives them.
31 Mar
GitHubFirst public postFrom GitHub's own incident history, before our archive started.
1 Apr+22 h 6 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 Monday March 31st, 2026, between 13:53 UTC and 21:23 UTC the Pull Requests service experienced elevated latency and failures.
Resolved ·
This incident was resolved on Mar 31, 2026 but unintentionally reopened.
Investigating ·
The degradation has been mitigated.
Investigating ·
The degradation has been mitigated.
Investigating ·
The degradation has been mitigated.
Resolved ·
This incident has been resolved.
Investigating ·
The degradation affecting Pull Requests has been mitigated.
Investigating ·
We continue to see a small subset of repositories experiencing timeouts and elevated latency in Pull Requests, affecting under 1% of requests.
Investigating ·
Error rates remain elevated across multiple pull request endpoints.
Investigating ·
We continue to experience elevated error rates affecting Pull Requests.
Investigating ·
We identified an issue causing increased errors when accessing Pull Requests.
Show 5 earlier updates
Investigating ·
Investigating ·
Investigating ·
Investigating ·
Investigating ·
Last updated