- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Git Operations, Webhooks, API Requests, Issues, Pull Requests, Actions, Copilot, Codespaces
- Down Index
- 48of 100
What to do
Check whether you use GitHub Copilot Git Operations, Webhooks, API Requests, Issues and 4 more. 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 9m it lasted.
Anything that failed between 2026-03-03 18:59 UTC and 2026-03-03 20:09 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 25
- investigating
We are investigating reports of degraded availability for Actions, Copilot and Issues
provider
- investigating
API Requests is experiencing degraded availability. We are continuing to investigate.
provider
- investigating
Pull Requests is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
Webhooks is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
We're seeing some service degradation across GitHub services. We're currently investigating impact.
provider
- investigating
Webhooks is experiencing degraded availability. We are continuing to investigate.
provider
- investigating
Pull Requests is experiencing degraded availability. We are continuing to investigate.
provider
- investigating
Codespaces is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
API Requests is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
API Requests is operating normally.
provider
- investigating
We've identified the issue and have applied a mitigation. We're seeing recovery of services. We continue to montitor for full recovery.
provider
- investigating
Issues is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
Webhooks is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
Codespaces is operating normally.
provider
- investigating
Webhooks is operating normally.
provider
- investigating
Issues is operating normally.
provider
- investigating
Pull Requests is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
Pull Requests is operating normally.
provider
- investigating
Copilot is operating normally.
provider
- investigating
We are seeing recovery across multiple services. Impact is mostly isolated to git operations at this point, we continue to investigate
provider
- investigating
Git Operations is experiencing degraded availability. We are continuing to investigate.
provider
- investigating
Git Operations is operating normally.
provider
- investigating
Actions is operating normally.
provider
- investigating
We're seeing recovery across all services. We're continuing to monitor for full recovery.
provider
- resolved
On March 3, 2026, between 18:46 UTC and 20:09 UTC, GitHub experienced a period of degraded availability impacting GitHub.com, the GitHub API, GitHub Actions, Git operations, GitHub Copilot, and other dependent services. At the peak of the incident, GitHub.com request failures reached approximately 40%. During the same period, approximately 43% of GitHub API requests failed. Git operations over HTTP had an error rate of approximately 6%, while SSH was not impacted. GitHub Copilot requests had an error rate of approximately 21%. GitHub Actions experienced less than 1% impact. This incident shared the same underlying cause as an incident in early February where we saw a large volume of writes to the user settings caching mechanism. While deploying a change to reduce the burden of these writes, a bug caused every user’s cache to expire, get recalculated, and get rewritten. The increased load caused replication delays that cascaded down to all affected services. We mitigated this issue by immediately rolling back the faulty deployment. We understand these incidents disrupted the workflows of developers. While we have made substantial, long-term investments in how GitHub is built and operated to improve resilience, we acknowledge we have more work to do. Getting there requires deep architectural work that is already underway, as well as urgent, targeted improvements. We are taking the following immediate steps: - We have added a killswitch and improved monitoring to the caching mechanism to ensure we are notified before there is user impact and can respond swiftly. - We are moving the cache mechanism to a dedicated host, ensuring that any future issues will solely affect services that rely on it.
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-4e7ea6c10b
Is GitHub Copilot still down?
No, this incident was resolved 2026-03-03 20:09 UTC. For GitHub Copilot's live state, see https://down.guide/github-copilot.
How long did it last?
1h 9m, from 2026-03-03 18:59 UTC to 2026-03-03 20:09 UTC, by the times GitHub Copilot posted.
What was affected?
GitHub Copilot named Git Operations, Webhooks, API Requests, Issues and 4 more.
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.