MicrosoftRadar Independent status for Microsoft services

Incident with Pull Requests

At a glance · GitHub's status

ResolvedLasted 1 h 52 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 19:50 UTC on 23 Apr. GitHub marked it resolved at 21:43 UTC after 1 h 52 min. GitHub has since published a post-incident report.

GitHub says

GitHub's latest update, , in short excerpts.

On April 23, 2026, between 16:05 UTC and 20:43 UTC, the Pull Requests service experienced a regression affecting merge queue operations.

GitHub,

Read the full update on GitHub's status page

Timeline

Times in UTC, GitHub's own where it gives them.

  1. 23 Apr

    GitHubFirst public postFrom GitHub's own incident history, before our archive started.

  2. +1 h 53 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.

  1. 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.

  1. Post-incident report ·

    On April 23, 2026, between 16:05 UTC and 20:43 UTC, the Pull Requests service experienced a regression affecting merge queue operations.

  2. Resolved ·

    This incident has been resolved.

  3. Investigating ·

    Pull Requests is operating normally.

  4. Investigating ·

    We have identified a regression in merge queue behavior present when squash merging or rebasing.

  5. Investigating ·

    We are investigating reports of degraded performance for Pull Requests

Read the full update on GitHub's status page

Last updated