Skip to main content
Codecov logo

Is Codecov Down?

No — Codecov is up

Reachable from all 8 checked regions

Average response time: 287ms

Last checked · checks run every 6 hours

Official status page: https://status.codecov.com

Codecov uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
358ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 19 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

19-day clean streak
Sep 14: no data
Sep 15: no data
Sep 16: no data
Sep 17: no data
Sep 18: no data
Sep 19: no data
Sep 20: no data
Sep 21: no data
Sep 22: no data
Sep 23: no data
Sep 24: no data
Sep 25: 100.00% uptime, 16 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 31 checks
Sep 30: 100.00% uptime, 31 checks
Oct 1: 100.00% uptime, 32 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 24 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
205ms
DNS 41ms TCP 2ms TLS 9ms TTFB 204ms
arn
256ms
DNS 74ms TCP 1ms TLS 7ms TTFB 255ms
cdg
320ms
DNS 164ms TCP 1ms TLS 10ms TTFB 320ms
dfw
205ms
DNS 108ms TCP 2ms TLS 7ms TTFB 204ms
ewr
120ms
DNS 30ms TCP 2ms TLS 9ms TTFB 119ms
fra
256ms
DNS 64ms TCP 1ms TLS 9ms TTFB 255ms
syd
633ms
DNS 333ms TCP 1ms TLS 6ms TTFB 633ms
yyz
303ms
DNS 208ms TCP 1ms TLS 6ms TTFB 302ms

What Codecov does

Codecov is a code coverage service. CI jobs upload test coverage reports with the Codecov CLI, GitHub Action, CircleCI Orb or Bitrise Step, and Codecov turns them into pull request comments and codecov/project and codecov/patch status checks on GitHub, GitLab and Bitbucket. Teams use those checks to block pull requests that lower coverage. Sentry bought Codecov in 2022; Harness acquired it from Sentry in June 2026.

What an outage looks like

Coverage comments and codecov/project or codecov/patch statuses arrive hours late or not at all, because uploads are accepted but sit in a processing backlog. The app.codecov.io dashboard shows errors such as 400 Bad Request, or Bitbucket login fails. In CI the upload step itself can fail, as it did when the Action's integrity check broke in April 2026 and its gpg verification broke in June 2026.

What to do about it

Check status.codecov.com: Codecov Backend covers upload processing, Codecov Frontend the web app, and separate rows track GitHub, Bitbucket and GitLab. During a processing backlog you do not need to re-upload; in past incidents uploads were still accepted, no data was lost and delayed notifications arrived as the queue cleared. If a failed upload is failing your build, check whether your workflow sets fail_ci_if_error to true.

Is it down for everyone, or just you?

If this page says Codecov is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

GitHub
GitHub
Harness
Harness
SonarQube Cloud
SonarQube Cloud
Bitbucket
Bitbucket

Codecov outage FAQ

Will a Codecov outage fail my CI build?
Not by default. In the Codecov GitHub Action, fail_ci_if_error defaults to false, so a failed upload does not make the step exit with an error. The Action's README examples set it to true, though, and with that setting a Codecov outage turns every job red. Set it to false temporarily to unblock merges, or keep it and wait for status.codecov.com to show recovery.
Is coverage data lost when Codecov processing is delayed?
Not in recent incidents. During the February 2026 upload processing slowdown, Codecov said uploads were still being accepted, results would take longer to appear, and no data had been lost. During the July 22, 2026 backlog it reported the queue clearing and told early-affected users to expect their notifications. After a short drop on July 26, missed pull request notifications were sent manually.
Why is the Codecov status check missing on my pull request?
Usually a processing backlog. Codecov posts codecov/project and codecov/patch after it processes your upload, and most Codecov incidents in 2026 were delays in upload processing or pull request notifications rather than the website going down. Check the Codecov Backend row on status.codecov.com. If no report arrived at all, your if_not_found setting decides whether the status fails or passes.
Does a GitHub outage affect Codecov?
Yes. Codecov's pull request comments and status checks go through GitHub, and its status page tracks GitHub Actions, API Requests, Git Operations, Pull Requests and Webhooks as rows of their own. When those are degraded, Codecov results can stall even though Codecov is healthy. Bitbucket and GitLab have rows too; after a March 2026 Bitbucket OAuth incident, every Bitbucket user had to log in to Codecov again.
Who owns Codecov now?
Harness. Sentry acquired Codecov in November 2022, and Harness announced on June 2, 2026 that it had acquired Codecov from Sentry, saying it would keep the brand and free access for open source projects. The website terms on about.codecov.io now name Harness Inc. as the operator. Sign-in with Sentry is still offered, and the status page remains at status.codecov.com.

How we measure this

  • We request Codecov's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Codecov publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Codecov goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required