Skip to content

Outage tracker / Gmail

Is Gmail down?

I'm having a problem

Vendor reports no incidentWhat Gmail reports

Gmail reports no incident on its status page.

As of the last successful poll, 2026-11-05 13:53 UTC.

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

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

Front-door and live API checks

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

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

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

our check readinglive · checked Nov 5, 2026, 2:07 PM UTC
US-East309 msChecks passing
US-West450 msChecks passing
Europe196 msChecks passing
Asia-Pacific875 msChecks passing
US-Central271 msChecks passing
Canada357 msChecks passing
UK212 msChecks passing
Southeast Asia1520 msChecks passing
Australia1642 msChecks passing
South America901 msChecks passing
their status pagetheir claim, not our reading

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

Gmail response time, by region

US-East
812msp95 · 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 423ms2026-10-08 UTC: p95 641ms2026-10-09 UTC: p95 653ms2026-10-10 UTC: p95 675ms2026-10-11 UTC: p95 651ms2026-10-12 UTC: p95 446ms2026-10-13 UTC: p95 706ms2026-10-14 UTC: p95 428ms2026-10-15 UTC: p95 542ms2026-10-16 UTC: p95 735ms2026-10-17 UTC: p95 587ms2026-10-18 UTC: p95 775ms2026-10-19 UTC: p95 947ms2026-10-20 UTC: p95 571ms2026-10-21 UTC: p95 532ms2026-10-22 UTC: p95 578ms2026-10-23 UTC: p95 529ms2026-10-24 UTC: p95 571ms2026-10-25 UTC: p95 604ms2026-10-26 UTC: p95 794ms2026-10-27 UTC: p95 555ms2026-10-28 UTC: p95 543ms2026-10-29 UTC: p95 488ms2026-10-30 UTC: p95 604ms2026-10-31 UTC: p95 577ms2026-11-01 UTC: p95 526ms2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 682ms2026-11-04 UTC: p95 846ms2026-11-05 UTC: p95 812ms
Oct 7Oct 21Nov 5
US-West
711msp95 · 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-10-07 UTC: p95 640ms2026-10-08 UTC: p95 823ms2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 623ms2026-10-11 UTC: p95 619ms2026-10-12 UTC: p95 706ms2026-10-13 UTC: p95 446ms2026-10-14 UTC: p95 528ms2026-10-15 UTC: p95 478ms2026-10-16 UTC: p95 736ms2026-10-17 UTC: p95 914ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 721ms2026-10-22 UTC: p95 609ms2026-10-23 UTC: p95 606ms2026-10-24 UTC: p95 483ms2026-10-25 UTC: p95 514ms2026-10-26 UTC: p95 649ms2026-10-27 UTC: p95 709ms2026-10-28 UTC: p95 603ms2026-10-29 UTC: p95 506ms2026-10-30 UTC: p95 546ms2026-10-31 UTC: p95 511ms2026-11-01 UTC: p95 478ms2026-11-02 UTC: p95 556ms2026-11-03 UTC: p95 672ms2026-11-04 UTC: p95 676ms2026-11-05 UTC: p95 711ms
Oct 7Oct 21Nov 5
Europe
421msp95 · 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-10-07 UTC: p95 742ms2026-10-08 UTC: p95 346ms2026-10-09 UTC: p95 409ms2026-10-10 UTC: p95 368ms2026-10-11 UTC: p95 615ms2026-10-12 UTC: p95 817ms2026-10-13 UTC: p95 534ms2026-10-14 UTC: p95 638ms2026-10-15 UTC: p95 925ms2026-10-16 UTC: p95 508ms2026-10-17 UTC: p95 532ms2026-10-18 UTC: p95 518ms2026-10-19 UTC: p95 514ms2026-10-20 UTC: p95 434ms2026-10-21 UTC: p95 312ms2026-10-22 UTC: p95 340ms2026-10-23 UTC: p95 255ms2026-10-24 UTC: p95 200ms2026-10-25 UTC: p95 300ms2026-10-26 UTC: p95 290ms2026-10-27 UTC: p95 290ms2026-10-28 UTC: p95 245ms2026-10-29 UTC: p95 279ms2026-10-30 UTC: p95 282ms2026-10-31 UTC: p95 270ms2026-11-01 UTC: p95 244ms2026-11-02 UTC: p95 317ms2026-11-03 UTC: p95 388ms2026-11-04 UTC: p95 374ms2026-11-05 UTC: p95 421ms
Oct 7Oct 21Nov 5
Asia-Pacific
1.5sp95 · 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-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 753ms2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 944ms2026-10-11 UTC: p95 900ms2026-10-12 UTC: p95 973ms2026-10-13 UTC: p95 942ms2026-10-14 UTC: p95 963ms2026-10-15 UTC: p95 996ms2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 887ms2026-10-22 UTC: p95 841ms2026-10-23 UTC: p95 922ms2026-10-24 UTC: p95 965ms2026-10-25 UTC: p95 833ms2026-10-26 UTC: p95 1.0s2026-10-27 UTC: p95 1.0s2026-10-28 UTC: p95 914ms2026-10-29 UTC: p95 870ms2026-10-30 UTC: p95 916ms2026-10-31 UTC: p95 915ms2026-11-01 UTC: p95 1.0s2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.6s2026-11-05 UTC: p95 1.5s
Oct 7Oct 21Nov 5
US-Central
670msp95 · 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 622ms2026-10-08 UTC: p95 626ms2026-10-09 UTC: p95 891ms2026-10-10 UTC: p95 507ms2026-10-11 UTC: p95 636ms2026-10-12 UTC: p95 576ms2026-10-13 UTC: p95 642ms2026-10-14 UTC: p95 801ms2026-10-15 UTC: p95 756ms2026-10-16 UTC: p95 528ms2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.0s2026-10-21 UTC: p95 690ms2026-10-22 UTC: p95 819ms2026-10-23 UTC: p95 869ms2026-10-24 UTC: p95 765ms2026-10-25 UTC: p95 744ms2026-10-26 UTC: p95 764ms2026-10-27 UTC: p95 797ms2026-10-28 UTC: p95 736ms2026-10-29 UTC: p95 820ms2026-10-30 UTC: p95 635ms2026-10-31 UTC: p95 917ms2026-11-01 UTC: p95 672ms2026-11-02 UTC: p95 666ms2026-11-03 UTC: p95 702ms2026-11-04 UTC: p95 677ms2026-11-05 UTC: p95 670ms
Oct 7Oct 21Nov 5
Canada
585msp95 · 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 653ms2026-10-08 UTC: p95 999ms2026-10-09 UTC: p95 862ms2026-10-10 UTC: p95 862ms2026-10-11 UTC: p95 854ms2026-10-12 UTC: p95 532ms2026-10-13 UTC: p95 632ms2026-10-14 UTC: p95 680ms2026-10-15 UTC: p95 455ms2026-10-16 UTC: p95 864ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 742ms2026-10-23 UTC: p95 1.0s2026-10-24 UTC: p95 901ms2026-10-25 UTC: p95 1.2s2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 758ms2026-10-28 UTC: p95 768ms2026-10-29 UTC: p95 668ms2026-10-30 UTC: p95 647ms2026-10-31 UTC: p95 701ms2026-11-01 UTC: p95 568ms2026-11-02 UTC: p95 581ms2026-11-03 UTC: p95 666ms2026-11-04 UTC: p95 601ms2026-11-05 UTC: p95 585ms
Oct 7Oct 21Nov 5
UK
395msp95 · 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 377ms2026-10-08 UTC: p95 554ms2026-10-09 UTC: p95 574ms2026-10-10 UTC: p95 657ms2026-10-11 UTC: p95 606ms2026-10-12 UTC: p95 840ms2026-10-13 UTC: p95 915ms2026-10-14 UTC: p95 621ms2026-10-15 UTC: p95 888ms2026-10-16 UTC: p95 848ms2026-10-17 UTC: p95 753ms2026-10-18 UTC: p95 868ms2026-10-19 UTC: p95 695ms2026-10-20 UTC: p95 422ms2026-10-21 UTC: p95 726ms2026-10-22 UTC: p95 807ms2026-10-23 UTC: p95 762ms2026-10-24 UTC: p95 892ms2026-10-25 UTC: p95 320ms2026-10-26 UTC: p95 401ms2026-10-27 UTC: p95 432ms2026-10-28 UTC: p95 519ms2026-10-29 UTC: p95 336ms2026-10-30 UTC: p95 318ms2026-10-31 UTC: p95 415ms2026-11-01 UTC: p95 325ms2026-11-02 UTC: p95 326ms2026-11-03 UTC: p95 678ms2026-11-04 UTC: p95 600ms2026-11-05 UTC: p95 395ms
Oct 7Oct 21Nov 5
Southeast Asia
1.6sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.5s2026-10-08 UTC: p95 1.6s2026-10-09 UTC: p95 1.8s2026-10-10 UTC: p95 1.7s2026-10-11 UTC: p95 1.6s2026-10-12 UTC: p95 1.5s2026-10-13 UTC: p95 1.7s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 1.6s2026-10-16 UTC: p95 1.5s2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 2.0s2026-10-21 UTC: p95 2.1s2026-10-22 UTC: p95 1.8s2026-10-23 UTC: p95 1.3s2026-10-24 UTC: p95 1.7s2026-10-25 UTC: p95 1.4s2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 1.5s2026-10-28 UTC: p95 1.9s2026-10-29 UTC: p95 1.3s2026-10-30 UTC: p95 1.5s2026-10-31 UTC: p95 1.4s2026-11-01 UTC: p95 1.4s2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 2.0s2026-11-04 UTC: p95 1.7s2026-11-05 UTC: p95 1.6s
Oct 7Oct 21Nov 5
Australia
2.3sp95 · 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 1.3s2026-10-08 UTC: p95 1.4s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.8s2026-10-11 UTC: p95 1.8s2026-10-12 UTC: p95 1.6s2026-10-13 UTC: p95 1.6s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 1.4s2026-10-16 UTC: p95 1.5s2026-10-17 UTC: p95 1.9s2026-10-18 UTC: p95 2.1s2026-10-19 UTC: p95 2.0s2026-10-20 UTC: p95 1.8s2026-10-21 UTC: p95 2.0s2026-10-22 UTC: p95 2.1s2026-10-23 UTC: p95 2.2s2026-10-24 UTC: p95 1.8s2026-10-25 UTC: p95 1.5s2026-10-26 UTC: p95 1.8s2026-10-27 UTC: p95 2.1s2026-10-28 UTC: p95 2.5s2026-10-29 UTC: p95 1.6s2026-10-30 UTC: p95 1.6s2026-10-31 UTC: p95 1.8s2026-11-01 UTC: p95 1.9s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 2.4s2026-11-04 UTC: p95 2.2s2026-11-05 UTC: p95 2.3s
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 993ms2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 982ms2026-10-13 UTC: p95 1.0s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 871ms2026-10-16 UTC: p95 954ms2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 1.7s2026-10-22 UTC: p95 2.2s2026-10-23 UTC: p95 9.1s2026-10-24 UTC: p95 1.4s2026-10-25 UTC: p95 1.4s2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 1.5s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.3s2026-10-30 UTC: p95 1.4s2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 1.7s
Oct 7Oct 21Nov 5

