Skip to content

Outage tracker / Kraken

Is Kraken down?

I'm having a problem

Vendor reports an incidentWhat Kraken reports

Kraken reports an incident on its status page: Deposit and Withdrawal Delays on Multiple Networks.

Impact: minor. Since 2026-11-05 10:19 UTC.

Latest update, 2026-11-05 10:19 UTC: We’re investigating an issue affecting funding gateways on the Ink, Optimism, Unichain, Shape, Gensyn, Fraxtal, Katana, X Layer and Base networks. Deposits and withdrawals on these networks may be delayed at this time. All other funding methods are operating normally. We are working to resolve the issue and will keep you updated.

Kraken'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 Kraken pass from all 10 regions we check.

As of Nov 5, 2026, 3:05 PM UTC, RealUptime's checks of Kraken passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 3:05 PM UTC
US-East1691 msChecks passing
US-West1132 msChecks passing
Europe282 msChecks passing
Asia-Pacific2474 msChecks passing
US-Central247 msChecks passing
Canada144 msChecks passing
UK65 msChecks passing
Southeast Asia2032 msChecks passing
Australia311 msChecks passing
South America1629 msChecks passing
their status pagetheir claim, not our reading

Kraken publishes no status feed we can read, so the only reading here is our check reading on the left.

Kraken response time, by region

