- Level
- confirmed
- Worst impact
- Degraded
- Components
- Codecov Frontend, Codecov Backend
- Down Index
- 24of 100
What to do
Check whether you use Codecov Codecov Frontend, Codecov Backend. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 9h 23m it lasted.
Anything that failed between 2025-02-26 17:51 UTC and 2025-02-27 03:14 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 2
- investigating
We are currently experiencing issues with sending notifications to Slack due to an ongoing incident: https://slack-status.com/2025-02/1b757d1d0f444c34
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-bc67fa53d9
Is Codecov still down?
No, this incident was resolved 2025-02-27 03:14 UTC. For Codecov's live state, see https://down.guide/providers/codecov.
How long did it last?
9h 23m, from 2025-02-26 17:51 UTC to 2025-02-27 03:14 UTC, by the times Codecov posted.
What was affected?
Codecov named Codecov Frontend, 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.