Skip to content

Outage tracker / Google Gemini (AI)

Is Google Gemini (AI) down?

I'm having a problem

Vendor reports no incidentWhat Google Gemini (AI) reports

Google Gemini (AI) reports no incident on its status page.

As of the last successful poll, 2026-10-23 02:50 UTC.

Google Gemini (AI)'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 2 minutes ago

Our checks of Google Gemini (AI) pass from all 10 regions we check.

As of Oct 23, 2026, 2:54 AM UTC, RealUptime's checks of Google Gemini (AI) passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Oct 23, 2026, 2:54 AM UTC
US-East600 msChecks passing
US-West882 msChecks passing
Europe346 msChecks passing
Asia-Pacific471 msChecks passing
US-Central182 msChecks passing
Canada714 msChecks passing
UK372 msChecks passing
Southeast Asia1114 msChecks passing
Australia975 msChecks passing
South America1865 msChecks passing
their status pagetheir claim, not our reading

Google Gemini (AI) publishes no status feed we can read, so the only reading here is our check reading on the left.

Google Gemini (AI) response time, by region

US-East
1sp95 · 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-09-24 UTC: p95 656ms2026-09-25 UTC: p95 575ms2026-09-26 UTC: p95 509ms2026-09-27 UTC: p95 601ms2026-09-28 UTC: p95 589ms2026-09-29 UTC: p95 733ms2026-09-30 UTC: p95 706ms2026-10-01 UTC: p95 501ms2026-10-02 UTC: p95 325ms2026-10-03 UTC: p95 352ms2026-10-04 UTC: p95 337ms2026-10-05 UTC: p95 359ms2026-10-06 UTC: p95 326ms2026-10-07 UTC: p95 328ms2026-10-08 UTC: p95 421ms2026-10-09 UTC: p95 440ms2026-10-10 UTC: p95 375ms2026-10-11 UTC: p95 346ms2026-10-12 UTC: p95 360ms2026-10-13 UTC: p95 444ms2026-10-14 UTC: p95 416ms2026-10-15 UTC: p95 470ms2026-10-16 UTC: p95 407ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 1.0s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 995ms2026-10-23 UTC: p95 1s
Sep 24Oct 8Oct 23
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-24 UTC: p95 589ms2026-09-25 UTC: p95 574ms2026-09-26 UTC: p95 473ms2026-09-27 UTC: p95 491ms2026-09-28 UTC: p95 484ms2026-09-29 UTC: p95 355ms2026-09-30 UTC: p95 392ms2026-10-01 UTC: p95 433ms2026-10-02 UTC: p95 389ms2026-10-03 UTC: p95 399ms2026-10-04 UTC: p95 438ms2026-10-05 UTC: p95 405ms2026-10-06 UTC: p95 443ms2026-10-07 UTC: p95 382ms2026-10-08 UTC: p95 416ms2026-10-09 UTC: p95 413ms2026-10-10 UTC: p95 415ms2026-10-11 UTC: p95 432ms2026-10-12 UTC: p95 443ms2026-10-13 UTC: p95 551ms2026-10-14 UTC: p95 630ms2026-10-15 UTC: p95 686ms2026-10-16 UTC: p95 633ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 1.7s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 1.2s
Sep 24Oct 8Oct 23
Europe
612msp95 · 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-24 UTC: p95 357ms2026-09-25 UTC: p95 295ms2026-09-26 UTC: p95 227ms2026-09-27 UTC: p95 230ms2026-09-28 UTC: p95 222ms2026-09-29 UTC: p95 225ms2026-09-30 UTC: p95 287ms2026-10-01 UTC: p95 238ms2026-10-02 UTC: p95 292ms2026-10-03 UTC: p95 240ms2026-10-04 UTC: p95 224ms2026-10-05 UTC: p95 260ms2026-10-06 UTC: p95 251ms2026-10-07 UTC: p95 238ms2026-10-08 UTC: p95 294ms2026-10-09 UTC: p95 295ms2026-10-10 UTC: p95 243ms2026-10-11 UTC: p95 247ms2026-10-12 UTC: p95 256ms2026-10-13 UTC: p95 251ms2026-10-14 UTC: p95 184ms2026-10-15 UTC: p95 202ms2026-10-16 UTC: p95 238ms2026-10-17 UTC: p95 411ms2026-10-18 UTC: p95 621ms2026-10-19 UTC: p95 723ms2026-10-20 UTC: p95 658ms2026-10-21 UTC: p95 962ms2026-10-22 UTC: p95 660ms2026-10-23 UTC: p95 612ms
Sep 24Oct 8Oct 23
Asia-Pacific
1.1sp95 · 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-09-24 UTC: p95 584ms2026-09-25 UTC: p95 562ms2026-09-26 UTC: p95 518ms2026-09-27 UTC: p95 617ms2026-09-28 UTC: p95 541ms2026-09-29 UTC: p95 482ms2026-09-30 UTC: p95 550ms2026-10-01 UTC: p95 493ms2026-10-02 UTC: p95 441ms2026-10-03 UTC: p95 472ms2026-10-04 UTC: p95 413ms2026-10-05 UTC: p95 432ms2026-10-06 UTC: p95 474ms2026-10-07 UTC: p95 437ms2026-10-08 UTC: p95 482ms2026-10-09 UTC: p95 526ms2026-10-10 UTC: p95 425ms2026-10-11 UTC: p95 451ms2026-10-12 UTC: p95 448ms2026-10-13 UTC: p95 614ms2026-10-14 UTC: p95 710ms2026-10-15 UTC: p95 913ms2026-10-16 UTC: p95 901ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 1.1s
Sep 24Oct 8Oct 23
US-Central
303msp95 · 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-24 UTC: p95 249ms2026-09-25 UTC: p95 280ms2026-09-26 UTC: p95 331ms2026-09-27 UTC: p95 329ms2026-09-28 UTC: p95 386ms2026-09-29 UTC: p95 400ms2026-09-30 UTC: p95 381ms2026-10-01 UTC: p95 331ms2026-10-02 UTC: p95 213ms2026-10-03 UTC: p95 298ms2026-10-04 UTC: p95 352ms2026-10-05 UTC: p95 265ms2026-10-06 UTC: p95 290ms2026-10-07 UTC: p95 290ms2026-10-08 UTC: p95 336ms2026-10-09 UTC: p95 393ms2026-10-10 UTC: p95 352ms2026-10-11 UTC: p95 367ms2026-10-12 UTC: p95 323ms2026-10-13 UTC: p95 347ms2026-10-14 UTC: p95 495ms2026-10-15 UTC: p95 473ms2026-10-16 UTC: p95 362ms2026-10-17 UTC: p95 754ms2026-10-18 UTC: p95 865ms2026-10-19 UTC: p95 885ms2026-10-20 UTC: p95 837ms2026-10-21 UTC: p95 640ms2026-10-22 UTC: p95 342ms2026-10-23 UTC: p95 303ms
Sep 24Oct 8Oct 23
Canada
811msp95 · 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-24 UTC: p95 651ms2026-09-25 UTC: p95 514ms2026-09-26 UTC: p95 400ms2026-09-27 UTC: p95 443ms2026-09-28 UTC: p95 420ms2026-09-29 UTC: p95 502ms2026-09-30 UTC: p95 525ms2026-10-01 UTC: p95 496ms2026-10-02 UTC: p95 400ms2026-10-03 UTC: p95 377ms2026-10-04 UTC: p95 396ms2026-10-05 UTC: p95 419ms2026-10-06 UTC: p95 464ms2026-10-07 UTC: p95 351ms2026-10-08 UTC: p95 381ms2026-10-09 UTC: p95 359ms2026-10-10 UTC: p95 424ms2026-10-11 UTC: p95 452ms2026-10-12 UTC: p95 425ms2026-10-13 UTC: p95 467ms2026-10-14 UTC: p95 393ms2026-10-15 UTC: p95 386ms2026-10-16 UTC: p95 336ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.4s2026-10-23 UTC: p95 811ms
Sep 24Oct 8Oct 23
UK
507msp95 · 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-24 UTC: p95 378ms2026-09-25 UTC: p95 430ms2026-09-26 UTC: p95 310ms2026-09-27 UTC: p95 158ms2026-09-28 UTC: p95 165ms2026-09-29 UTC: p95 203ms2026-09-30 UTC: p95 168ms2026-10-01 UTC: p95 300ms2026-10-02 UTC: p95 252ms2026-10-03 UTC: p95 242ms2026-10-04 UTC: p95 208ms2026-10-05 UTC: p95 229ms2026-10-06 UTC: p95 243ms2026-10-07 UTC: p95 316ms2026-10-08 UTC: p95 228ms2026-10-09 UTC: p95 319ms2026-10-10 UTC: p95 192ms2026-10-11 UTC: p95 158ms2026-10-12 UTC: p95 205ms2026-10-13 UTC: p95 244ms2026-10-14 UTC: p95 193ms2026-10-15 UTC: p95 227ms2026-10-16 UTC: p95 236ms2026-10-17 UTC: p95 471ms2026-10-18 UTC: p95 665ms2026-10-19 UTC: p95 648ms2026-10-20 UTC: p95 1.0s2026-10-21 UTC: p95 991ms2026-10-22 UTC: p95 645ms2026-10-23 UTC: p95 507ms
Sep 24Oct 8Oct 23
Southeast Asia
1.1sp95 · 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-24 UTC: p95 777ms2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 803ms2026-09-27 UTC: p95 823ms2026-09-28 UTC: p95 810ms2026-09-29 UTC: p95 768ms2026-09-30 UTC: p95 650ms2026-10-01 UTC: p95 657ms2026-10-02 UTC: p95 606ms2026-10-03 UTC: p95 686ms2026-10-04 UTC: p95 672ms2026-10-05 UTC: p95 819ms2026-10-06 UTC: p95 812ms2026-10-07 UTC: p95 891ms2026-10-08 UTC: p95 806ms2026-10-09 UTC: p95 816ms2026-10-10 UTC: p95 735ms2026-10-11 UTC: p95 741ms2026-10-12 UTC: p95 839ms2026-10-13 UTC: p95 876ms2026-10-14 UTC: p95 918ms2026-10-15 UTC: p95 884ms2026-10-16 UTC: p95 719ms2026-10-17 UTC: p95 2.2s2026-10-18 UTC: p95 2.3s2026-10-19 UTC: p95 2.5s2026-10-20 UTC: p95 2.2s2026-10-21 UTC: p95 1.7s2026-10-22 UTC: p95 1.4s2026-10-23 UTC: p95 1.1s
Sep 24Oct 8Oct 23
Australia
1.0sp95 · 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-24 UTC: p95 1.2s2026-09-25 UTC: p95 1.4s2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 1.2s2026-09-29 UTC: p95 1.2s2026-09-30 UTC: p95 1.4s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.5s2026-10-03 UTC: p95 1.3s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.2s2026-10-06 UTC: p95 1.2s2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 897ms2026-10-10 UTC: p95 915ms2026-10-11 UTC: p95 963ms2026-10-12 UTC: p95 988ms2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.0s2026-10-16 UTC: p95 1.0s2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 1.9s2026-10-21 UTC: p95 1.8s2026-10-22 UTC: p95 1.7s2026-10-23 UTC: p95 1.0s
Sep 24Oct 8Oct 23
South America
1.7sp95 · latest
2.5s1.3s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 1.8s2026-09-25 UTC: p95 1.6s2026-09-26 UTC: p95 1.6s2026-09-27 UTC: p95 1.8s2026-09-28 UTC: p95 1.5s2026-09-29 UTC: p95 1.3s2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.3s2026-10-04 UTC: p95 1.5s2026-10-05 UTC: p95 1.1s2026-10-06 UTC: p95 1.5s2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.0s2026-10-10 UTC: p95 923ms2026-10-11 UTC: p95 995ms2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.5s2026-10-14 UTC: p95 1.3s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.4s2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 2.4s2026-10-19 UTC: p95 2.1s2026-10-20 UTC: p95 2.1s2026-10-21 UTC: p95 1.8s2026-10-22 UTC: p95 2.2s2026-10-23 UTC: p95 1.7s
Sep 24Oct 8Oct 23