Check your own site while you wait on Gmail

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

What we measured, function by function

Gmail 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
  • AuthUS-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
  • Gmail APIUS-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
  • Google sign-inUS-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
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: 309msstatus code: 401checked: Nov 5, 2026, 2:06 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Gmail normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 450msstatus code: 401checked: Nov 5, 2026, 2:04 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Gmail normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 271msstatus code: 401checked: Nov 5, 2026, 2:06 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Gmail normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 357msstatus code: 401checked: Nov 5, 2026, 2:03 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Gmail normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 901msstatus code: 401checked: Nov 5, 2026, 2:06 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Gmail 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: 196msstatus code: 401checked: Nov 5, 2026, 2:07 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Gmail normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 212msstatus code: 401checked: Nov 5, 2026, 2:06 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Gmail 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: 875msstatus code: 401checked: Nov 5, 2026, 2:02 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Gmail normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 1520msstatus code: 401checked: Nov 5, 2026, 2:05 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Gmail normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 1642msstatus code: 401checked: Nov 5, 2026, 2:06 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Gmail 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 Gmail, 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 Gmail yet, which is not evidence that nothing is wrong.

Recent probe events

Gmail Android App users on the latest Gmail Android release may experience issues accessing their inbox., 157hdeclared on their status page2026-09-18
Multiple Workspace Products experiencing Issues., 56mdeclared on their status page2026-05-31
Gmail users are experiencing delayed delivery of messages sent from the bank.in domains., 8h 47mdeclared on their status page2026-05-21
Gmail Android users using Microsoft Exchange Online may fail to log in due to authentication issues., 366hdeclared on their status page2026-05-06
Customers may experience delays in receiving and sending emails., 8h 10mdeclared on their status page2026-04-08
Gmail users might see banners indicating missing spam checks., 4h 53mdeclared on their status page2026-01-24
Gmail is experiencing an issue with images not loading properly., 2h 58mdeclared on their status page2025-11-10
A subset of customers in EDU domains are experiencing issues accessing Gmail mobile applications., 25h 20mdeclared on their status page2025-10-24

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

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

Full check history for Gmail: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Put this badge in your README

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

What we check

primaryfunctional: live API
https://mail.google.com/mail/u/0/feed/atom
secondary
https://mail.google.com/mail/u/0/
secondary
https://gmail.googleapis.com/gmail/v1/users/me/profile
secondary
https://accounts.google.com/.well-known/openid-configuration

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: mail.google.com

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