Grok is answering at its usual speed from all 9 countries we time it from.
Our probes' last round was at 14:07 UTC. The last report we read from xAI's status page (12 Nov, 16:25 UTC) listed Grok as operational. It has expired and may not describe the present. Open the status page
Grok over the last 24 hours
Status pageGrok
No current report
Our timinggrok.com
On time from 9 countries
The bands in words
- xAI's status page for Grok: No report read for the whole 24 hours.
- Our timing of grok.com: Delayed 13 Nov, 14:22 to 18:22 UTC; delayed 13 Nov, 18:37 to 19:22 UTC; delayed 13 Nov, 19:37 to 20:22 UTC; no timings 05:22 to 05:37 UTC; no answer 07:22 to 08:07 UTC; delayed 10:07 to 10:52 UTC. On time the rest of the time.
What the status page listed
We have no current report from xAI's status page for Grok. The last one we read was at 12 Nov, 16:25 UTC. Our latest attempt to read it, at 13:30 UTC, failed.
What our probes confirmed
- grok.com from Sao Paulo, Brazil (Oracle network)
14 Nov, 10:07 to 10:37 UTC; up to 904 ms against a usual 398 ms, in 2 rounds. - grok.com from Sao Paulo, Brazil (Oracle network)
14 Nov, 07:37 to 07:52 UTC; no answer in 2 rounds. - grok.com from Saint-Laurent, Canada (OVH network)
14 Nov, 07:37 to 07:52 UTC; no answer in 2 rounds. - grok.com from London, United Kingdom (OVH network)
14 Nov, 07:07 to 07:52 UTC; no answer in 3 rounds. - grok.com from London, United Kingdom (Oracle network)
14 Nov, 07:07 to 07:52 UTC; no answer in 3 rounds. - grok.com from Buffalo, United States (HostPapa network)
14 Nov, 07:07 to 07:52 UTC; no answer in 3 rounds. - grok.com from Montreal, Canada (OVH network)
14 Nov, 07:07 to 07:37 UTC; no answer in 2 rounds. - grok.com from Roubaix, France (OVH network)
14 Nov, 07:07 to 07:37 UTC; no answer 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 grok.com, with no cookies. The provider sees your IP address, as it does whenever you use Grok. The result stays on this page and is not sent to us.
grok.com
The front page of grok.com, answered by xAI's servers and not from a cache. We do not sign in or send a prompt, so this is the way in to Grok on its own site. Grok inside X is not timed.
| Timed from | Usual | Now | Last 24 hours | Reading |
|---|---|---|---|---|
| Your network | ||||
| United Statesyour comparison | 384 | 592 | On timelast round slow, not confirmed | |
| Canada | 400 | 292 | On time | |
| Brazil | 406 | 366 | On time | |
| United Kingdom | 467 | 306 | On time | |
| Germany | 408 | 336 | On time | |
| France | 468 | 371 | On time | |
| India | 600 | 514 | On time | |
| Singapore | – | – | too few rounds | Not timedour probes get a bot check here |
| Japan | 468 | 365 | On time | |
| Australia | 545 | 706 | On time |
Why is Grok slow?
Right now the way in to Grok answers at its usual speed from every country we time it from. If Grok 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 Grok, 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 xAI to report. Its status page is quoted at the top of this page and part by part below.
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.
xAI's status page, part by part
We have no current part-by-part report from xAI's status page.
Confirmed delays for Grok in the last seven days
- grok.com from Sao Paulo, Brazil (Oracle network)
14 Nov, 10:07 to 10:37 UTC; up to 904 ms against a usual 398 ms, in 2 rounds. - grok.com from Sao Paulo, Brazil (Oracle network)
14 Nov, 07:37 to 07:52 UTC; no answer in 2 rounds. - grok.com from Saint-Laurent, Canada (OVH network)
14 Nov, 07:37 to 07:52 UTC; no answer in 2 rounds. - grok.com from London, United Kingdom (OVH network)
14 Nov, 07:07 to 07:52 UTC; no answer in 3 rounds. - grok.com from London, United Kingdom (Oracle network)
14 Nov, 07:07 to 07:52 UTC; no answer in 3 rounds. - grok.com from Buffalo, United States (HostPapa network)
14 Nov, 07:07 to 07:52 UTC; no answer in 3 rounds. - grok.com from Montreal, Canada (OVH network)
14 Nov, 07:07 to 07:37 UTC; no answer in 2 rounds. - grok.com from Roubaix, France (OVH network)
14 Nov, 07:07 to 07:37 UTC; no answer in 2 rounds.