Check your own site while you wait on Google Gemini (AI)

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 Google Gemini (AI). It cannot diagnose Google Gemini (AI)'s own systems.

What we measured, function by function

Google Gemini (AI) 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 Google Gemini (AI) reports an incident on its status page, and again when it reports it resolved.

Get an email when Google Gemini (AI) reports an incident

Email me when Google Gemini (AI) 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 Google Gemini (AI)'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: 600msstatus code: 200checked: Oct 23, 2026, 2:54 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Google Gemini (AI) normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 882msstatus code: 200checked: Oct 23, 2026, 2:47 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Google Gemini (AI) normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 182msstatus code: 200checked: Oct 23, 2026, 2:49 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Google Gemini (AI) normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 714msstatus code: 200checked: Oct 23, 2026, 2:39 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Google Gemini (AI) normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 1865msstatus code: 200checked: Oct 23, 2026, 2:53 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Google Gemini (AI) 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: 346msstatus code: 200checked: Oct 23, 2026, 2:50 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Google Gemini (AI) normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 372msstatus code: 200checked: Oct 23, 2026, 2:44 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Google Gemini (AI) 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: 471msstatus code: 200checked: Oct 23, 2026, 2:49 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Google Gemini (AI) normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 1114msstatus code: 200checked: Oct 23, 2026, 2:41 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Google Gemini (AI) normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 975msstatus code: 200checked: Oct 23, 2026, 2:43 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Google Gemini (AI) 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 Google Gemini (AI), 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 Google Gemini (AI) yet, which is not evidence that nothing is wrong.