US-East
2.4sp95 · latest
5s2.5s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 898ms2026-10-08 UTC: p95 883ms2026-10-09 UTC: p95 522ms2026-10-10 UTC: p95 818ms2026-10-11 UTC: p95 784ms2026-10-12 UTC: p95 832ms2026-10-13 UTC: p95 789ms2026-10-14 UTC: p95 767ms2026-10-15 UTC: p95 590ms2026-10-16 UTC: p95 774ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.1s2026-10-24 UTC: p95 1.3s2026-10-25 UTC: p95 366ms2026-10-26 UTC: p95 829ms2026-10-27 UTC: p95 808ms2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 1.2s2026-10-30 UTC: p95 1.5s2026-10-31 UTC: p95 1.3s2026-11-01 UTC: p95 1.6s2026-11-02 UTC: p95 2.0s2026-11-03 UTC: p95 2.5s2026-11-04 UTC: p95 2.7s2026-11-05 UTC: p95 2.4s
Oct 7Oct 21Nov 5
US-West
2.4sp95 · 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 320ms2026-10-08 UTC: p95 349ms2026-10-09 UTC: p95 493ms2026-10-10 UTC: p95 562ms2026-10-11 UTC: p95 614ms2026-10-12 UTC: p95 654ms2026-10-13 UTC: p95 592ms2026-10-14 UTC: p95 520ms2026-10-15 UTC: p95 484ms2026-10-16 UTC: p95 680ms2026-10-17 UTC: p95 897ms2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.5s2026-10-23 UTC: p95 810ms2026-10-24 UTC: p95 435ms2026-10-25 UTC: p95 936ms2026-10-26 UTC: p95 1.1s2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 1.3s2026-10-30 UTC: p95 789ms2026-10-31 UTC: p95 826ms2026-11-01 UTC: p95 1.5s2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 3.2s2026-11-04 UTC: p95 2.1s2026-11-05 UTC: p95 2.4s
Oct 7Oct 21Nov 5
Europe
1.4sp95 · latest
2.5s1.3s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 717ms2026-10-08 UTC: p95 425ms2026-10-09 UTC: p95 252ms2026-10-10 UTC: p95 426ms2026-10-11 UTC: p95 540ms2026-10-12 UTC: p95 399ms2026-10-13 UTC: p95 280ms2026-10-14 UTC: p95 492ms2026-10-15 UTC: p95 364ms2026-10-16 UTC: p95 318ms2026-10-17 UTC: p95 690ms2026-10-18 UTC: p95 678ms2026-10-19 UTC: p95 676ms2026-10-20 UTC: p95 546ms2026-10-21 UTC: p95 714ms2026-10-22 UTC: p95 801ms2026-10-23 UTC: p95 386ms2026-10-24 UTC: p95 361ms2026-10-25 UTC: p95 398ms2026-10-26 UTC: p95 386ms2026-10-27 UTC: p95 299ms2026-10-28 UTC: p95 378ms2026-10-29 UTC: p95 487ms2026-10-30 UTC: p95 665ms2026-10-31 UTC: p95 681ms2026-11-01 UTC: p95 752ms2026-11-02 UTC: p95 1.6s2026-11-03 UTC: p95 1.8s2026-11-04 UTC: p95 2.0s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
Asia-Pacific
3.4sp95 · latest
10s5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 874ms2026-10-08 UTC: p95 794ms2026-10-09 UTC: p95 657ms2026-10-10 UTC: p95 693ms2026-10-11 UTC: p95 770ms2026-10-12 UTC: p95 681ms2026-10-13 UTC: p95 784ms2026-10-14 UTC: p95 1.3s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 862ms2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 1.7s2026-10-22 UTC: p95 2.1s2026-10-23 UTC: p95 1.9s2026-10-24 UTC: p95 2.1s2026-10-25 UTC: p95 1.5s2026-10-26 UTC: p95 2.0s2026-10-27 UTC: p95 7.2s2026-10-28 UTC: p95 1.8s2026-10-29 UTC: p95 2.8s2026-10-30 UTC: p95 2.8s2026-10-31 UTC: p95 2.8s2026-11-01 UTC: p95 2.9s2026-11-02 UTC: p95 3.1s2026-11-03 UTC: p95 3.6s2026-11-04 UTC: p95 3.2s2026-11-05 UTC: p95 3.4s
Oct 7Oct 21Nov 5
US-Central
609msp95 · 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 451ms2026-10-08 UTC: p95 590ms2026-10-09 UTC: p95 488ms2026-10-10 UTC: p95 300ms2026-10-11 UTC: p95 272ms2026-10-12 UTC: p95 358ms2026-10-13 UTC: p95 473ms2026-10-14 UTC: p95 496ms2026-10-15 UTC: p95 527ms2026-10-16 UTC: p95 689ms2026-10-17 UTC: p95 911ms2026-10-18 UTC: p95 988ms2026-10-19 UTC: p95 964ms2026-10-20 UTC: p95 1.0s2026-10-21 UTC: p95 1.0s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 1.3s2026-10-24 UTC: p95 1.6s2026-10-25 UTC: p95 1.8s2026-10-26 UTC: p95 1.5s2026-10-27 UTC: p95 987ms2026-10-28 UTC: p95 511ms2026-10-29 UTC: p95 1.6s2026-10-30 UTC: p95 774ms2026-10-31 UTC: p95 945ms2026-11-01 UTC: p95 752ms2026-11-02 UTC: p95 979ms2026-11-03 UTC: p95 931ms2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 609ms
Oct 7Oct 21Nov 5
Canada
1.5sp95 · 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-10-07 UTC: p95 537ms2026-10-08 UTC: p95 396ms2026-10-09 UTC: p95 546ms2026-10-10 UTC: p95 508ms2026-10-11 UTC: p95 522ms2026-10-12 UTC: p95 429ms2026-10-13 UTC: p95 435ms2026-10-14 UTC: p95 387ms2026-10-15 UTC: p95 525ms2026-10-16 UTC: p95 686ms2026-10-17 UTC: p95 936ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.4s2026-10-23 UTC: p95 1.3s2026-10-24 UTC: p95 719ms2026-10-25 UTC: p95 1.4s2026-10-26 UTC: p95 1.4s2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 1.2s2026-10-30 UTC: p95 623ms2026-10-31 UTC: p95 878ms2026-11-01 UTC: p95 882ms2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 1.5s
Oct 7Oct 21Nov 5
UK
402msp95 · 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-10-07 UTC: p95 249ms2026-10-08 UTC: p95 348ms2026-10-09 UTC: p95 324ms2026-10-10 UTC: p95 324ms2026-10-11 UTC: p95 329ms2026-10-12 UTC: p95 364ms2026-10-13 UTC: p95 180ms2026-10-14 UTC: p95 228ms2026-10-15 UTC: p95 247ms2026-10-16 UTC: p95 208ms2026-10-17 UTC: p95 865ms2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 984ms2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 311ms2026-10-24 UTC: p95 423ms2026-10-25 UTC: p95 80ms2026-10-26 UTC: p95 190ms2026-10-27 UTC: p95 673ms2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 1.0s2026-10-30 UTC: p95 181ms2026-10-31 UTC: p95 370ms2026-11-01 UTC: p95 420ms2026-11-02 UTC: p95 573ms2026-11-03 UTC: p95 550ms2026-11-04 UTC: p95 623ms2026-11-05 UTC: p95 402ms
Oct 7Oct 21Nov 5
Southeast Asia
2.0sp95 · 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 670ms2026-10-08 UTC: p95 443ms2026-10-09 UTC: p95 639ms2026-10-10 UTC: p95 1.0s2026-10-11 UTC: p95 1.0s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 370ms2026-10-15 UTC: p95 697ms2026-10-16 UTC: p95 1.0s2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 2.7s2026-10-20 UTC: p95 3.0s2026-10-21 UTC: p95 2.8s2026-10-22 UTC: p95 3.2s2026-10-23 UTC: p95 1.2s2026-10-24 UTC: p95 1.2s2026-10-25 UTC: p95 1.7s2026-10-26 UTC: p95 1.7s2026-10-27 UTC: p95 2.4s2026-10-28 UTC: p95 2.3s2026-10-29 UTC: p95 2.3s2026-10-30 UTC: p95 890ms2026-10-31 UTC: p95 767ms2026-11-01 UTC: p95 1.9s2026-11-02 UTC: p95 2.0s2026-11-03 UTC: p95 3.4s2026-11-04 UTC: p95 1.9s2026-11-05 UTC: p95 2.0s
Oct 7Oct 21Nov 5
Australia
2.4sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.6s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 1.6s2026-10-11 UTC: p95 669ms2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 826ms2026-10-14 UTC: p95 1.0s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 3.3s2026-10-18 UTC: p95 3.1s2026-10-19 UTC: p95 2.5s2026-10-20 UTC: p95 3.3s2026-10-21 UTC: p95 2.5s2026-10-22 UTC: p95 2.4s2026-10-23 UTC: p95 1.5s2026-10-24 UTC: p95 2.0s2026-10-25 UTC: p95 2.5s2026-10-26 UTC: p95 2.4s2026-10-27 UTC: p95 3.0s2026-10-28 UTC: p95 1.3s2026-10-29 UTC: p95 2.0s2026-10-30 UTC: p95 738ms2026-10-31 UTC: p95 1.4s2026-11-01 UTC: p95 2.8s2026-11-02 UTC: p95 3.1s2026-11-03 UTC: p95 3.5s2026-11-04 UTC: p95 1.9s2026-11-05 UTC: p95 2.4s
Oct 7Oct 21Nov 5
South America
1.1sp95 · latest
20s10s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 20s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 806ms2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 618ms2026-10-10 UTC: p95 412ms2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.6s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 786ms2026-10-15 UTC: p95 789ms2026-10-16 UTC: p95 917ms2026-10-17 UTC: p95 1.6s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.9s2026-10-21 UTC: p95 1.8s2026-10-22 UTC: p95 2.2s2026-10-23 UTC: p95 10.3s2026-10-24 UTC: p95 2.0s2026-10-25 UTC: p95 629ms2026-10-26 UTC: p95 988ms2026-10-27 UTC: p95 1.2s2026-10-28 UTC: p95 1.7s2026-10-29 UTC: p95 2.7s2026-10-30 UTC: p95 1.0s2026-10-31 UTC: p95 1.7s2026-11-01 UTC: p95 2.4s2026-11-02 UTC: p95 2.3s2026-11-03 UTC: p95 1.9s2026-11-04 UTC: p95 954ms2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5

