Skip to content

Outage tracker / Mercury

Is Mercury down?

I'm having a problem

Vendor reports no incidentWhat Mercury reports

Mercury reports no incident on its status page.

As of the last successful poll, 2026-10-22 22:40 UTC.

Mercury'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 3 minutes ago

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

As of Oct 22, 2026, 10:43 PM UTC, RealUptime's checks of Mercury passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Oct 22, 2026, 10:43 PM UTC
US-East428 msChecks passing
US-West979 msChecks passing
Europe580 msChecks passing
Asia-Pacific1356 msChecks passing
US-Central997 msChecks passing
Canada391 msChecks passing
UK571 msChecks passing
Southeast Asia917 msChecks passing
Australia1461 msChecks passing
South America2551 msChecks passing
their status pagetheir claim, not our reading

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

from Mercury's own status page, checked Oct 22, 2026, 10:33 PM UTC
Mercury's own status page shows no incident, and our checks of Mercury pass right now.

Mercury's own component breakdown, as they publish it

  • Account AccessOperational
  • Account ManagementOperational
  • Account Opening Operational
  • Money Movement Operational
  • CardsOperational
  • Bill Pay & InvoicingOperational
  • Check DepositsOperational
  • Mercury TreasuryOperational
  • Integrations & APIOperational
  • Mercury PersonalOperational
  • SupportOperational

These are Mercury's components, named and scored by Mercury. 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 Mercury'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.

Mercury response time, by region

