- 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 23m it lasted.
Anything that failed between 2026-08-10 20:27 UTC and 2026-08-10 21:50 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 6
- investigating
We are investigating reports of impacted performance for some GitHub services.
provider
- monitoring
We are currently investigating reports of some Copilot users experiencing issues accessing certain models. Affected users may see errors or degraded functionality when attempting to use specific models. We are actively working on a fix and will provide updates as we have more information.
provider
- monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
provider
- monitoring
The issue has been mitigated across all affected environments. We are currently deploying on a fix to prevent reoccurrence. We will provide another update once the fix has been deployed.
provider
- monitoring
We have deployed and validated the fix to prevent immediate reoccurrence. We will be performing additional work to limit these kinds of failures in the future.
provider
- resolved
On August 10, 2026, between 19:48 UTC and 20:49 UTC, GitHub Copilot users saw an incomplete list of available models. During this window, the service could return as few as one model instead of the full catalog. Requests that tried to use a model missing from that shortened list failed with a "model not found" error. Copilot requests that used an available model were not affected. This did not affect customers on data-residency (Proxima) environments. The issue was caused by a change to how model data was published, which our systems could not read back correctly and fell back to a limited default list. We mitigated the incident by 20:49 UTC and deployed a fix to prevent immediate recurrence by 21:50 UTC. We are adding validation and retry safeguards so that model data is verified before it is served. We apologize for the disruption.
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-ab53e10115
Is GitHub Copilot still down?
No, this incident was resolved 2026-08-10 21:50 UTC. For GitHub Copilot's live state, see https://down.guide/github-copilot.
How long did it last?
1h 23m, from 2026-08-10 20:27 UTC to 2026-08-10 21:50 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.