Is Gemini down right now?
Authenticated API inference - 2 models monitored · How we classify outages
Gemini is currently operational - 116ms HTTP response. Last checked . 90-day uptime: 100%. Gemini API: all 2 models responding - fastest TTFT 391ms.
UPDATE: Network traffic to Google Cloud originating from Delhi, Chennai, Mumbai and surrounding areas is experiencing intermittent periods of elevated latency and possible packet loss.
Stay informed
Follow @tickerr_ai
We post when tier 1 LLM APIs go down - before the official status page updates.
Follow on X →Or get the weekly reliability digest:
Add a status badge
Show live Gemini status on your site, README, or docs.
HTTP uptime (90d)
100%
20 incidents (90d)
HTTP response now
116ms
HTTP p50 (7d)
250ms
median ping response
HTTP p95 (7d)
1042ms
tail ping response
Gemini API Status
Live · every 5 minBest TTFT (p50)
391ms
time to first token
Best throughput
1000tok/s
output tokens/sec (24h avg)
Min success rate
100%
worst model (24h)
P50 = typical speed. P95 = worst case 95% of the time. Measured by Tickerr's independent inference checks. Requires ≥10 checks to display.
TTFT over 24 hours
ⓘ Authenticated streaming API calls via native fetch. TTFT = milliseconds from request start to first streamed token chunk. Throughput = output tokens ÷ generation time. Checks run from Vercel us-east-1. Independent of the provider's official status page.
Agent monitoring active · 2 agents reporting · Powered by Tickerr MCP
HTTP endpoint response time (7 days)
p50 250ms·p95 1042msⓘ HTTP response times to Gemini's status endpoint - measures infrastructure availability, not API inference speed. For TTFT and model-level API status, see the Gemini API Status section above.
90-day uptime
Incident history
gemini-2.5-flash-lite API Latency Degraded
Independent monitoring detected elevated API latency for gemini-2.5-flash-lite. Current TTFT is 4.4× above the rolling p50 baseline (1827ms vs p50 412ms). The service is responding but slower than nor…
Independent monitoring detected consecutive API failures for gemini-2.5-flash. Tickerr measures time-to-first-token (TTFT) via live streaming API calls every 5 minutes.
Independent monitoring detected consecutive API failures for gemini-2.5-flash-lite. Tickerr measures time-to-first-token (TTFT) via live streaming API calls every 5 minutes.
gemini-2.5-flash-lite API Latency Degraded
Independent monitoring detected elevated API latency for gemini-2.5-flash-lite. Current TTFT is 8.8× above the rolling p50 baseline (4684ms vs p50 531ms). The service is responding but slower than nor…
gemini-2.5-flash-lite API Latency Degraded
Independent monitoring detected elevated API latency for gemini-2.5-flash-lite. Current TTFT is 6.7× above the rolling p50 baseline (2647ms vs p50 393ms). The service is responding but slower than nor…
gemini-2.5-flash-lite API Latency Degraded
Independent monitoring detected elevated API latency for gemini-2.5-flash-lite. Current TTFT is 6.9× above the rolling p50 baseline (3489ms vs p50 503ms). The service is responding but slower than nor…
gemini-2.5-flash-lite API Latency Degraded
Independent monitoring detected elevated API latency for gemini-2.5-flash-lite. Current TTFT is 12.3× above the rolling p50 baseline (6340ms vs p50 514ms). The service is responding but slower than no…
gemini-2.5-flash-lite API Latency Degraded
Independent monitoring detected elevated API latency for gemini-2.5-flash-lite. Current TTFT is 6.6× above the rolling p50 baseline (3092ms vs p50 468ms). The service is responding but slower than nor…
Independent monitoring detected consecutive API failures for gemini-2.5-flash-lite. Tickerr measures time-to-first-token (TTFT) via live streaming API calls every 5 minutes.
gemini-2.5-flash-lite API Latency Degraded
Independent monitoring detected elevated API latency for gemini-2.5-flash-lite. Current TTFT is 7.9× above the rolling p50 baseline (3892ms vs p50 494ms). The service is responding but slower than nor…
gemini-2.5-flash-lite API Latency Degraded
Independent monitoring detected elevated API latency for gemini-2.5-flash-lite. Current TTFT is 3× above the rolling p50 baseline (1426ms vs p50 479ms). The service is responding but slower than norma…
gemini-2.5-flash-lite API Latency Degraded
Independent monitoring detected elevated API latency for gemini-2.5-flash-lite. Current TTFT is 8.5× above the rolling p50 baseline (5199ms vs p50 610ms). The service is responding but slower than nor…
gemini-2.5-flash-lite API Latency Degraded
Independent monitoring detected elevated API latency for gemini-2.5-flash-lite. Current TTFT is 13.1× above the rolling p50 baseline (5384ms vs p50 412ms). The service is responding but slower than no…
gemini-2.5-flash-lite API Latency Degraded
Independent monitoring detected elevated API latency for gemini-2.5-flash-lite. Current TTFT is 7.5× above the rolling p50 baseline (9039ms vs p50 1204ms). The service is responding but slower than no…
gemini-2.5-flash-lite API Latency Degraded
Independent monitoring detected elevated API latency for gemini-2.5-flash-lite. Current TTFT is 3.1× above the rolling p50 baseline (3699ms vs p50 1204ms). The service is responding but slower than no…
gemini-2.5-flash-lite API Latency Degraded
Independent monitoring detected elevated API latency for gemini-2.5-flash-lite. Current TTFT is 2.2× above the rolling p50 baseline (6015ms vs p50 2708ms). The service is responding but slower than no…
Independent monitoring detected consecutive API failures for gemini-2.5-flash-lite. Tickerr measures time-to-first-token (TTFT) via live streaming API calls every 5 minutes.
gemini-2.5-flash-lite API Latency Degraded
Independent monitoring detected elevated API latency for gemini-2.5-flash-lite. Current TTFT is 11.2× above the rolling p50 baseline (6969ms vs p50 624ms). The service is responding but slower than no…
<p> Incident began at <strong>2026-06-05 00:00</strong> and ended at <strong>2026-06-26 12:00</strong> <span>(all times are <strong>US/Pacific</strong>)…
Independent monitoring detected consecutive API failures for gemini-2.5-flash-lite. Tickerr measures time-to-first-token (TTFT) via live streaming API calls every 5 minutes.
Related pages
Gemini API not working? Common error codes
If Gemini's API is returning errors, the table below explains what each code means and how to fix it. If errors are widespread, check the live status above - a service incident will appear there within minutes.
| Error | What it means & what to do |
|---|---|
| HTTP 429 (RESOURCE_EXHAUSTED) | Rate limit exceeded - 15 RPM on free tier; add retry delay |
| HTTP 503 (UNAVAILABLE) | Service unavailable - check for Google Cloud incidents |
| HTTP 400 (INVALID_ARGUMENT) | Bad request - check prompt format and safety filters |
Note: Tickerr monitors Gemini's status endpoint, not individual API calls. An HTTP 429 or 500 in your app may be specific to your account tier - check the rate limits page for plan-specific thresholds.
About Gemini status
Gemini is Google's AI assistant and language model. Gemini downtime affects both the consumer app and the API used by developers. If Gemini is not working, it may be a Google infrastructure issue affecting multiple services. Gemini status is checked every 5 minutes.