Skip to content

Outage tracker / Codecov

Is Codecov down?

I'm having a problem

Vendor reports no incidentWhat Codecov reports

Codecov reports no incident on its status page.

As of the last successful poll, 2026-11-05 14:34 UTC.

Codecov's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked moments ago

Our checks of Codecov pass from all 10 regions we check.

As of Nov 5, 2026, 2:35 PM UTC, RealUptime's checks of Codecov passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 2:35 PM UTC
US-East312 msChecks passing
US-West1111 msChecks passing
Europe811 msChecks passing
Asia-Pacific1543 msChecks passing
US-Central294 msChecks passing
Canada932 msChecks passing
UK180 msChecks passing
Southeast Asia276 msChecks passing
Australia375 msChecks passing
South America506 msChecks passing
their status pagetheir claim, not our reading

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

from Codecov's own status page, checked Nov 5, 2026, 1:56 PM UTC
Codecov's own status page shows no incident, and our checks of Codecov pass 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
1.4sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 314ms2026-10-08 UTC: p95 282ms2026-10-09 UTC: p95 312ms2026-10-10 UTC: p95 381ms2026-10-11 UTC: p95 447ms2026-10-12 UTC: p95 455ms2026-10-13 UTC: p95 404ms2026-10-14 UTC: p95 364ms2026-10-15 UTC: p95 286ms2026-10-16 UTC: p95 382ms2026-10-17 UTC: p95 397ms2026-10-18 UTC: p95 979ms2026-10-19 UTC: p95 775ms2026-10-20 UTC: p95 411ms2026-10-21 UTC: p95 328ms2026-10-22 UTC: p95 398ms2026-10-23 UTC: p95 534ms2026-10-24 UTC: p95 249ms2026-10-25 UTC: p95 242ms2026-10-26 UTC: p95 371ms2026-10-27 UTC: p95 371ms2026-10-28 UTC: p95 355ms2026-10-29 UTC: p95 313ms2026-10-30 UTC: p95 405ms2026-10-31 UTC: p95 424ms2026-11-01 UTC: p95 510ms2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.6s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
US-West
3.2sp95 · latest
5s2.5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 430ms2026-10-08 UTC: p95 452ms2026-10-09 UTC: p95 426ms2026-10-10 UTC: p95 423ms2026-10-11 UTC: p95 442ms2026-10-12 UTC: p95 474ms2026-10-13 UTC: p95 538ms2026-10-14 UTC: p95 458ms2026-10-15 UTC: p95 429ms2026-10-16 UTC: p95 465ms2026-10-17 UTC: p95 542ms2026-10-18 UTC: p95 545ms2026-10-19 UTC: p95 640ms2026-10-20 UTC: p95 541ms2026-10-21 UTC: p95 676ms2026-10-22 UTC: p95 814ms2026-10-23 UTC: p95 545ms2026-10-24 UTC: p95 505ms2026-10-25 UTC: p95 467ms2026-10-26 UTC: p95 517ms2026-10-27 UTC: p95 482ms2026-10-28 UTC: p95 629ms2026-10-29 UTC: p95 759ms2026-10-30 UTC: p95 557ms2026-10-31 UTC: p95 750ms2026-11-01 UTC: p95 574ms2026-11-02 UTC: p95 2.0s2026-11-03 UTC: p95 2.4s2026-11-04 UTC: p95 2.3s2026-11-05 UTC: p95 3.2s
Oct 7Oct 21Nov 5
Europe
918msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 357ms2026-10-08 UTC: p95 340ms2026-10-09 UTC: p95 330ms2026-10-10 UTC: p95 400ms2026-10-11 UTC: p95 405ms2026-10-12 UTC: p95 415ms2026-10-13 UTC: p95 448ms2026-10-14 UTC: p95 412ms2026-10-15 UTC: p95 942ms2026-10-16 UTC: p95 465ms2026-10-17 UTC: p95 428ms2026-10-18 UTC: p95 507ms2026-10-19 UTC: p95 456ms2026-10-20 UTC: p95 417ms2026-10-21 UTC: p95 451ms2026-10-22 UTC: p95 443ms2026-10-23 UTC: p95 442ms2026-10-24 UTC: p95 342ms2026-10-25 UTC: p95 348ms2026-10-26 UTC: p95 357ms2026-10-27 UTC: p95 358ms2026-10-28 UTC: p95 509ms2026-10-29 UTC: p95 384ms2026-10-30 UTC: p95 684ms2026-10-31 UTC: p95 401ms2026-11-01 UTC: p95 358ms2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 1.7s2026-11-04 UTC: p95 1.8s2026-11-05 UTC: p95 918ms
Oct 7Oct 21Nov 5
Asia-Pacific
3.0sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 491ms2026-10-08 UTC: p95 419ms2026-10-09 UTC: p95 485ms2026-10-10 UTC: p95 473ms2026-10-11 UTC: p95 498ms2026-10-12 UTC: p95 540ms2026-10-13 UTC: p95 570ms2026-10-14 UTC: p95 553ms2026-10-15 UTC: p95 478ms2026-10-16 UTC: p95 496ms2026-10-17 UTC: p95 453ms2026-10-18 UTC: p95 460ms2026-10-19 UTC: p95 653ms2026-10-20 UTC: p95 577ms2026-10-21 UTC: p95 442ms2026-10-22 UTC: p95 580ms2026-10-23 UTC: p95 1.0s2026-10-24 UTC: p95 1.3s2026-10-25 UTC: p95 426ms2026-10-26 UTC: p95 462ms2026-10-27 UTC: p95 3.9s2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 761ms2026-10-30 UTC: p95 1.5s2026-10-31 UTC: p95 962ms2026-11-01 UTC: p95 1.0s2026-11-02 UTC: p95 2.2s2026-11-03 UTC: p95 2.3s2026-11-04 UTC: p95 3.0s2026-11-05 UTC: p95 3.0s
Oct 7Oct 21Nov 5
US-Central
376msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 345ms2026-10-08 UTC: p95 362ms2026-10-09 UTC: p95 388ms2026-10-10 UTC: p95 376ms2026-10-11 UTC: p95 410ms2026-10-12 UTC: p95 417ms2026-10-13 UTC: p95 431ms2026-10-14 UTC: p95 381ms2026-10-15 UTC: p95 340ms2026-10-16 UTC: p95 454ms2026-10-17 UTC: p95 483ms2026-10-18 UTC: p95 481ms2026-10-19 UTC: p95 520ms2026-10-20 UTC: p95 388ms2026-10-21 UTC: p95 656ms2026-10-22 UTC: p95 394ms2026-10-23 UTC: p95 486ms2026-10-24 UTC: p95 349ms2026-10-25 UTC: p95 323ms2026-10-26 UTC: p95 361ms2026-10-27 UTC: p95 958ms2026-10-28 UTC: p95 1.0s2026-10-29 UTC: p95 1.0s2026-10-30 UTC: p95 807ms2026-10-31 UTC: p95 511ms2026-11-01 UTC: p95 449ms2026-11-02 UTC: p95 570ms2026-11-03 UTC: p95 732ms2026-11-04 UTC: p95 835ms2026-11-05 UTC: p95 376ms
Oct 7Oct 21Nov 5
Canada
2.2sp95 · latest
2.5s1.3s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 445ms2026-10-08 UTC: p95 360ms2026-10-09 UTC: p95 324ms2026-10-10 UTC: p95 362ms2026-10-11 UTC: p95 391ms2026-10-12 UTC: p95 370ms2026-10-13 UTC: p95 467ms2026-10-14 UTC: p95 426ms2026-10-15 UTC: p95 393ms2026-10-16 UTC: p95 390ms2026-10-17 UTC: p95 380ms2026-10-18 UTC: p95 325ms2026-10-19 UTC: p95 349ms2026-10-20 UTC: p95 341ms2026-10-21 UTC: p95 402ms2026-10-22 UTC: p95 528ms2026-10-23 UTC: p95 498ms2026-10-24 UTC: p95 372ms2026-10-25 UTC: p95 390ms2026-10-26 UTC: p95 339ms2026-10-27 UTC: p95 685ms2026-10-28 UTC: p95 488ms2026-10-29 UTC: p95 459ms2026-10-30 UTC: p95 684ms2026-10-31 UTC: p95 430ms2026-11-01 UTC: p95 602ms2026-11-02 UTC: p95 494ms2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 2.2s2026-11-05 UTC: p95 2.2s
Oct 7Oct 21Nov 5
UK
741msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 265ms2026-10-08 UTC: p95 217ms2026-10-09 UTC: p95 315ms2026-10-10 UTC: p95 350ms2026-10-11 UTC: p95 354ms2026-10-12 UTC: p95 371ms2026-10-13 UTC: p95 343ms2026-10-14 UTC: p95 350ms2026-10-15 UTC: p95 224ms2026-10-16 UTC: p95 528ms2026-10-17 UTC: p95 218ms2026-10-18 UTC: p95 245ms2026-10-19 UTC: p95 320ms2026-10-20 UTC: p95 277ms2026-10-21 UTC: p95 288ms2026-10-22 UTC: p95 370ms2026-10-23 UTC: p95 304ms2026-10-24 UTC: p95 247ms2026-10-25 UTC: p95 401ms2026-10-26 UTC: p95 210ms2026-10-27 UTC: p95 233ms2026-10-28 UTC: p95 786ms2026-10-29 UTC: p95 633ms2026-10-30 UTC: p95 507ms2026-10-31 UTC: p95 546ms2026-11-01 UTC: p95 465ms2026-11-02 UTC: p95 658ms2026-11-03 UTC: p95 799ms2026-11-04 UTC: p95 370ms2026-11-05 UTC: p95 741ms
Oct 7Oct 21Nov 5
Southeast Asia
2.6sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 466ms2026-10-08 UTC: p95 476ms2026-10-09 UTC: p95 508ms2026-10-10 UTC: p95 466ms2026-10-11 UTC: p95 468ms2026-10-12 UTC: p95 816ms2026-10-13 UTC: p95 674ms2026-10-14 UTC: p95 632ms2026-10-15 UTC: p95 459ms2026-10-16 UTC: p95 515ms2026-10-17 UTC: p95 526ms2026-10-18 UTC: p95 453ms2026-10-19 UTC: p95 660ms2026-10-20 UTC: p95 596ms2026-10-21 UTC: p95 825ms2026-10-22 UTC: p95 650ms2026-10-23 UTC: p95 647ms2026-10-24 UTC: p95 489ms2026-10-25 UTC: p95 498ms2026-10-26 UTC: p95 532ms2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 448ms2026-10-30 UTC: p95 636ms2026-10-31 UTC: p95 1.1s2026-11-01 UTC: p95 1.5s2026-11-02 UTC: p95 1.6s2026-11-03 UTC: p95 1.0s2026-11-04 UTC: p95 1.6s2026-11-05 UTC: p95 2.6s
Oct 7Oct 21Nov 5
Australia
1.4sp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 679ms2026-10-08 UTC: p95 678ms2026-10-09 UTC: p95 652ms2026-10-10 UTC: p95 619ms2026-10-11 UTC: p95 705ms2026-10-12 UTC: p95 758ms2026-10-13 UTC: p95 987ms2026-10-14 UTC: p95 865ms2026-10-15 UTC: p95 660ms2026-10-16 UTC: p95 675ms2026-10-17 UTC: p95 797ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 763ms2026-10-21 UTC: p95 730ms2026-10-22 UTC: p95 669ms2026-10-23 UTC: p95 615ms2026-10-24 UTC: p95 698ms2026-10-25 UTC: p95 690ms2026-10-26 UTC: p95 666ms2026-10-27 UTC: p95 738ms2026-10-28 UTC: p95 760ms2026-10-29 UTC: p95 987ms2026-10-30 UTC: p95 725ms2026-10-31 UTC: p95 2.0s2026-11-01 UTC: p95 2.5s2026-11-02 UTC: p95 2.2s2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 1.4s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
South America
1.7sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 532ms2026-10-08 UTC: p95 609ms2026-10-09 UTC: p95 528ms2026-10-10 UTC: p95 574ms2026-10-11 UTC: p95 566ms2026-10-12 UTC: p95 920ms2026-10-13 UTC: p95 784ms2026-10-14 UTC: p95 929ms2026-10-15 UTC: p95 643ms2026-10-16 UTC: p95 579ms2026-10-17 UTC: p95 630ms2026-10-18 UTC: p95 544ms2026-10-19 UTC: p95 673ms2026-10-20 UTC: p95 811ms2026-10-21 UTC: p95 907ms2026-10-22 UTC: p95 710ms2026-10-23 UTC: p95 8.6s2026-10-24 UTC: p95 603ms2026-10-25 UTC: p95 588ms2026-10-26 UTC: p95 845ms2026-10-27 UTC: p95 598ms2026-10-28 UTC: p95 1.7s2026-10-29 UTC: p95 766ms2026-10-30 UTC: p95 509ms2026-10-31 UTC: p95 783ms2026-11-01 UTC: p95 1.8s2026-11-02 UTC: p95 2.4s2026-11-03 UTC: p95 1.7s2026-11-04 UTC: p95 2.8s2026-11-05 UTC: p95 1.7s
Oct 7Oct 21Nov 5

