- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Codecov Frontend
- Down Index
- 34of 100
What to do
Check whether you use Codecov Codecov Frontend. 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 1d 4h it lasted.
Anything that failed between 2026-03-16 11:46 UTC and 2026-03-17 16:07 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 3
- investigating
With identified an issue with our OAuth connection for Bitbucket
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This incident has been resolved. All Bitbucket users will need to login to Codecov again, as their authorizations were reset. Codecov will not be able to commincate with Bitbucket until you do.
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-27fd79a9f9
Is Codecov still down?
No, this incident was resolved 2026-03-17 16:07 UTC. For Codecov's live state, see https://down.guide/codecov.
How long did it last?
1d 4h, from 2026-03-16 11:46 UTC to 2026-03-17 16:07 UTC, by the times Codecov posted.
What was affected?
Codecov named Codecov Frontend.
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.