Disruption with Copilot Cloud services

At a glance · GitHub's status

ResolvedLasted 2 h 29 min

First posted
on GitHub Enterprise Cloud data residency status
Ended
· marked resolved
Affects
GitHub Enterprise Cloud Australia
Edited
Not since we first saw it
Source
GitHub Enterprise Cloud data residency status · checked 1 min ago

In short

GitHub reported degraded service affecting GitHub Enterprise Cloud Australia, starting 10:19 UTC on 29 Oct. GitHub marked it resolved at 12:49 UTC after 2 h 29 min. GitHub has since published a post-incident report.

GitHub says

GitHub's latest update, , in short excerpts.

On October 29, 2026, between 05:50 UTC and 12:40 UTC, Copilot agent sessions on GitHub.com and in VS Code were degraded.

GitHub,

Read the full update on GitHub's status page

Timeline

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

  1. 29 Oct

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

  2. +2 h 30 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 Australia

    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 29, 2026, between 05:50 UTC and 12:40 UTC, Copilot agent sessions on GitHub.com and in VS Code were degraded.

  2. Resolved ·

    This incident has been resolved.

  3. Investigating ·

    The degradation has been mitigated.

  4. Investigating ·

    We continue to experience failure rates of 1-2% and increased latency on our agent sessions service, including creating and listing sessions.

  5. Investigating ·

    We continue to experience failure rates of 1-2% and increased latency on our agent sessions service, including creating and listing sessions.

  6. Investigating ·

    We are experiencing increased failures and latency on our agent sessions service, including creating and listing sessions.

  7. Investigating ·

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

Read the full update on GitHub's status page

Last updated