- Level
- confirmed
- Worst impact
- Degraded
- Components
- Codecov Backend
- Down Index
- 20of 100
What to do
Check whether you use Codecov Codecov Backend. 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 16m it lasted.
Anything that failed between 2025-01-09 20:24 UTC and 2025-01-09 22:40 UTC may need a replay.Subscribe to Codecov's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=codecov works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Codecov 3
- investigating
We are experiencing high volumes and are seeing some queue back ups resulting in longer than normal notification times.
provider
- monitoring
Queue levels are approaching normal. Notification times should be back to normal as well.
provider
- resolved
This incident has been resolved.
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-e1b92479a8
Is Codecov still down?
No, this incident was resolved 2025-01-09 22:40 UTC. For Codecov's live state, see https://down.guide/codecov.
How long did it last?
2h 16m, from 2025-01-09 20:24 UTC to 2025-01-09 22:40 UTC, by the times Codecov posted.
What was affected?
Codecov named Codecov Backend.
What caused it?
Codecov hasn't published a root cause. If it does, it shows here.
Where does this come from?
Codecov's official status page, https://status.codecov.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.