- Level
- confirmed
- Worst impact
- Major outage
- Down Index
- 42of 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 3h 43m it lasted.
Anything that failed between 2026-04-22 15:35 UTC and 2026-04-22 19:18 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 8
- investigating
We are investigating reports of impacted performance for some GitHub services.
provider
- investigating
We are aware of users seeing errors interacting with Copilot chat on github.com and Copilot cloud agent. We have identified the cause and are investigating remediations.
provider
- investigating
We continue to work on mitigation for Copilot chat and cloud agent.
provider
- investigating
Mitigation is progressing for Copilot chat and cloud agent.
provider
- investigating
Mitigation is progressing for Copilot chat and cloud agent recovery.
provider
- investigating
We are now seeing recovery for Copilot cloud agent.
provider
- investigating
Copilot cloud agent and chat are mitigated for github.com.
provider
- resolved
On April 22, 2026, between 15:16 UTC and 19:18 UTC, users experienced errors when interacting with Copilot Chat on github.com and Copilot Cloud Agent. During this time, users were unable to use Copilot Chat or Copilot Cloud Agent. Copilot Memory (in preview) was not available to Copilot agent sessions during this time. The issue was caused by an infrastructure configuration change that resulted in connectivity issues with our databases. The team identified the cause and restored connectivity to the database. Copilot Chat and Cloud Agent for github.com were restored by 18:16 UTC. Remaining regional deployments were restored incrementally, with full resolution at 19:18 UTC. We have taken steps to prevent similar infrastructure changes from causing these kinds of database operations 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-f0653f9dc7
Is GitHub Copilot still down?
No, this incident was resolved 2026-04-22 19:18 UTC. For GitHub Copilot's live state, see https://down.guide/github-copilot.
How long did it last?
3h 43m, from 2026-04-22 15:35 UTC to 2026-04-22 19:18 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.