GitHub Copilot Cloud Agent Service Incident on April 2, 2026
By
bhouston
The bagel they save for the regulars. Don't skim, savour.
Summary
GitHub experienced a service incident on April 2, 2026, where Copilot Cloud Agent entered a period of reduced performance between 15:20 and 20:18 UTC. The issue was caused by an internal feature being developed for Copilot Code Review, which led to an increased number of jobs being sent to the Copilot Cloud Agent infrastructure. This load eventually triggered an internal rate limit, causing all work to suspend for an hour. The incident has been resolved, and this appears to be part of GitHub's status page documenting system performance incidents.
Key quotes
· 4 pulledBetween 15:20 and 20:18 UTC on Thursday April 2, Copilot Cloud Agent entered a period of reduced performance.
Due to an internal feature being developed for Copilot Code Review, the Copilot Cloud Agent infrastructure started to receive an increased number of jobs.
This load eventually caused us to hit an internal rate limit, causing all work to suspend for an hour.
Welcome to GitHub's home for real-time and historical data on system performance.
You might also wanna read
GitHub Copilot: A Powerful AI Tool for Debugging Code
The article explores how GitHub Copilot, an AI-powered coding assistant, can significantly streamline the debugging process for developers.
GitHub·1y ago
How to prevent GitHub Copilot CLI from being interrupted by computer sleep settings
The article discusses how aggressive power settings on modern computers can interrupt GitHub Copilot CLI tasks when users walk away. The aut
josephguadagno.net·1d ago
GitHub Actions suffers three-hour outage with false 'account suspended' error
GitHub Actions experienced a major outage lasting over three hours, during which users saw an alarming but incorrect error message stating "
theregister.com·2d ago