- 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 2025-01-30 19:42 UTC and 2025-01-28 17:00 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
On 28 January from 12:00 to 30 January 13:00 EST There was a disruption to global upload token validation that resulted in the Codecov system accepting uploads but internally denying the upload. This resulted in failed upload processing for repositories configured to use the global upload token. We now have increased monitoring for this scenario and have put measures in place to prevent it altogether. The underlying issue has been resolved and global upload token uploads should again be working as expected.
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-b2a54a53fc
Is Codecov still down?
No, this incident was resolved 2025-01-28 17:00 UTC. For Codecov's live state, see https://down.guide/codecov.
How long did it last?
0m, from 2025-01-30 19:42 UTC to 2025-01-28 17:00 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.