Recent probe events

Mitigated intermittent elevated error rates with Gemini 3.1 Pro models on Gemini Web and Gemini App., 7h 22mdeclared on their status page2026-09-11
Gemini App in Workspace and Gemini Side Panel (Gemini in Workspace) customers are experiencing “Something Went Wrong” errors., 7h 10mdeclared on their status page2026-06-10
Investigating elevated error rates with Gemini conversations., 98h 13mdeclared on their status page2026-05-04
: Some customers may have experienced an issue with Gemini where conversation history may not have been visible., 99h 38mdeclared on their status page2026-02-18

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

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

Full check history for Google Gemini (AI): 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

Google Gemini (AI) uptime by RealUptime's checksLive, from this page's own readings.
[![Google Gemini (AI) uptime by RealUptime's checks](https://realuptime.io/outages/google-gemini/badge.svg?days=30)](https://realuptime.io/outages/google-gemini)
<a href="https://realuptime.io/outages/google-gemini"><img src="https://realuptime.io/outages/google-gemini/badge.svg?days=30" alt="Google Gemini (AI) 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 Google Gemini (AI) down?", https://realuptime.io/outages/google-gemini. 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://generativelanguage.googleapis.com/$discovery/rest?version=v1beta
secondaryfunctional: live API
https://generativelanguage.googleapis.com/v1beta/models
secondary
https://gemini.google.com/

What our check can and cannot see

A pass means the configuration document the service publishes, such as an API or sign-in description, loaded. That document is usually static or cached, so it does not show that the endpoints it describes are answering.

Host checked: generativelanguage.googleapis.com

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