Skip to main content
Codecov

Queue backup resulting in delayed reporting

Degraded Lasted 2h 52m · started · Codecov's page

Level
confirmed
Worst impact
Degraded
Components
Codecov Backend
Down Index
21of 100

What to do

  • Check whether you use Codecov Codecov Backend. 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 52m it lasted.

    Anything that failed between 2025-01-16 18:58 UTC and 2025-01-16 21:50 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

  1. investigating

    We are currently investigating this issue.

    provider

  2. monitoring

    A fix has been implemented and we are monitoring the results.

    provider

  3. 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-b5e58a34fd

Is Codecov still down?

No, this incident was resolved 2025-01-16 21:50 UTC. For Codecov's live state, see https://down.guide/codecov.

How long did it last?

2h 52m, from 2025-01-16 18:58 UTC to 2025-01-16 21:50 UTC, by the times Codecov posted.

What was affected?

Codecov named Codecov Backend.

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.