US-East
770msp95 · 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 391ms2026-09-24 UTC: p95 392ms2026-09-25 UTC: p95 398ms2026-09-26 UTC: p95 340ms2026-09-27 UTC: p95 364ms2026-09-28 UTC: p95 364ms2026-09-29 UTC: p95 348ms2026-09-30 UTC: p95 409ms2026-10-01 UTC: p95 247ms2026-10-02 UTC: p95 263ms2026-10-03 UTC: p95 331ms2026-10-04 UTC: p95 319ms2026-10-05 UTC: p95 276ms2026-10-06 UTC: p95 443ms2026-10-07 UTC: p95 364ms2026-10-08 UTC: p95 336ms2026-10-09 UTC: p95 256ms2026-10-10 UTC: p95 304ms2026-10-11 UTC: p95 237ms2026-10-12 UTC: p95 261ms2026-10-13 UTC: p95 348ms2026-10-14 UTC: p95 370ms2026-10-15 UTC: p95 361ms2026-10-16 UTC: p95 371ms2026-10-17 UTC: p95 661ms2026-10-18 UTC: p95 885ms2026-10-19 UTC: p95 921ms2026-10-20 UTC: p95 901ms2026-10-21 UTC: p95 869ms2026-10-22 UTC: p95 770ms
Sep 23Oct 7Oct 22
US-West
1.2sp95 · 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-09-23 UTC: p95 339ms2026-09-24 UTC: p95 444ms2026-09-25 UTC: p95 478ms2026-09-26 UTC: p95 398ms2026-09-27 UTC: p95 431ms2026-09-28 UTC: p95 453ms2026-09-29 UTC: p95 428ms2026-09-30 UTC: p95 469ms2026-10-01 UTC: p95 392ms2026-10-02 UTC: p95 442ms2026-10-03 UTC: p95 498ms2026-10-04 UTC: p95 370ms2026-10-05 UTC: p95 450ms2026-10-06 UTC: p95 448ms2026-10-07 UTC: p95 437ms2026-10-08 UTC: p95 449ms2026-10-09 UTC: p95 345ms2026-10-10 UTC: p95 358ms2026-10-11 UTC: p95 380ms2026-10-12 UTC: p95 439ms2026-10-13 UTC: p95 481ms2026-10-14 UTC: p95 474ms2026-10-15 UTC: p95 439ms2026-10-16 UTC: p95 483ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.2s
Sep 23Oct 7Oct 22
Europe
900msp95 · 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-09-23 UTC: p95 508ms2026-09-24 UTC: p95 479ms2026-09-25 UTC: p95 445ms2026-09-26 UTC: p95 775ms2026-09-27 UTC: p95 702ms2026-09-28 UTC: p95 807ms2026-09-29 UTC: p95 482ms2026-09-30 UTC: p95 554ms2026-10-01 UTC: p95 674ms2026-10-02 UTC: p95 754ms2026-10-03 UTC: p95 622ms2026-10-04 UTC: p95 652ms2026-10-05 UTC: p95 576ms2026-10-06 UTC: p95 624ms2026-10-07 UTC: p95 484ms2026-10-08 UTC: p95 487ms2026-10-09 UTC: p95 599ms2026-10-10 UTC: p95 510ms2026-10-11 UTC: p95 481ms2026-10-12 UTC: p95 647ms2026-10-13 UTC: p95 567ms2026-10-14 UTC: p95 569ms2026-10-15 UTC: p95 562ms2026-10-16 UTC: p95 483ms2026-10-17 UTC: p95 822ms2026-10-18 UTC: p95 975ms2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 853ms2026-10-21 UTC: p95 991ms2026-10-22 UTC: p95 900ms
Sep 23Oct 7Oct 22
Asia-Pacific
2.2sp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 1.0s2026-09-24 UTC: p95 941ms2026-09-25 UTC: p95 861ms2026-09-26 UTC: p95 913ms2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 1.5s2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.3s2026-10-06 UTC: p95 1.2s2026-10-07 UTC: p95 1.0s2026-10-08 UTC: p95 938ms2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.0s2026-10-11 UTC: p95 1.8s2026-10-12 UTC: p95 983ms2026-10-13 UTC: p95 886ms2026-10-14 UTC: p95 998ms2026-10-15 UTC: p95 1.0s2026-10-16 UTC: p95 1.0s2026-10-17 UTC: p95 1.8s2026-10-18 UTC: p95 1.9s2026-10-19 UTC: p95 1.9s2026-10-20 UTC: p95 1.9s2026-10-21 UTC: p95 1.9s2026-10-22 UTC: p95 2.2s
Sep 23Oct 7Oct 22
US-Central
1.3sp95 · 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-09-23 UTC: p95 426ms2026-09-24 UTC: p95 362ms2026-09-25 UTC: p95 440ms2026-09-26 UTC: p95 295ms2026-09-27 UTC: p95 251ms2026-09-28 UTC: p95 315ms2026-09-29 UTC: p95 298ms2026-09-30 UTC: p95 297ms2026-10-01 UTC: p95 338ms2026-10-02 UTC: p95 263ms2026-10-03 UTC: p95 433ms2026-10-04 UTC: p95 367ms2026-10-05 UTC: p95 311ms2026-10-06 UTC: p95 416ms2026-10-07 UTC: p95 364ms2026-10-08 UTC: p95 259ms2026-10-09 UTC: p95 301ms2026-10-10 UTC: p95 427ms2026-10-11 UTC: p95 405ms2026-10-12 UTC: p95 427ms2026-10-13 UTC: p95 541ms2026-10-14 UTC: p95 478ms2026-10-15 UTC: p95 412ms2026-10-16 UTC: p95 553ms2026-10-17 UTC: p95 849ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.3s
Sep 23Oct 7Oct 22
Canada
844msp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 234ms2026-09-24 UTC: p95 237ms2026-09-25 UTC: p95 430ms2026-09-26 UTC: p95 492ms2026-09-27 UTC: p95 283ms2026-09-28 UTC: p95 470ms2026-09-29 UTC: p95 448ms2026-09-30 UTC: p95 527ms2026-10-01 UTC: p95 467ms2026-10-02 UTC: p95 429ms2026-10-03 UTC: p95 511ms2026-10-04 UTC: p95 700ms2026-10-05 UTC: p95 532ms2026-10-06 UTC: p95 399ms2026-10-07 UTC: p95 343ms2026-10-08 UTC: p95 348ms2026-10-09 UTC: p95 448ms2026-10-10 UTC: p95 406ms2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 610ms2026-10-13 UTC: p95 300ms2026-10-14 UTC: p95 363ms2026-10-15 UTC: p95 264ms2026-10-16 UTC: p95 583ms2026-10-17 UTC: p95 328ms2026-10-18 UTC: p95 816ms2026-10-19 UTC: p95 334ms2026-10-20 UTC: p95 662ms2026-10-21 UTC: p95 512ms2026-10-22 UTC: p95 844ms
Sep 23Oct 7Oct 22
UK
1.1sp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 555ms2026-09-24 UTC: p95 539ms2026-09-25 UTC: p95 577ms2026-09-26 UTC: p95 565ms2026-09-27 UTC: p95 549ms2026-09-28 UTC: p95 609ms2026-09-29 UTC: p95 640ms2026-09-30 UTC: p95 551ms2026-10-01 UTC: p95 818ms2026-10-02 UTC: p95 775ms2026-10-03 UTC: p95 732ms2026-10-04 UTC: p95 781ms2026-10-05 UTC: p95 473ms2026-10-06 UTC: p95 449ms2026-10-07 UTC: p95 432ms2026-10-08 UTC: p95 704ms2026-10-09 UTC: p95 711ms2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 683ms2026-10-12 UTC: p95 820ms2026-10-13 UTC: p95 603ms2026-10-14 UTC: p95 722ms2026-10-15 UTC: p95 641ms2026-10-16 UTC: p95 566ms2026-10-17 UTC: p95 706ms2026-10-18 UTC: p95 756ms2026-10-19 UTC: p95 806ms2026-10-20 UTC: p95 957ms2026-10-21 UTC: p95 716ms2026-10-22 UTC: p95 1.1s
Sep 23Oct 7Oct 22
Southeast Asia
1.4sp95 · 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-09-23 UTC: p95 1.8s2026-09-24 UTC: p95 1.6s2026-09-25 UTC: p95 1.6s2026-09-26 UTC: p95 1.9s2026-09-27 UTC: p95 1.5s2026-09-28 UTC: p95 1.7s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.5s2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 1.6s2026-10-03 UTC: p95 1.8s2026-10-04 UTC: p95 1.6s2026-10-05 UTC: p95 1.9s2026-10-06 UTC: p95 1.7s2026-10-07 UTC: p95 1.6s2026-10-08 UTC: p95 1.7s2026-10-09 UTC: p95 2.2s2026-10-10 UTC: p95 2.6s2026-10-11 UTC: p95 2.5s2026-10-12 UTC: p95 2.6s2026-10-13 UTC: p95 1.8s2026-10-14 UTC: p95 2.1s2026-10-15 UTC: p95 1.4s2026-10-16 UTC: p95 1.4s2026-10-17 UTC: p95 2.2s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 1.9s2026-10-20 UTC: p95 1.9s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.4s
Sep 23Oct 7Oct 22
Australia
1.9sp95 · 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-09-23 UTC: p95 1.4s2026-09-24 UTC: p95 1.5s2026-09-25 UTC: p95 1.7s2026-09-26 UTC: p95 1.5s2026-09-27 UTC: p95 1.7s2026-09-28 UTC: p95 1.6s2026-09-29 UTC: p95 1.8s2026-09-30 UTC: p95 1.6s2026-10-01 UTC: p95 1.5s2026-10-02 UTC: p95 1.6s2026-10-03 UTC: p95 1.5s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.1s2026-10-06 UTC: p95 1.3s2026-10-07 UTC: p95 1.5s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.8s2026-10-11 UTC: p95 2.1s2026-10-12 UTC: p95 1.9s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.0s2026-10-15 UTC: p95 1.5s2026-10-16 UTC: p95 1.6s2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 1.9s2026-10-21 UTC: p95 2.0s2026-10-22 UTC: p95 1.9s
Sep 23Oct 7Oct 22
South America
2.6sp95 · latest
5s2.5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 925ms2026-09-24 UTC: p95 904ms2026-09-25 UTC: p95 969ms2026-09-26 UTC: p95 1s2026-09-27 UTC: p95 873ms2026-09-28 UTC: p95 985ms2026-09-29 UTC: p95 1.2s2026-09-30 UTC: p95 1.0s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 913ms2026-10-03 UTC: p95 899ms2026-10-04 UTC: p95 845ms2026-10-05 UTC: p95 1.1s2026-10-06 UTC: p95 922ms2026-10-07 UTC: p95 847ms2026-10-08 UTC: p95 947ms2026-10-09 UTC: p95 1.0s2026-10-10 UTC: p95 1.0s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.7s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 861ms2026-10-16 UTC: p95 762ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 2.1s2026-10-21 UTC: p95 2.0s2026-10-22 UTC: p95 2.6s
Sep 23Oct 7Oct 22

