- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 18of 100
What to do
Check whether your product depends on GitHub Copilot. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1h 21m it lasted.
Anything that failed between 2026-08-05 11:38 UTC and 2026-08-05 13:00 UTC may need a replay.Subscribe to GitHub Copilot's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=github-copilot works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from GitHub Copilot 4
- investigating
We are investigating reports of impacted performance for some GitHub services.
provider
- monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
provider
- monitoring
Copilot cloud agent jobs have recovered and the backlog of delayed jobs is being processed.
provider
- 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. The service recovered when the rate limit window expired. We then tuned the control so it no longer affected unrelated coding agent traffic. 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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-1ba5dac451
Is GitHub Copilot still down?
No, this incident was resolved 2026-08-05 13:00 UTC. For GitHub Copilot's live state, see https://down.guide/github-copilot.
How long did it last?
1h 21m, from 2026-08-05 11:38 UTC to 2026-08-05 13:00 UTC, by the times GitHub Copilot posted.
What caused it?
GitHub Copilot hasn't published a root cause. If it does, it shows here.
Where does this come from?
GitHub Copilot's official status page, https://www.githubstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.