MicrosoftRadar Independent status for Microsoft services

Incident with Git Operations, Issues, Actions and Pull Requests

At a glance · GitHub's status

ResolvedLasted 47 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 17:17 UTC on 7 Oct. GitHub marked it resolved at 18:04 UTC after 47 min. GitHub has since published a post-incident report.

GitHub says

GitHub's latest update, , in short excerpts.

On October 7, 2026, from 16:52 to 17:01 UTC, GitHub experienced a recurrence of the write-operation outage from earlier that day.

GitHub,

Read the full update on GitHub's status page

Timeline

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

  1. 7 Oct

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

  2. +48 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 ·

    On October 7, 2026, from 16:52 to 17:01 UTC, GitHub experienced a recurrence of the write-operation outage from earlier that day.

  2. Resolved ·

    This incident has been resolved.

  3. Investigating ·

    All systems have recovered.

  4. Investigating ·

    We observed widespread impact across GitHub services from 16:52 UTC to 17:01 UTC, and are investigating the root cause.

  5. Investigating ·

    The degradation has been mitigated.

  6. Investigating ·

    We are investigating reports of degraded performance for Issues and Pull Requests

Read the full update on GitHub's status page

Last updated