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-10-22 21:50 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 1 minute ago

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

As of Oct 22, 2026, 9:50 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 Oct 22, 2026, 9:50 PM UTC
US-East163 msChecks passing
US-West445 msChecks passing
Europe316 msChecks passing
Asia-Pacific482 msChecks passing
US-Central352 msChecks passing
Canada379 msChecks passing
UK214 msChecks passing
Southeast Asia642 msChecks passing
Australia508 msChecks passing
South America541 msChecks passing
their status pagetheir claim, not our reading

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

from Codecov's own status page, checked Oct 22, 2026, 9:22 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
426msp95 · 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-09-23 UTC: p95 280ms2026-09-24 UTC: p95 262ms2026-09-25 UTC: p95 296ms2026-09-26 UTC: p95 278ms2026-09-27 UTC: p95 277ms2026-09-28 UTC: p95 276ms2026-09-29 UTC: p95 265ms2026-09-30 UTC: p95 249ms2026-10-01 UTC: p95 311ms2026-10-02 UTC: p95 303ms2026-10-03 UTC: p95 298ms2026-10-04 UTC: p95 262ms2026-10-05 UTC: p95 273ms2026-10-06 UTC: p95 538ms2026-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 426ms
Sep 23Oct 7Oct 22
US-West
835msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 465ms2026-09-24 UTC: p95 440ms2026-09-25 UTC: p95 454ms2026-09-26 UTC: p95 447ms2026-09-27 UTC: p95 463ms2026-09-28 UTC: p95 473ms2026-09-29 UTC: p95 449ms2026-09-30 UTC: p95 422ms2026-10-01 UTC: p95 431ms2026-10-02 UTC: p95 449ms2026-10-03 UTC: p95 486ms2026-10-04 UTC: p95 514ms2026-10-05 UTC: p95 496ms2026-10-06 UTC: p95 434ms2026-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 835ms
Sep 23Oct 7Oct 22
Europe
447msp95 · 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-09-23 UTC: p95 350ms2026-09-24 UTC: p95 335ms2026-09-25 UTC: p95 352ms2026-09-26 UTC: p95 375ms2026-09-27 UTC: p95 357ms2026-09-28 UTC: p95 385ms2026-09-29 UTC: p95 329ms2026-09-30 UTC: p95 338ms2026-10-01 UTC: p95 418ms2026-10-02 UTC: p95 384ms2026-10-03 UTC: p95 349ms2026-10-04 UTC: p95 384ms2026-10-05 UTC: p95 346ms2026-10-06 UTC: p95 335ms2026-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 447ms
Sep 23Oct 7Oct 22
Asia-Pacific
604msp95 · latest
1s500ms0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 445ms2026-09-24 UTC: p95 663ms2026-09-25 UTC: p95 440ms2026-09-26 UTC: p95 438ms2026-09-27 UTC: p95 412ms2026-09-28 UTC: p95 531ms2026-09-29 UTC: p95 472ms2026-09-30 UTC: p95 490ms2026-10-01 UTC: p95 639ms2026-10-02 UTC: p95 511ms2026-10-03 UTC: p95 439ms2026-10-04 UTC: p95 458ms2026-10-05 UTC: p95 596ms2026-10-06 UTC: p95 544ms2026-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 604ms
Sep 23Oct 7Oct 22
US-Central
390msp95 · 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-23 UTC: p95 401ms2026-09-24 UTC: p95 374ms2026-09-25 UTC: p95 388ms2026-09-26 UTC: p95 344ms2026-09-27 UTC: p95 388ms2026-09-28 UTC: p95 431ms2026-09-29 UTC: p95 368ms2026-09-30 UTC: p95 401ms2026-10-01 UTC: p95 295ms2026-10-02 UTC: p95 390ms2026-10-03 UTC: p95 381ms2026-10-04 UTC: p95 392ms2026-10-05 UTC: p95 331ms2026-10-06 UTC: p95 449ms2026-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 390ms
Sep 23Oct 7Oct 22
Canada
535msp95 · 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-23 UTC: p95 347ms2026-09-24 UTC: p95 373ms2026-09-25 UTC: p95 313ms2026-09-26 UTC: p95 327ms2026-09-27 UTC: p95 392ms2026-09-28 UTC: p95 387ms2026-09-29 UTC: p95 331ms2026-09-30 UTC: p95 339ms2026-10-01 UTC: p95 395ms2026-10-02 UTC: p95 321ms2026-10-03 UTC: p95 363ms2026-10-04 UTC: p95 408ms2026-10-05 UTC: p95 347ms2026-10-06 UTC: p95 460ms2026-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 535ms
Sep 23Oct 7Oct 22
UK
384msp95 · 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-09-23 UTC: p95 219ms2026-09-24 UTC: p95 206ms2026-09-25 UTC: p95 227ms2026-09-26 UTC: p95 296ms2026-09-27 UTC: p95 217ms2026-09-28 UTC: p95 296ms2026-09-29 UTC: p95 208ms2026-09-30 UTC: p95 223ms2026-10-01 UTC: p95 300ms2026-10-02 UTC: p95 354ms2026-10-03 UTC: p95 218ms2026-10-04 UTC: p95 217ms2026-10-05 UTC: p95 277ms2026-10-06 UTC: p95 297ms2026-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 384ms
Sep 23Oct 7Oct 22
Southeast Asia
649msp95 · latest
1s500ms0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 492ms2026-09-24 UTC: p95 443ms2026-09-25 UTC: p95 457ms2026-09-26 UTC: p95 466ms2026-09-27 UTC: p95 462ms2026-09-28 UTC: p95 497ms2026-09-29 UTC: p95 534ms2026-09-30 UTC: p95 530ms2026-10-01 UTC: p95 455ms2026-10-02 UTC: p95 489ms2026-10-03 UTC: p95 473ms2026-10-04 UTC: p95 477ms2026-10-05 UTC: p95 575ms2026-10-06 UTC: p95 648ms2026-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 649ms
Sep 23Oct 7Oct 22
Australia
677msp95 · 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-23 UTC: p95 633ms2026-09-24 UTC: p95 686ms2026-09-25 UTC: p95 644ms2026-09-26 UTC: p95 663ms2026-09-27 UTC: p95 787ms2026-09-28 UTC: p95 656ms2026-09-29 UTC: p95 610ms2026-09-30 UTC: p95 623ms2026-10-01 UTC: p95 846ms2026-10-02 UTC: p95 612ms2026-10-03 UTC: p95 654ms2026-10-04 UTC: p95 617ms2026-10-05 UTC: p95 640ms2026-10-06 UTC: p95 792ms2026-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 677ms
Sep 23Oct 7Oct 22
South America
718msp95 · 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-23 UTC: p95 599ms2026-09-24 UTC: p95 584ms2026-09-25 UTC: p95 679ms2026-09-26 UTC: p95 665ms2026-09-27 UTC: p95 659ms2026-09-28 UTC: p95 753ms2026-09-29 UTC: p95 590ms2026-09-30 UTC: p95 575ms2026-10-01 UTC: p95 562ms2026-10-02 UTC: p95 589ms2026-10-03 UTC: p95 659ms2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 579ms2026-10-06 UTC: p95 596ms2026-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 718ms
Sep 23Oct 7Oct 22

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: 163msstatus code: 200checked: Oct 22, 2026, 9:49 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: 445msstatus code: 200checked: Oct 22, 2026, 9:50 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: 352msstatus code: 200checked: Oct 22, 2026, 9:50 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: 379msstatus code: 200checked: Oct 22, 2026, 9:49 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: 541msstatus code: 200checked: Oct 22, 2026, 9:50 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: 316msstatus code: 200checked: Oct 22, 2026, 9:50 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: 214msstatus code: 200checked: Oct 22, 2026, 9:50 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: 482msstatus code: 200checked: Oct 22, 2026, 9:50 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: 642msstatus code: 200checked: Oct 22, 2026, 9:50 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: 508msstatus code: 200checked: Oct 22, 2026, 9:50 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

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>

The badge shows the share of our checks that passed over the last 30 days. 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

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.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

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.