Check your own site while you wait on Kraken

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

What we measured, function by function

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

Get an email when Kraken reports an incident

Email me when Kraken 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 Kraken'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: 1691msstatus code: 200checked: Nov 5, 2026, 2:57 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Kraken normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1132msstatus code: 200checked: Nov 5, 2026, 2:55 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Kraken normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 247msstatus code: 200checked: Nov 5, 2026, 3:03 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Kraken normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 144msstatus code: 200checked: Nov 5, 2026, 3:04 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Kraken normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 1629msstatus code: 200checked: Nov 5, 2026, 3:04 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Kraken 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: 282msstatus code: 200checked: Nov 5, 2026, 2:52 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Kraken normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 65msstatus code: 200checked: Nov 5, 2026, 3:04 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Kraken 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: 2474msstatus code: 200checked: Nov 5, 2026, 2:41 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Kraken normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 2032msstatus code: 200checked: Nov 5, 2026, 3:05 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Kraken normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 311msstatus code: 200checked: Nov 5, 2026, 3:04 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Kraken 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 Kraken, 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 Kraken yet, which is not evidence that nothing is wrong.

Recent probe events

Delays in Chart Updates - Kraken Pro Prop, 35mdeclared on their status page2026-11-05
Deposit and Withdrawal Delays on Multiple Networksdeclared on their status page2026-11-05
Plaid US Withdrawal Delays, 31mdeclared on their status page2026-11-04
Brazilian Real (BRL) PIX Funding Delays, 39h 37mdeclared on their status page2026-11-03
Incorrect liquidation prices displayed on Kraken Pro, 2h 36mdeclared on their status page2026-11-03
Delayed Earn rewards payouts, 32mdeclared on their status page2026-10-30
Spot Exchange Connectivity Issues - Web, Mobile & API (Rest & Websockets), 1hdeclared on their status page2026-10-30
Flow (FLOW) Funding Delays, 30h 23mdeclared on their status page2026-10-29

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

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

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

Kraken uptime by RealUptime's checksLive, from this page's own readings.
[![Kraken uptime by RealUptime's checks](https://realuptime.io/outages/kraken/badge.svg?days=30)](https://realuptime.io/outages/kraken)
<a href="https://realuptime.io/outages/kraken"><img src="https://realuptime.io/outages/kraken/badge.svg?days=30" alt="Kraken 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 Kraken down?", https://realuptime.io/outages/kraken. The readings change with every check, so give the date you read them.

What we check

primaryfunctional: live API
https://api.kraken.com/0/public/Time
secondary
https://www.kraken.com/
secondary
https://status.kraken.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.kraken.com

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