Skip to main content

GitHub outage on October 29, 2026: Disruption with Copilot Cloud services

GitHub has reported an incident affecting GitHub since 10:19 UTC on 29 October 2026 (1 hour 52 minutes so far).

github.com All times UTC

Open

Official incident reported by GitHub

Started
10:19
29 Oct 2026 UTC
Status
Open
not resolved yet
Duration
1h 52m
1 hour 52 minutes so far
Impact
Minor
as rated by GitHub
Updates
4
posted by GitHub

Timeline

All times UTC.

Official incident from GitHub

Disruption with Copilot Cloud services

Investigating Minor impact 29 Oct 2026 10:19 UTC View on GitHub's status page
  1. Official
    Investigating

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

  2. Official
    Investigating

    We are experiencing increased failures and latency on our agent sessions service, including creating and listing sessions. This can impact cloud based agent sessions on web, mobile, VS Code, CLI and the GitHub Copilot app.

  3. Official
    Investigating

    We continue to experience failure rates of 1-2% and increased latency on our agent sessions service, including creating and listing sessions. This can impact cloud based agent sessions on web, mobile, VS Code, CLI and the GitHub Copilot app.

  4. Official
    Investigating

    We continue to experience failure rates of 1-2% and increased latency on our agent sessions service, including creating and listing sessions. This can impact cloud based agent sessions on web, mobile, VS Code, CLI and the GitHub Copilot app. We are actively applying mitigations and monitoring for recovery.

"Official" rows are quoted from GitHub's public status page, www.githubstatus.com. Very long posts are shortened.

What our checkpoints saw

HostTracker's checkpoints, which test github.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live GitHub status shows what our checks see right now.

Does your product depend on GitHub?

An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.

You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.

Independent measurement by HostTracker. Not affiliated with GitHub. Official updates are quoted from GitHub's public status page and remain GitHub's own words.