Check your own site while you wait on Codecov

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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when Codecov reports an incident on its status page, and again when it reports it resolved.

Get an email when Codecov reports an incident

Email me when Codecov reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is Codecov's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 312msstatus code: 200checked: Nov 5, 2026, 2:18 PM 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
      Checks passinglatency: 1111msstatus code: 200checked: Nov 5, 2026, 2:03 PM 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
      Checks passinglatency: 294msstatus code: 200checked: Nov 5, 2026, 2:15 PM 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
      Checks passinglatency: 932msstatus code: 200checked: Nov 5, 2026, 2:14 PM 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
    Checks passinglatency: 506msstatus code: 200checked: Nov 5, 2026, 2:17 PM 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 811msstatus code: 200checked: Nov 5, 2026, 2:35 PM 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
      Checks passinglatency: 180msstatus code: 200checked: Nov 5, 2026, 2:14 PM 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1543msstatus code: 200checked: Nov 5, 2026, 1:54 PM 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
      Checks passinglatency: 276msstatus code: 200checked: Nov 5, 2026, 2:16 PM 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
      Checks passinglatency: 375msstatus code: 200checked: Nov 5, 2026, 2:15 PM 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 probe events

Codecov app and services are down, 2h 23mdeclared on their status page2026-10-05
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

check 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 check readings and Codecov's own claim at the time, side by side.

Full check history for Codecov: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Codecov uptime by RealUptime's checksLive, from this page's own readings.
[![Codecov uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Codecov down?", https://realuptime.io/outages/codecov. The readings change with every check, so give the date you read them.

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

What our check can and cannot see

A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.

Host checked: api.codecov.io

RealUptime is not affiliated with Codecov; the name identifies what we checked, 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.