Check your own site while you wait on Mercury

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 Mercury. It cannot diagnose Mercury's own systems.

What we measured, function by function

Mercury 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 Mercury reports an incident on its status page, and again when it reports it resolved.

Get an email when Mercury reports an incident

Email me when Mercury 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 Mercury'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: 428msstatus code: 401checked: Oct 22, 2026, 10:21 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Mercury normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 979msstatus code: 401checked: Oct 22, 2026, 10:28 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Mercury normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 997msstatus code: 401checked: Oct 22, 2026, 9:53 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Mercury normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 391msstatus code: 401checked: Oct 22, 2026, 10:43 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Mercury normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 2551msstatus code: 401checked: Oct 22, 2026, 9:53 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Mercury 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: 580msstatus code: 401checked: Oct 22, 2026, 10:25 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Mercury normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 571msstatus code: 401checked: Oct 22, 2026, 10:02 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Mercury 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: 1356msstatus code: 401checked: Oct 22, 2026, 10:37 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Mercury normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 917msstatus code: 401checked: Oct 22, 2026, 10:06 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Mercury normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 1461msstatus code: 401checked: Oct 22, 2026, 10:12 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Mercury 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 Mercury, 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 Mercury yet, which is not evidence that nothing is wrong.

Recent probe events

Failed Investments Wire Transfers Out for Some Customers, 161h 28mdeclared on their status page2026-10-07
Issues Revealing Card Details on Web and Mobile, 1h 18mdeclared on their status page2026-10-02
Account Actions Experiencing Delays, 2h 5mdeclared on their status page2026-09-02
Intermittent Inbound & Outbound Call Disruption, 38mdeclared on their status page2026-09-01

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

We have been measuring Mercury 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 Mercury covering any window you pick, with our check readings and Mercury's own claim at the time, side by side.

Full check history for Mercury: 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

Mercury uptime by RealUptime's checksLive, from this page's own readings.
[![Mercury uptime by RealUptime's checks](https://realuptime.io/outages/mercury/badge.svg?days=30)](https://realuptime.io/outages/mercury)
<a href="https://realuptime.io/outages/mercury"><img src="https://realuptime.io/outages/mercury/badge.svg?days=30" alt="Mercury 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 Mercury down?", https://realuptime.io/outages/mercury. 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.mercury.com/api/v1/accounts
secondary
https://mercury.com/

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.mercury.com

RealUptime is not affiliated with Mercury; the name identifies what we checked, and nothing here speaks for Mercury's own team. We send a single web request to Mercury from 10 regions on our own schedule and time the response. We do not see inside Mercury's systems, do not use an account or real transaction, and are not the same signal Mercury's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Mercury 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.