- Level
- confirmed
- Worst impact
- Degraded
- Components
- Codecov Backend
- Regions
- us
- Down Index
- 23of 100
What to do
Check whether you use Codecov Codecov Backend in us. 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 25m it lasted.
Anything that failed between 2025-06-12 18:37 UTC and 2025-06-12 21:03 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 4
- investigating
We are currently investigating latency problems across all of our infrastructure in US regions.
provider
- identified
We have identified the problem as being with our cloud infrastructure provider and have contacted them for further diagnosis. Customer impact is delays in ingestion and intermittent failures for both US customers.
provider
- monitoring
Some of the our cloud infrastructure provider features are back online.
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-709bad7924
Is Codecov still down?
No, this incident was resolved 2025-06-12 21:03 UTC. For Codecov's live state, see https://down.guide/codecov.
How long did it last?
2h 25m, from 2025-06-12 18:37 UTC to 2025-06-12 21:03 UTC, by the times Codecov posted.
What was affected?
Codecov named Codecov Backend in us.
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.