Skip to content

Outage tracker / Codecov

Is Codecov down?

I'm having a problem

Operationalchecked 3 minutes ago

We reached Codecov from all 10 regions we check.

Functional endpoints verified

No outage recorded in the 14 days we have measured Codecov (since Aug 22, 2026).

our independent probeslive · checked Sep 5, 2026, 2:04 AM UTC
US-East196 msOperational
US-West402 msOperational
Europe226 msOperational
Asia-Pacific889 msOperational
US-Central552 msOperational
Canada558 msOperational
UK341 msOperational
Southeast Asia1102 msOperational
Australia397 msOperational
South America289 msOperational
their status pagetheir claim, not our reading

Codecov reports: All systems operational (“All Systems Operational”)

from Codecov's own status page, checked Sep 5, 2026, 1:46 AM UTC
Our probes and Codecov's own status page agree: both show Codecov as reachable right now.

Codecov's own component breakdown, as they publish it

  • Atlassian Bitbucket APIOperational
  • Codecov FrontendOperational
  • GitHub ActionsOperational
  • Google Cloud Platform SQLOperational
  • Atlassian Bitbucket PipelinesOperational
  • Codecov BackendOperational
  • GitHub API RequestsOperational
  • Google Cloud Platform Kubernetes EngineOperational
  • Atlassian Bitbucket WebhooksOperational
  • GitHub Git OperationsOperational
  • Google Cloud Platform Cloud StorageOperational
  • Google Cloud Platform Google Container EngineOperational
  • Google Cloud Platform Google Compute EngineOperational
  • GitHub Pull RequestsOperational
  • GitLabOperational
  • Codecov Billing (Stripe API)Operational
  • GitHub WebhooksOperational
  • Codecov Docs (hosted by ReadMe)Operational

These are Codecov's components, named and scored by Codecov. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Codecov's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Codecov response time, by region

US-East
542msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 475ms2026-08-23 UTC: p95 821ms2026-08-24 UTC: p95 497ms2026-08-25 UTC: p95 472ms2026-08-26 UTC: p95 584ms2026-08-27 UTC: p95 358ms2026-08-28 UTC: p95 516ms2026-08-29 UTC: p95 596ms2026-08-30 UTC: p95 604ms2026-08-31 UTC: p95 694ms2026-09-01 UTC: p95 768ms2026-09-02 UTC: p95 918ms2026-09-03 UTC: p95 944ms2026-09-04 UTC: p95 527ms2026-09-05 UTC: p95 542ms
Aug 7Aug 21Sep 5
US-West
732msp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 468ms2026-08-23 UTC: p95 706ms2026-08-24 UTC: p95 646ms2026-08-25 UTC: p95 538ms2026-08-26 UTC: p95 654ms2026-08-27 UTC: p95 638ms2026-08-28 UTC: p95 1.1s2026-08-29 UTC: p95 900ms2026-08-30 UTC: p95 894ms2026-08-31 UTC: p95 740ms2026-09-01 UTC: p95 704ms2026-09-02 UTC: p95 537ms2026-09-03 UTC: p95 632ms2026-09-04 UTC: p95 790ms2026-09-05 UTC: p95 732ms
Aug 7Aug 21Sep 5
Europe
311msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 494ms2026-08-23 UTC: p95 608ms2026-08-24 UTC: p95 720ms2026-08-25 UTC: p95 597ms2026-08-26 UTC: p95 581ms2026-08-27 UTC: p95 379ms2026-08-28 UTC: p95 529ms2026-08-29 UTC: p95 753ms2026-08-30 UTC: p95 752ms2026-08-31 UTC: p95 488ms2026-09-01 UTC: p95 526ms2026-09-02 UTC: p95 545ms2026-09-03 UTC: p95 432ms2026-09-04 UTC: p95 349ms2026-09-05 UTC: p95 311ms
Aug 7Aug 21Sep 5
Asia-Pacific
998msp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 477ms2026-08-23 UTC: p95 974ms2026-08-24 UTC: p95 506ms2026-08-25 UTC: p95 667ms2026-08-26 UTC: p95 879ms2026-08-27 UTC: p95 775ms2026-08-28 UTC: p95 761ms2026-08-29 UTC: p95 872ms2026-08-30 UTC: p95 702ms2026-08-31 UTC: p95 898ms2026-09-01 UTC: p95 716ms2026-09-02 UTC: p95 708ms2026-09-03 UTC: p95 1.2s2026-09-04 UTC: p95 1.1s2026-09-05 UTC: p95 998ms
Aug 7Aug 21Sep 5
US-Central
602msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 694ms2026-09-04 UTC: p95 645ms2026-09-05 UTC: p95 602ms
Aug 7Aug 21Sep 5
Canada
672msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 680ms2026-09-04 UTC: p95 803ms2026-09-05 UTC: p95 672ms
Aug 7Aug 21Sep 5
UK
398msp95 · latest
500ms250ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 412ms2026-09-04 UTC: p95 358ms2026-09-05 UTC: p95 398ms
Aug 7Aug 21Sep 5
Southeast Asia
1.1sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.1s2026-09-04 UTC: p95 1.0s2026-09-05 UTC: p95 1.1s
Aug 7Aug 21Sep 5
Australia
711msp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.2s2026-09-04 UTC: p95 662ms2026-09-05 UTC: p95 711ms
Aug 7Aug 21Sep 5
South America
463msp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.1s2026-09-04 UTC: p95 757ms2026-09-05 UTC: p95 463ms
Aug 7Aug 21Sep 5

