MicrosoftRadar Independent status for Microsoft services

Disruption with LFS

At a glance · GitHub's status

ResolvedLasted 1 h 4 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 just now

In short

GitHub reported a partial outage affecting GitHub Enterprise Cloud US, starting 15:49 UTC on 8 Jul. GitHub marked it resolved at 16:53 UTC after 1 h 4 min. GitHub has since published a post-incident report.

GitHub says

GitHub's latest update, , in short excerpts.

On July 8, 2026, between 15:07 UTC and 22:13 UTC, multiple GitHub services—including the Web UI, REST API, GraphQL API, Actions, Packages, Copilot, and Git…

GitHub,

Read the full update on GitHub's status page

Timeline

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

  1. 8 Jul

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

  2. +1 h 5 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 July 8, 2026, between 15:07 UTC and 22:13 UTC, multiple GitHub services—including the Web UI, REST API, GraphQL API, Actions, Packages, Copilot, and Git…

  2. Resolved ·

    This incident has been resolved.

  3. Investigating ·

    This impact is related to another ongoing public incident.

  4. Investigating ·

    We believe this LFS outage is related to the concurrent "Services are degraded in some data resident GitHub environments" incident presently occurring in multiple regions.

  5. Investigating ·

    We are investigating disruptions affecting Git Large File Storage (LFS).

  6. Investigating ·

    We are investigating reports of impacted performance for some GitHub services.

Read the full update on GitHub's status page

Last updated