Gemini is answering at its usual speed from all 10 countries we time it from.
Our probes' last round was at 14:07 UTC. Google's status page lists no open incident for Gemini (read 14:17 UTC). It reports incidents only and does not say whether Gemini is available. Open the status page
Gemini over the last 24 hours
Status pageGemini
No open incident listed
Our timinggemini.google.com
On time from 10 countries
The bands in words
- Google's status page for Gemini: No state given 13 Nov, 14:17 to 14 Nov, 14:17 UTC.
- Our timing of gemini.google.com: Delayed 13:22 to 13:52 UTC. On time the rest of the time.
What the status page listed
Google's status page listed no incident for Gemini in the last 24 hours.
What our probes confirmed
- gemini.google.com from Singapore, Singapore (LeaseWeb network)
14 Nov, 13:22 to 13:37 UTC; up to 294 ms against a usual 118 ms, in 2 rounds.
- Operational, or on time
- Degraded, partial outage or maintenance; or delayed
- Major outage, or no answer
- No state given, or too few samples
- No report read, or no timings
- How we measure
Your browser sends three small requests to gemini.google.com, with no cookies. The provider sees your IP address, as it does whenever you use Gemini. The result stays on this page and is not sent to us.
gemini.google.com
The front page of gemini.google.com, answered by Google's servers. We do not sign in or send a prompt, so this is the way in to Gemini, not a conversation. It is the one host here that is not behind Cloudflare.
| Timed from | Usual | Now | Last 24 hours | Reading |
|---|---|---|---|---|
| Your network | ||||
| United Statesyour comparison | 174 | 186 | On time | |
| Canada | 182 | 262 | On time | |
| Brazil | 560 | 638 | On time | |
| United Kingdom | 129 | 180 | On time | |
| Germany | 153 | 212 | On time | |
| France | 150 | 148 | On time | |
| India | 209 | 254 | On time | |
| Singapore | 116 | 191 | On time | |
| Japan | 151 | 278 | On timelast round slow, not confirmed | |
| Australia | 419 | 442 | On time |
Why is Gemini slow?
Right now the way in to Gemini answers at its usual speed from every country we time it from. If Gemini is slow for you, the time is going somewhere our probes do not reach. Slowness can sit in three places.
- Your own connection. Wi-Fi, mobile data, a VPN or a company proxy sit between you and Gemini, and our probes do not share that path. The button above times the same hosts from your browser: if your times are slow while the probes in your country are not, the delay is on your side.
- The answer being written. Our times end at the first byte of the server's reply. A model writes after that, piece by piece, so long answers, hard prompts and modes that reason before answering take longer, and a long conversation gives it more to read before it starts. We time none of this.
- The provider. A busy or failing model is for Google to report. Its status page is quoted at the top of this page and part by part below.
For a slow or unstable connection, Google's own troubleshooting page says to switch networks, and when Gemini has high traffic, to wait five minutes and try again: Troubleshoot error codes in Gemini Apps
Reading the board
The probes are machines in datacenters, one or two per country. Every 15 minutes they time the same request, and the board shows the middle value. "Usual" is the middle value over the last seven days from the same probes.
The trace draws each round as a multiple of the usual time. The lower line is usual, the upper line is twice usual, and a yellow dot marks a round at or above it. One slow round is common and is not a delay. A country reads "Delayed" only when a probe is that slow in two of three rounds while it times another provider's hosts normally.
Google's status page, part by part
We have no current part-by-part report from Google's status page.
Confirmed delays for Gemini in the last seven days
- gemini.google.com from Singapore, Singapore (LeaseWeb network)
14 Nov, 13:22 to 13:37 UTC; up to 294 ms against a usual 118 ms, in 2 rounds. - gemini.google.com from Mumbai, India (Oracle network)
13 Nov, 00:22 to 00:52 UTC; up to 546 ms against a usual 194 ms, in 2 rounds. - gemini.google.com from Mumbai, India (Oracle network)
11 Nov, 22:37 to 22:52 UTC; up to 426 ms against a usual 194 ms, in 2 rounds. - gemini.google.com from Mumbai, India (Oracle network)
10 Nov, 23:22 to 23:37 UTC; up to 582 ms against a usual 194 ms, in 2 rounds. - gemini.google.com from Mumbai, India (Oracle network)
10 Nov, 20:37 to 20:52 UTC; up to 433 ms against a usual 194 ms, in 2 rounds.