Incident with Pull Requests

At a glance · GitHub's status

ResolvedLasted 13 h 12 min

First posted
on GitHub Enterprise Cloud data residency status
Ended
· marked resolved
Affects
GitHub Enterprise Cloud US
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 US, starting 11:58 UTC on 15 Oct. GitHub marked it resolved at 01:10 UTC on 16 Oct after 13 h 12 min. GitHub has since published a post-incident report.

GitHub says

GitHub's latest update, , in short excerpts.

Between October 14, 2026, at 20:55 UTC and October 16, 2026, at 01:10 UTC, multiple customers using GitHub Enterprise Cloud with data residency in the…

GitHub,

Read the full update on GitHub's status page

Timeline

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

  1. 15 Oct

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

  2. 16 Oct+13 h 12 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 US

    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 ·

    Between October 14, 2026, at 20:55 UTC and October 16, 2026, at 01:10 UTC, multiple customers using GitHub Enterprise Cloud with data residency in the…

  2. Resolved ·

    This incident has been resolved.

  3. Investigating ·

    The reconciliation process is complete and all pull request data is accurately reflected in the pull request list.

  4. Investigating ·

    The complete reconciliation effort for all pull request data is still underway and expected to complete within 6 hours (by 2026-10-16 04:00 UTC), but self-healing…

  5. Investigating ·

    The complete reconciliation effort for all pull request data is expected to complete within 8 hours (by 2026-10-16 04:00 UTC), but self-healing mechanisms will restore…

  6. Investigating ·

    Partial mitigation is complete after cutting over to our new infrastructure, so newly created and updated pull requests should now be reflected in pull requests…

Show 7 earlier updates
  1. Investigating ·

  2. Investigating ·

  3. Investigating ·

  4. Investigating ·

  5. Investigating ·

  6. Investigating ·

  7. Investigating ·

Read the full update on GitHub's status page

Last updated