What is the google API's uptime?

Measured uptime for the google API averages 100% across 4 region(s) over the last 24 hours.

Is the Gemini API (Google) down? Live status, latency & uptime by region

Last verified October 22, 2026 · rebuilt about every 30 minutes

Is the Gemini API (Google) down right now?

Requests to gemini-flash-lite-latest failing from 2 of 4 regions right now

Last successful probe Oct 22, 06:46 UTC · every 5 minutes from 4 region(s)

There was an outage: on Oct 22, 06:41 UTC, requests to gemini-flash-lite-latest failed from 2 of 4 regions simultaneously for under one 5-minute probe cycle. No other provider failed in that window, so a shared route or CDN does not explain it. Measured from outside google’s own network, independently of its status page; full log: measured AI API incidents.

Real requests to gemini-flash-lite-latest: 252 of 289 succeeded in the last 24 hours from 4 region(s); last failure Oct 22, 06:41 UTC from Asia (Tokyo), Europe (Germany) (timeout). A one-token completion is sent on the same schedule as the host probe; 5xx, 529 and timeouts count as failures, problems with our own key or quota are excluded.

Google publishes no machine-readable status page, so there is nothing to cross-check against.

As of October 22, 2026, the google AI API responds in 58 ms p50 (edge, time-to-first-byte) from US (Central) — its fastest measured region — with 100% uptime. Slowest is South America (São Paulo) at 140 ms p50.

Endpoint response (TTFB), 24 h

58 ms

Typical (p50) from US (Central), the fastest region

Uptime, 24 h

100%

1,152 probes across 4 region(s)

Failed probes, 72 h

of 3,459 probes, all regions

Failed requests, 24 h

of 289 to gemini-flash-lite-latest

Reported by Google, 72 h

—

no machine-readable status page

Was Google down in the last 3 days?

Yes. 12 outage(s) could be attributed to Google in the last 72 hours: probes failed from two or more regions at once while no other provider was failing.

Oct 22, 06:41 UTCOutage — requests to gemini-flash-lite-latest: 2 of 4 regions (Asia (Tokyo), Europe (Germany)) · under one 5-minute probe cycle · 2 failed probe(s) · timeout
Oct 22, 06:01 UTCrequests to gemini-flash-lite-latest: South America (São Paulo) only — not an outage · under one 5-minute probe cycle · 1 failed probe(s) · timeout
Oct 22, 01:01 UTCrequests to gemini-flash-lite-latest: Europe (Germany) only — not an outage · under one 5-minute probe cycle · 1 failed probe(s) · timeout
Oct 22, 00:41 UTCrequests to gemini-flash-lite-latest: Europe (Germany) only — not an outage · under one 5-minute probe cycle · 1 failed probe(s) · timeout
Oct 22, 00:01 UTCrequests to gemini-flash-lite-latest: Asia (Tokyo) only — not an outage · under one 5-minute probe cycle · 1 failed probe(s) · timeout
Oct 21, 20:01 UTCrequests to gemini-flash-lite-latest: South America (São Paulo) only — not an outage · under one 5-minute probe cycle · 1 failed probe(s) · timeout
Oct 21, 17:01 UTCrequests to gemini-flash-lite-latest: Asia (Tokyo) only — not an outage · under one 5-minute probe cycle · 1 failed probe(s) · timeout
Oct 21, 16:01 UTCOutage — requests to gemini-flash-lite-latest: 2 of 4 regions (Europe (Germany), South America (São Paulo)) · under one 5-minute probe cycle · 2 failed probe(s) · timeout
Oct 21, 15:41 UTCOutage — requests to gemini-flash-lite-latest: 2 of 4 regions (Europe (Germany), South America (São Paulo)) · under one 5-minute probe cycle · 2 failed probe(s) · timeout
Oct 21, 15:21 UTCrequests to gemini-flash-lite-latest: 2 of 4 regions (Asia (Tokyo), South America (São Paulo)) — 1 other provider(s) failed in the same minutes, not attributed · under one 5-minute probe cycle · 2 failed probe(s) · timeout
Oct 21, 15:00 UTCrequests to gemini-flash-lite-latest: 4 of 4 regions (Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central)) — 1 other provider(s) failed in the same minutes, not attributed · under one 5-minute probe cycle · 4 failed probe(s) · timeout
Oct 21, 14:40 UTCOutage — requests to gemini-flash-lite-latest: 4 of 4 regions (Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central)) · under one 5-minute probe cycle · 4 failed probe(s) · timeout

