GitHub Copilot incident
Some Copilot Cloud Agent jobs not starting
Started
August 5, 2026 at 11:38 AM UTC
Duration
1h 21m
Resolved
August 5, 2026 at 01:00 PM UTC
Updates timeline
- Investigating
We are investigating reports of impacted performance for some GitHub services.
- Monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
- Monitoring
Copilot cloud agent jobs have recovered and the backlog of delayed jobs is being processed.
- Resolved
On August 5, 2026, between 11:02 and 11:54 UTC, the GitHub Copilot cloud agent service was degraded and new cloud agent jobs were delayed from starting. During this period 100% of newly submitted agent jobs were affected. The incident was limited to delay of cloud agent jobs. No jobs were lost and the queued backlog was processed by 13:00 UTC. This was due to an internal rate limit used to protect service availability that was enabled more broadly than intended delaying more traffic than expected. <br /> <br />The service recovered when the rate limit window expired. We then tuned the control so it no longer affected unrelated coding agent traffic. <br /> <br />We are working to improve the control's scoping and our monitoring and alerting to reduce our time to detection and mitigation of similar issues in the future.
Get an email the next time GitHub Copilot goes down
Outage alerts for GitHub Copilot, straight to your inbox. No account needed, unsubscribe in every email.
Watching more than one service? A free account covers 5 services + a daily digest — and Pro is currently free.
Live GitHub Copilot status
Current indicator + 24h latency
All incidents
Cross-service timeline
Subscribe via RSS
Atom feed for any reader