Grok outages and problems
In the past 24 hours, 813 user reports came in for Grok. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 95.83% uptime for the day.
The most recent spike big enough to count as an outage was 14 hours ago. The busiest 15-minute window of the day had 160 reports, about 15 hours ago.
-
Elevated reports
Ended 2 h agoLasted 15 min16peak reports
-
Elevated reports
Ended 3 h agoLasted 15 min13peak reports
-
Elevated reports
Ended 4 h agoLasted 15 min15peak reports
-
Outage
Ended 14 h agoLasted 1 h160peak reports
Grok in October 2026
- Problem reports in October (since 5 October)
- 7,626
- Most reported this month
- No. 15 of 1,284
Monthly report for October 2026
What went wrong
What people said was wrong in recent problem reports for Grok worldwide.
Share of 195 recent reports that said what was wrong, from every country listed below.
Grok reports around the world
In the last 24 hours, 1,268 problem reports about Grok came in from 57 countries. Right now reports are at the usual level in every country.
- Outage now
- Problems now
- Normal
| Country | Now | Last hour | 24 hours |
|---|---|---|---|
| The US numbers above | Normal | 24 | 810 |
| Canada | Normal | 5 | 64 |
| The UK | Normal | 3 | 45 |
| South Africa | Normal | 2 | 3 |
| Germany | Normal | 1 | 47 |
| Brazil | Normal | 1 | 18 |
| The Philippines | Normal | 1 | 10 |
| Belgium | Normal | 1 | 3 |
| Austria | Normal | 1 | 2 |
| Argentina | Normal | 1 | 2 |
| Russia | Normal | 1 | 1 |
| Japan | Normal | 0 | 33 |
Each country's status compares its reports with the usual level there. 60 more countries had 230 reports in the last 24 hours. Map outlines: Natural Earth.
Grok problem spikes, last 30 days
Since 5 October, Grok had 8 outage spikes and 9 periods of elevated reports. The longest lasted 4 h 39 min, on 27 October.
- Fri 2 Oct: no data
- Sat 3 Oct: no data
- Sun 4 Oct: no data
- Mon 5 Oct: 2 reports
- Tue 6 Oct: 0 reports
- Wed 7 Oct: 24 reports
- Thu 8 Oct: 3 reports
- Fri 9 Oct: 3 reports
- Sat 10 Oct: 1 report
- Sun 11 Oct: 0 reports
- Mon 12 Oct: 7 reports
- Tue 13 Oct: 5 reports
- Wed 14 Oct: 6 reports
- Thu 15 Oct: 4 reports
- Fri 16 Oct: 0 reports
- Sat 17 Oct: 0 reports
- Sun 18 Oct: 2 reports
- Mon 19 Oct: 2 reports
- Tue 20 Oct: 1 report
- Wed 21 Oct: no data
- Thu 22 Oct: 0 reports
- Fri 23 Oct: 24 reports (outage spike that day)
- Sat 24 Oct: 20 reports
- Sun 25 Oct: 13 reports
- Mon 26 Oct: 3 reports
- Tue 27 Oct: 6 reports (outage spike that day)
- Wed 28 Oct: 3,499 reports (outage spike that day)
- Thu 29 Oct: 503 reports (outage spike that day)
- Fri 30 Oct: 2,740 reports (outage spike that day)
- Sat 31 Oct: 758 reports (outage spike that day)
-
Elevated reports
Sat 31 Oct, 20:18–20:33Lasted 15 min18peak reports
-
Elevated reports
Sat 31 Oct, 19:08–19:23Lasted 15 min18peak reports
-
Elevated reports
Sat 31 Oct, 18:08–18:23Lasted 15 min13peak reports
-
Elevated reports
Sat 31 Oct, 17:08–17:23Lasted 15 min17peak reports
-
Elevated reports
Sat 31 Oct, 14:55–15:10Lasted 15 min13peak reports
-
Outage
Sat 31 Oct, 06:23–07:23Lasted 1 h178peak reports
-
Outage
Fri 30 Oct, 19:48–20:33Lasted 45 min143peak reports
-
Elevated reports
Fri 30 Oct, 13:09–13:26Lasted 17 min10peak reports
9 earlier spikes in this period.
By country
Each square is one day in the countries with the most reports: red when reports stayed at outage level for half an hour or more, amber when they stayed above the usual level for an hour or more, grey otherwise.
- The US7,589
- The UK612
- Canada603
- Brazil304
- Germany295
- Australia246
- Mexico207
- Japan166
Country history starts on 28 October 2026. Days run from midnight to midnight, Central European time.
A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 5 October 2026. Monthly reports for all services
How to fix Grok not working
When Grok itself is having trouble, these steps won't bring it back, but they will rule out anything on your side:
Your browser tries to reach x.ai over your own connection, right now. Nothing is sent to us or stored.
Start a fresh Grok chat
Long threads can stall partway through a reply, and a new conversation often clears that up because it starts without all the earlier context. Open a new chat and resend your prompt. If it answers there, the old thread was the problem.
Compare with the xAI status page
Open the official status page at https://status.x.ai and look for an open incident. If nothing is listed, the fault is probably on your side, though smaller outages sometimes show up there late. The status at the top of this page counts user problem reports in 15-minute windows over the last 24 hours, so a jump in reports with a clean official page can still mean the trouble is wider than you.
Switch between X and the standalone app
Grok runs inside X and as its own app, so if one keeps failing, try the other while signed in with the same account. On a phone, move from Wi-Fi to mobile data or turn off any VPN, because some networks and VPN exits get blocked or rate limited.
Clear app data or reinstall Grok
On Android, go to Settings > Apps > Grok > Storage (or Storage and cache) and tap Clear cache; on iPhone, press and hold the app icon, tap Remove App, then reinstall it from the App Store. In a browser, clear cookies and site data for the site and sign in again. Still stuck? The help centre at https://help.x.ai covers account and sign-in problems.
While Grok is down: what to use instead
- Grok inside X If the standalone app won't load, try the Grok tab in the X app or on the X website, which sometimes keeps answering, though a wider outage on xAI's side tends to take both down.
- Switch between web and app Use the browser when the phone app hangs on a reply that never finishes, or the reverse, because a bad app update or a stale login can break one without touching the other.
- ChatGPT Fine for drafting, summaries and code help while you wait, but it won't pull in live posts from X the way Grok does.
- Claude Paste in a long document or a chunk of code when you can't wait for the service to come back.
Fix Grok on Windows, Mac, Android and iPhone
Grok on Windows
- Fix
- Clear your web browser's cache and cookies, or try accessing Grok in an Incognito window. You can also disable browser extensions that might block the X platform.
- Check
- Attempt to open the Grok interface in a different web browser, or check your browser's developer console for network connection errors.
ping x.aiTest whether Grok's servers replynslookup x.aiCheck that Grok's DNS resolvestracert x.aiTrace where the connection dropsipconfig /flushdnsClear the DNS cache, then reloadGrok on Mac
- Fix
- Force refresh the page in Safari or Chrome, or temporarily disable any macOS VPN or firewall settings that might block Grok.
- Check
- Test if Grok loads in Safari's Private Browsing mode, or check your network connection to the X domain using macOS diagnostics.
ping -c 4 x.aiTest whether Grok's servers replynslookup x.aiCheck that Grok's DNS resolvestraceroute x.aiTrace where the connection dropssudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderFlush the macOS DNS cache, then reloadGrok on Android
- Fix
- Clear the X app cache in your Android system settings, force stop the app, or update it to the latest version via the Google Play Store to fix Grok.
- Check
- Try accessing Grok through a mobile web browser on your device to see if the issue is isolated to the Android app.
Grok on iPhone and iPad
- Fix
- Force close and restart the X app on your iPhone or iPad, or check the Apple App Store for any pending updates that restore Grok functionality.
- Check
- Switch from Wi-Fi to cellular data, or try loading Grok in Safari to verify if the iOS app is experiencing a localized outage.
Biggest Grok problems so far
-
1
OutageLasted 3 h 37 min1,507reports in 15 min
-
2
OutageLasted 3 h 29 min476reports in 15 min
-
3
OutageLasted 1 h178reports in 15 min
Ranked by the most problem reports in one 15-minute window. Our archive started on 5 October 2026, so earlier problems are not counted. Times are Central European time.
Problems at the same time as Grok
Since 5 October, all 17 of Grok's spikes in problem reports overlapped a spike at another service.
When several services get problem reports at once, something they share, such as a cloud host or a network, can be the real cause. Matching times alone do not prove it.
Most often at the same time
- Archive of Our Own15 times
- Capital One11 times
- Starbucks11 times
- Costco10 times
- Discord9 times
- Cricket Wireless9 times
How many of Grok's spikes overlapped one of theirs.
During the latest spike
Grok: Sat 31 Oct, 20:18 to 20:33
- Archive of Our Own, outage,29 Oct 07:55 to 21:23
- YouTube, outage,00:53 to 21:23
- Starbucks, outage,13:23 to 21:23
- Costco, outage,14:23 to 20:23
- Discord, outage,15:23 to 20:53
- EA, outage,16:53 to 20:23
- Pavlov Media, outage,17:08 to 21:23
- Bank of America, outage,17:23 to 21:23
19 more services. Red dot: outage. Amber dot: elevated reports.
A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.
When people report Grok problems
The busiest hour for reports about Grok is 19:00 to 20:00 Central European time, and the busiest day is Thursday.
By hour of the day
- 00:00 to 01:00: 1.1 reports on an average day
- 01:00 to 02:00: 2.3 reports on an average day
- 02:00 to 03:00: 2.3 reports on an average day
- 03:00 to 04:00: 1.9 reports on an average day
- 04:00 to 05:00: 1.4 reports on an average day
- 05:00 to 06:00: 1.7 reports on an average day
- 06:00 to 07:00: 1.6 reports on an average day
- 07:00 to 08:00: 1.9 reports on an average day
- 08:00 to 09:00: 1 report on an average day
- 09:00 to 10:00: 0.78 reports on an average day
- 10:00 to 11:00: 1.2 reports on an average day
- 11:00 to 12:00: 1.9 reports on an average day
- 12:00 to 13:00: 1.8 reports on an average day
- 13:00 to 14:00: 2.2 reports on an average day
- 14:00 to 15:00: 2.7 reports on an average day
- 15:00 to 16:00: 2.8 reports on an average day
- 16:00 to 17:00: 3.1 reports on an average day
- 17:00 to 18:00: 3.2 reports on an average day
- 18:00 to 19:00: 2.6 reports on an average day
- 19:00 to 20:00: 3.2 reports on an average day
- 20:00 to 21:00: 2.8 reports on an average day
- 21:00 to 22:00: 2.8 reports on an average day
- 22:00 to 23:00: 1.8 reports on an average day
- 23:00 to 00:00: 1.7 reports on an average day
By day of the week
- Monday: 4.1 reports on an average Monday
- Tuesday: 3.1 reports on an average Tuesday
- Wednesday: 31 reports on an average Wednesday
- Thursday: 119 reports on an average Thursday
- Friday: 96 reports on an average Friday
- Saturday: 91 reports on an average Saturday
- Sunday: 4.9 reports on an average Sunday
Each bar is the average number of user reports in that hour, or on that day of the week, from 24 days of reports since 5 October 2026. The busiest bar is highlighted. Spikes in reports are left out, so one outage does not set the pattern.
What happens when Grok goes down
Grok is the AI assistant from xAI, the company Elon Musk founded in 2023, and you can use it in a browser, on iPhone, on Android and inside X. People rely on it for coding help and quick answers about posts on X, while developers build on the xAI API, so an outage can stall a draft halfway through or break an app that calls it in the background.
Chat usually goes first. You send a prompt and the reply either hangs on a loading indicator or stops partway through a sentence, and your past conversations may not open from the sidebar at all. Image generation and voice mode often break separately from text, so you might still get written answers while pictures time out or voice refuses to connect. Problems are often partial: Grok inside X can fail while the standalone app works, or the trouble can reach some accounts or regions before others, so check the official status page at https://status.x.ai to see whether xAI has posted an incident.
Grok IP address, servers and network
- IPv4 addresses
- 104.18.18.80
Show all 2
- 104.18.19.80
- IPv6 addresses
- 2606:4700::6812:1250
Show all 2
- 2606:4700::6812:1350
- Network
- AS13335 · Cloudflare, Inc., registered in the United States
- Served through
- Cloudflare · our check was answered by its Frankfurt (FRA) data centre
- DNS hosted by
- Cloudflare
- HTTPS certificate
- Issued by Google Trust Services, valid until 25 Jan 2027 (85 days)
- HTTP/3
- Not advertised
- Our check
- Answered in 99 ms (it turned away our automated check, which is common)
Checked from our server in Frankfurt, Germany, 15 h ago, for x.ai. A service behind a CDN answers from many data centres, usually the one nearest to you, so these addresses are where its traffic enters, not where its own servers stand. Visitors elsewhere may see different addresses.
Checked from 11 places around the world
All 11 locations got an answer from x.ai. Fastest from Los Angeles (117 ms), slowest from Singapore (294 ms). Every location connected through Cloudflare, Inc. (AS13335), using 3 different addresses.
| Location | Result | Time | Address reached |
|---|---|---|---|
| FrankfurtGermany | Up | 132 ms | 104.18.19.80 |
| ViennaAustria | Up | 277 ms | 104.18.19.80 |
| MilanItaly | Up | 235 ms | 104.18.18.80 |
| ParisFrance | Up | 159 ms | 104.18.19.80 |
| AmsterdamNetherlands | Up | 212 ms | 104.18.19.80 |
| MadridSpain | Up | 193 ms | 8.6.112.0 |
| WarsawPoland | Up | 195 ms | 104.18.18.80 |
| Los AngelesUSA | Up | 117 ms | 104.18.19.80 |
| São PauloBrazil | Up | 275 ms | 104.18.19.80 |
| SingaporeSingapore | Up | 294 ms | 104.18.18.80 |
| TokyoJapan | Up | 227 ms | 104.18.19.80 |
Checked with check-host.net from its servers in these cities 15 h ago, for x.ai. Time is how long each server took to load the page.
Grok FAQ
Is Grok down right now?
Why does Grok say I've hit my limit when I've barely used it?
I pay for X Premium, so why are Grok features still locked?
Why does Grok stop halfway through an answer or show 'Something went wrong'?
Why won't the app make the image I asked for?
Service updates from @grok
No posts about problems from @grok in the last 14 days. The latest is from .
How we track Grok
The status on this page comes from user-submitted problem reports for Grok, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for Grok, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.
When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. This is separate from Grok's official status page: user reports tend to show a problem early, while the official page confirms the cause. If the two disagree, check both.