- Level
- confirmed
- Worst impact
- Operational
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-06-06 13:00 UTC and 2026-06-06 13: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 Saturday, June 6th, the Codecov gpg public key located at keybase.io/codecovsecurity was absent. This caused widespread outages for users uploading with the Codecov - GitHub Action - CircleCI Orb - Bitrise Step In order to quickly move and prevent further outages, the Codecov team deleted the codecovsecurity account and created codecovsecops with the same public gpg key. This key can be verified against any pre-existing CLI to prove it is the same key and also at about.codecov.io/security. The key location was updated in all of the above uploaders on the latest versions.
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-d235e17117
Is Codecov still down?
No, this incident was resolved 2026-06-06 13:00 UTC. For Codecov's live state, see https://down.guide/providers/codecov.
How long did it last?
0m, from 2026-06-06 13:00 UTC to 2026-06-06 13: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.