rewindex

CompaniesGitHub CopilotIncidents

GitHub Copilot: Disruption with Copilot Cloud services

MinorStatus: resolvededitedStarted Resolved (2.5 h)6 updateswww.githubstatus.com (opens in new tab)

Timeline of updates

  1. investigating

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

  2. 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. 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. 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.

  5. monitoring

    The degradation has been mitigated. We are monitoring to ensure stability.

  6. resolvedEdited

    On October 29, 2026, between 05:50 UTC and 12:40 UTC, Copilot agent sessions on GitHub.com and in VS Code were degraded. Live session updates often failed to load, and on average 2.14% of requests to the agent sessions service failed, with a peak of 8.61%. For about 10 minutes around 09:20 UTC, up to 40% of requests to list or create agent sessions failed. Copilot Chat on GitHub.com showed degraded agent session features during this time. The issue occurred when a large increase in task-list requests from a client experiment overloaded the cache that supports the agent sessions service. We mitigated the impact by increasing cache capacity, reducing nonessential load on the cache, and disabling the client experiment. We are moving rate limiting to separate infrastructure, reducing client polling, and improving our alerting so we can detect and respond to this type of overload faster.

Changes Rewindex caught on this incident

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Rewindex captured a newer version after the last checkpoint; the next run () commits it.

Impact, status and times are the vendor’s own, as last archived. View on www.githubstatus.com (opens in new tab).

Cite this

Status incident (vendor impact label: minor) posted by GitHub Copilot, started 2026-10-29 10:22 UTC, resolved after 2.5 h, 6 update(s); edited after publishing.

Title
Disruption with Copilot Cloud services
Vendor
GitHub Copilot
Date
URL
https://rewindex.com/company/github-copilot/incidents/rn76zdy367m2

GitHub Copilot profileRecent GitHub Copilot incidentsAll outages on October 29, 2026GitHub Copilot in October 2026MarkdownJSON