Is GitHub Copilot down? October 29 cloud agent sessions disruption resolved after 2 hours 30 minutes

What happened and when

GitHub's status page reported an incident titled Disruption with Copilot Cloud services on October 29, 2026. The first update, posted at 10:19 UTC, said GitHub was investigating reports of impacted performance for some GitHub services. The incident was marked resolved at 12:49 UTC, about 2 hours 30 minutes after that first post.

At 10:22 UTC GitHub said its agent sessions service had increased failures and latency, including when creating and listing sessions.

Sources: Disruption with Copilot Cloud services

Which Copilot surfaces could be affected

According to the status page, the issue can impact cloud based agent sessions on web, mobile, VS Code, CLI and the GitHub Copilot app. The page does not say which of those surfaces actually had failures.

The updates posted at 11:01 and 11:37 UTC said failure rates were still 1-2%, with increased latency on the agent sessions service. Earlier and later posts give no failure rate.

The status page names only the agent sessions service and cloud based agent sessions. It does not list any other Copilot features as affected.

Sources: Disruption with Copilot Cloud services

Recovery and what comes next

At 11:37 UTC GitHub said it was actively applying mitigations and monitoring for recovery. At 12:33 UTC it reported that the degradation had been mitigated and that it was monitoring for stability. It marked the incident resolved at 12:49 UTC.

GitHub says a detailed root cause analysis will be shared once it is available. The status page does not say whether sessions that failed during the incident used AI Credits, and it does not mention any refunds or billing adjustments.

Sources: Disruption with Copilot Cloud services