Is it Codecov, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Codecov -- it cannot diagnose Codecov's own systems.

What we measured, function by function

Codecov answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 196msstatus code: 200checked: Sep 5, 2026, 2:04 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Codecov normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 402msstatus code: 200checked: Sep 5, 2026, 1:38 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Codecov normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 552msstatus code: 200checked: Sep 5, 2026, 2:00 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Codecov normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 558msstatus code: 200checked: Sep 5, 2026, 2:01 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Codecov normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 289msstatus code: 200checked: Sep 5, 2026, 1:50 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Codecov normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 226msstatus code: 200checked: Sep 5, 2026, 1:48 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Codecov normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 341msstatus code: 200checked: Sep 5, 2026, 2:04 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Codecov normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 889msstatus code: 200checked: Sep 5, 2026, 1:45 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Codecov normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 1102msstatus code: 200checked: Sep 5, 2026, 1:47 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Codecov normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 397msstatus code: 200checked: Sep 5, 2026, 1:55 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Codecov normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Codecov, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Codecov yet, which is not evidence that nothing is wrong.

Recent outages

Degraded performance on report processing, 50mdeclared on their status page2026-08-13
PR Notifications delayed, 1mdeclared on their status page2026-07-26
Upload processing is severely delayed, 5h 58mdeclared on their status page2026-07-22
Codecov services partially impacted and causing slowdowns, 12h 47mdeclared on their status page2026-07-16
Degraded processing service, 6h 55mdeclared on their status page2026-07-15
Codecov UI showing 400 Bad Request, 3h 3mdeclared on their status page2026-07-08
Codecov uploaders (Action/Orb/Step) fail gpg verification, 1mdeclared on their status page2026-06-06
Integrity verification on the CLI/Action is failing and blocking uploads to Codecov, 20mdeclared on their status page2026-04-23

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Codecov since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Codecov covering any window you pick, with our measurements and Codecov's own claim at the time, side by side.

Full availability history for Codecov: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Codecov, and again when they can reach it again. That is our own measurement from ten regions, not Codecov's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Codecov uptime measured by RealUptimeLive, from this page's own readings.
[![Codecov uptime measured by RealUptime](https://realuptime.io/outages/codecov/badge.svg?days=30)](https://realuptime.io/outages/codecov)
<a href="https://realuptime.io/outages/codecov"><img src="https://realuptime.io/outages/codecov/badge.svg?days=30" alt="Codecov uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Codecov's SLA implies, from our measurement

At or above your target

We measured none of downtime for Codecov over the 338h 7m since we started watching it on 2026-08-22, which is 100% uptime by our reading. A 99.9% target allows 20 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Codecov's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: live API
https://api.codecov.io/api/v2/github/codecov
secondary
https://about.codecov.io/
secondary
https://status.codecov.com/api/v2/status.json
RealUptime is not affiliated with Codecov; the name identifies what we measured, and nothing here speaks for Codecov's own team. We send a single web request to Codecov from 10 regions on our own schedule and time the response. We do not see inside Codecov's systems, do not use an account or real transaction, and are not the same signal Codecov's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Codecov is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.