- Level
- confirmed
- Worst impact
- Degraded
- Components
- Copilot
- Down Index
- 30of 100
What to do
Check whether you use GitHub Copilot 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 2h 43m it lasted.
Anything that failed between 2026-04-01 09:58 UTC and 2026-04-01 12:41 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 9
- investigating
We are investigating reports of degraded performance for Copilot
provider
- investigating
We are investigating reports of issues with service(s): Copilot Dotcom Agents. We will continue to keep users updated on progress towards mitigation.
provider
- investigating
Users may see increased latency and intermittent errors when viewing or creating agent sessions. We are working on mitigations to return to baseline performance and success rate.
provider
- monitoring
The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability.
provider
- monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
provider
- monitoring
The success rate for creating and viewing agent sessions has stabilized, and we're continuing to monitor latency, which is trending toward baseline levels.
provider
- monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
provider
- monitoring
The success rate and latency for creating and viewing agent sessions has stabilized at baseline levels, we are continuing to monitor recovery
provider
- resolved
On April 1, 2026, between 07:29 and 12:41 UTC, some customers experienced elevated 5xx errors and increased latency when using GitHub Copilot features that rely on `/agents/sessions` endpoints (including creating or viewing agent sessions). The issue was caused by resource exhaustion in one of the Copilot backend services handling these requests, in turn, causing timeouts and failed requests. We mitigated the incident by increasing the service’s available compute resources and tuning its runtime concurrency settings. Service health returned to normal and the incident was fully resolved by 12:41 UTC.
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-6ddd959c36
Is GitHub Copilot still down?
No, this incident was resolved 2026-04-01 12:41 UTC. For GitHub Copilot's live state, see https://down.guide/github-copilot.
How long did it last?
2h 43m, from 2026-04-01 09:58 UTC to 2026-04-01 12:41 UTC, by the times GitHub Copilot posted.
What was affected?
GitHub Copilot named Copilot.
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.