User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
gemini.google.com · AI
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Tests gemini.google.com from your browser and compares it with our checks, the official status, and user reports.
Press Run testNothing leaves your browser except a request to the site and to us.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 265 ms · 1 min ago.
No status feed
Google Gemini does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 11:30 | 0 | 0.0 | 153 ms | 0 |
| 11:45 | 0 | 0.0 | 171 ms | 0 |
| 12:00 | 0 | 0.0 | 582 ms | 0 |
| 12:15 | 0 | 0.0 | 321 ms | 0 |
| 12:30 | 0 | 0.0 | 138 ms | 0 |
| 12:45 | 0 | 0.0 | 524 ms | 0 |
| 13:00 | 0 | 0.0 | 172 ms | 0 |
| 13:15 | 0 | 0.0 | 159 ms | 0 |
| 13:30 | 0 | 0.0 | 155 ms | 0 |
| 13:45 | 0 | 0.0 | 151 ms | 0 |
| 14:00 | 0 | 0.0 | 181 ms | 0 |
| 14:15 | 0 | 0.0 | 224 ms | 0 |
| 14:30 | 0 | 0.0 | 156 ms | 0 |
| 14:45 | 0 | 0.0 | 155 ms | 0 |
| 15:00 | 0 | 0.0 | 177 ms | 0 |
| 15:15 | 0 | 0.0 | 163 ms | 0 |
| 15:30 | 0 | 0.0 | 175 ms | 0 |
| 15:45 | 0 | 0.0 | 188 ms | 0 |
| 16:00 | 0 | 0.0 | 270 ms | 0 |
| 16:15 | 0 | 0.0 | 135 ms | 0 |
| 16:30 | 0 | 0.0 | 146 ms | 0 |
| 16:45 | 0 | 0.0 | 169 ms | 0 |
| 17:00 | 0 | 0.0 | 265 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
Embed this status badge · JSON
No outages on record for Google Gemini yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Google Gemini goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Runs on: Google
Checks are succeeding and user reports are near the baseline.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.