Some Copilot Cloud Agent jobs not starting

Summary

Some Copilot Cloud Agent jobs not starting

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.

• Started

  Aug 5, 2026 · 11:38 AM

• Resolved

  Aug 5, 2026 · 1:00 PM

• Duration

  1h 21m

• Severity

  Minor

• ◐

  Investigating

  Aug 5 · 11:38 AM GitHub

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

• ◉

  Monitoring

  Aug 5 · 12:01 PM GitHub

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

• ◉

  Monitoring

  Aug 5 · 12:10 PM GitHub

  Copilot cloud agent jobs have recovered and the backlog of delayed jobs is being processed.

• ✓

  Resolved

  Aug 5 · 1:00 PM GitHub

  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.