Vendor record
Codecov
Checked
Front door check counts and Codecov’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We have no front door checks against Codecov in the last 30 days. That does not show whether it was reachable.
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Codecov product, region or your app worked.
How we count front door checksCodecov says
Incident posts from Codecov’s status page, with its titles, impact levels and times. They say what Codecov chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
9
incidents Codecov posted, last 1 year
Median recorded duration: 3h 8m. From 9 incidents with vendor-supplied starts and recorded closure times.
Most recent records · all dates
Codecov app and services are down
CriticalCodecov’s postStarted, per Codecov
Closed in our record(2h 31m)
Degraded performance on report processing
MinorCodecov’s postStarted, per Codecov
Closed in our record(59m)
Upload processing is delayed
MajorCodecov’s postStarted, per Codecov
Closed in our record(7h 7m)
Codecov services partially impacted and causing slowdowns
MinorCodecov’s postStarted, per Codecov
Closed in our record(12h 52m)
Degraded processing service
MajorCodecov’s postStarted, per Codecov
Closed in our record(6h 55m)
4 older records
Codecov UI showing 400 Bad Request
MinorCodecov’s postStarted, per Codecov
Closed in our record(3h 8m)
Integrity verification on the CLI/Action is failing and blocking uploads to Codecov
MinorCodecov’s postStarted, per Codecov
Closed in our record(26m)
Notifications might be delayed
Not specifiedCodecov’s postStarted, per Codecov
Closed in our record(49m)
Coverage notifications delayed
MajorCodecov’s postStarted, per Codecov
Closed in our record(16h 59m)
Your code, your dependencies
See which of your code paths call Codecov
Connect GitHub or GitLab to find where your public or private repository uses Codecov. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add Codecov status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is Codecov currently down?
Codecov's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did Codecov last have an outage?
The most recent closed incident record began 11 days ago and spans 2h 31m. The vendor reported a complete outage. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for Codecov?
No. CheckUpstream does not run front door checks against Codecov. The incident history on this page is what Codecov reported, not a measure of how often it was available.
How do I monitor Codecov in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track Codecov?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.