- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on Codecov. 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 0m it lasted.
Anything that failed between 2026-07-26 05:02 UTC and 2026-07-26 02:30 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 1
- resolved
Server OOM caused drop in PR notifications between 10:48PM ET to 11:20PM ET. PRs expecting notifications during that period have now been manually sent.
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-c6f2178db8
Is Codecov still down?
No, this incident was resolved 2026-07-26 02:30 UTC. For Codecov's live state, see https://down.guide/codecov.
How long did it last?
0m, from 2026-07-26 05:02 UTC to 2026-07-26 02:30 UTC, by the times Codecov posted.
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.