Earlier days with Google incidents: Oct 21 (4 outages) · Oct 20 (6 outages) · Oct 19 (2 outages) · Oct 16 (8 outages) · Oct 14 (7 outages) · Oct 13 (6 outages) · Oct 12 (1 outage) · Oct 9 (1 outage)

Show this live in your README: — embed code

What Google’s own status page reported

Google publishes no machine-readable status page, so there is nothing to set against the measurements above.

Is Google getting faster or slower?

Endpoint response (TTFB) · milliseconds · lower is faster

Last 72 hours · UTC · newest time on the right · current hour is incomplete.

Each line shows a region’s typical response per hour (p50), using the same scale. A gap means no successful timed probe in that hour.

typical response per hour (p50)all probes succeededsome failed (under half)half or more failedno probes recorded

Probe counts by region

Europe (Germany): 0 failed / 864 endpoint probesEurope (Germany) · model: 29 failed / 216 requestsUS (Central): 0 failed / 862 endpoint probesUS (Central) · model: 24 failed / 216 requestsAsia (Tokyo): 0 failed / 862 endpoint probesAsia (Tokyo) · model: 30 failed / 216 requestsSouth America (São Paulo): 0 failed / 862 endpoint probesSouth America (São Paulo) · model: 31 failed / 217 requests

Chart details

The host strip shows endpoint probe outcomes; the model strip shows completion-request outcomes for gemini-flash-lite-latest. The model strip does not show time to first token (TTFT). Adjacent hours with all successes or no data are joined. Hover an hour for its recorded values.

Latest is the most recent hourly p50 with data. Median is the median of hourly p50 values over these 72 hours. The “slower than usual” label means latest is at least 25% above that median; it is a relative change, not a fixed speed rating.

How fast is the Google API from each region?

Endpoint response (TTFB) · last 24 hours · milliseconds (ms) · lower is faster.

How to read these metrics

Endpoint response (TTFB)Network connection and the first response byte, without model inference.

Typical · p5050% of successful timed samples finish within this time.

Slower · p9595% of successful timed samples finish within this time.

Region	Typical (p50 TTFB)	Slower (p95)	Uptime
Asia (Tokyo)	66 ms	124 ms	100%
Europe (Germany)	99 ms	202 ms	100%
South America (São Paulo)	140 ms	207 ms	100%
US (Central)	58 ms	149 ms	100%

Measured from US (Central), google responds in 58 ms; from South America (São Paulo) the same API takes 140 ms — 2.4× longer for an identical request. That difference is the network path, not the model, and it applies to every call you make.

What is actually being measured here?

A probe in each region opens a real connection to google’s own API host every five minutes and times DNS resolution, the TCP handshake, the TLS handshake and the first byte of the response. Nothing is routed through a gateway or aggregator, so these figures describe google’s infrastructure rather than a reseller’s. Uptime counts a probe as failed only when the service genuinely fails — a 401 from an unauthenticated probe means the endpoint answered correctly and is counted as up.

What this page does not tell you

These are edge latency numbers: the time before the model begins generating. They say nothing about answer quality, throughput, price, or how long a full completion takes — those depend on the model you call. Edge latency matters because it is unavoidable: it is paid on every request, before a single token exists, and no prompt engineering removes it. Where an API key is available, inference time-to-first-token is measured separately and shown on the region pages with the model named next to the figure. Likewise, an unauthenticated probe cannot see errors that hit only some models or some accounts — the kind a status page usually reports — which is why Google’s own reports are shown next to the measurements rather than folded into them.