When Grok stops loading, hangs on a blank screen, or throws an error mid-response, the first question is always the same: is it Grok, or is it me? This guide walks through how to tell the difference, the most common reasons Grok stops working, and the fastest fixes for each. If you want the short answer before reading on, check the live Grok status page first. It shows current availability, recent uptime, and crowd-sourced reports from other users, which is the quickest way to rule out a wider problem.
First, Check Whether Grok Itself Is Down
Before you change a single setting, confirm where the problem actually lives. Most “Grok not working” moments fall into one of two buckets: a service-side disruption affecting everyone, or a local issue affecting only you. Spending two minutes on this saves you from clearing caches and reinstalling apps when the real fix is simply to wait.
The fastest signal is our live monitoring. The Grok status page tracks whether the service is responding and aggregates reports from people hitting the same wall right now. If reports are spiking and the status shows degraded or down, the problem is on xAI’s side and there is nothing to fix on your end. If everything looks green, the issue is more likely local, and the steps further down this guide will help.
For a deeper walkthrough of separating a real outage from a personal glitch, our guide on how to tell if an AI service is down or it is just you covers the full diagnostic flow, including how to test from a second device or network.
Quick Triage Checklist
- Check the live status: Open the Grok status page and look for spikes in user reports.
- Test a second site: If other websites and apps also fail, your connection is the suspect, not Grok.
- Switch networks: Move from Wi-Fi to mobile data (or vice versa) and retry. A different result points to your network.
- Try another device: If Grok works on your phone but not your laptop, the fault is local to that one device.
- Note the exact error: A login error, a timeout, and a “high demand” message each point to different causes.
Common Reasons Grok Is Not Working
Grok runs as a web app, a standalone mobile app, and as an assistant woven into X. That spread means a few distinct categories of failure, and the right fix depends on which one you are hitting.
Server Load and High Demand
AI assistants are compute-heavy, and Grok is no exception. When a popular feature launches or usage surges, the service can throttle requests, slow down dramatically, or return capacity messages instead of answers. You might see a spinner that never resolves, a “try again later” notice, or replies that cut off partway. This is the single most common reason a healthy account suddenly cannot get a response, and it is entirely on the provider’s side. When demand is the cause, the live status page usually shows a coordinated spike in reports. The only real fix is patience, which we cover at the end of this guide.
Regional and Network-Level Issues
Grok availability is not uniform everywhere. Some regions have limited or no official access, and a connection that worked yesterday can fail after a routing change, an ISP issue, or a corporate or school firewall that blocks the domain. If you recently changed networks, traveled, or started using a VPN, that shift alone can break access. Likewise, a VPN exit node in an unsupported region can trigger errors even when your home connection would work fine. Toggling the VPN off, or switching to a server in a supported region, is a fast test.
Account and Authentication Problems
Because Grok ties into X accounts and subscription tiers, a surprising number of failures are really login or entitlement problems wearing an outage costume. Common variants include an expired session, a password change on the linked account, a subscription that lapsed, or a feature gated behind a tier you are not on. If Grok loads but refuses to respond, loops you back to a sign-in screen, or says you lack access to a feature, treat it as an auth issue rather than a server outage. Signing out and back in clears most of these.
X Integration Hiccups
When you use Grok inside X, you now depend on two systems working together. If X itself is having trouble, the embedded Grok assistant can fail even when the standalone Grok app and website are perfectly healthy. The reverse is also true. This is why testing Grok in more than one place is so useful: if the X-integrated version is broken but the dedicated app works, the problem is the integration layer or X, not Grok’s core model service.
Browser Cache, Extensions, and Stale Sessions
On the web, a stale cache is a classic culprit. An old cached version of the app, a half-loaded script, or a corrupted session token can leave you staring at a blank page or a UI that will not accept input. Browser extensions are the other frequent offender. Ad blockers, privacy tools, script blockers, and aggressive anti-tracking extensions can interfere with the requests Grok needs to make, breaking logins or blocking responses. Testing in a private or incognito window, which disables most extensions by default, isolates this quickly.
App Version and Device Issues
On mobile, an outdated app build can break against updated servers, push notifications can stall, and background data restrictions or battery-saver modes can quietly choke the connection. A device that has been awake for days, a full cache, or a flaky background refresh can all produce symptoms that look like a Grok outage but are really local to your phone.
Step-by-Step Fixes
Work through these in order. They are arranged from fastest and least disruptive to more involved, so you rarely need to reach the bottom of the list.
1. Confirm It Is Not a Wider Outage
Open the Grok status page first. If it shows a problem and reports are climbing, stop here and wait, since none of the steps below will help during a service-side incident. You can also glance at the full live dashboard to see whether related services are wobbling at the same time, which sometimes points to a broader infrastructure issue.
2. Reload and Retry Cleanly
Do a hard refresh on the web (reload while bypassing the cache) or fully close and reopen the mobile app, swiping it out of the recent-apps list rather than just backgrounding it. A surprising share of transient errors clear with a clean restart, because the previous attempt left a stuck request or a stale token behind.
3. Test Your Connection
Load two or three unrelated websites. If they are slow or failing too, the issue is your internet, not Grok. Switch between Wi-Fi and mobile data, restart your router if needed, and try again. A different result on a different network is strong evidence the fault was local.
4. Sign Out and Back In
If Grok loads but will not respond or keeps bouncing you to a login screen, sign out completely and sign back in. This refreshes your session token and reauthenticates against the linked account, which resolves most authentication and entitlement errors. Confirm the linked X account is in good standing and that any required subscription is still active.
5. Clear Cache or Try Incognito
On the web, open a private or incognito window and try Grok there. If it works, the problem is your normal browser’s cache or an extension. Clear the cache for the site, then disable extensions one at a time, starting with ad blockers and privacy tools, until the conflict disappears. On mobile, clear the app’s cache in your device settings, or reinstall the app if clearing does not help.
6. Disable VPN and Check Region
If you use a VPN or proxy, turn it off and retry. If Grok works without it, your VPN exit point was likely in an unsupported region or was being blocked. Where access is restricted in your actual location, a supported-region server may be required, but always confirm you are within Grok’s terms of use.
7. Update the App and Your Device
Check your app store for a pending Grok update and install it. Outdated builds are a common cause of mobile failures after a server-side change. Restarting the device itself clears stuck background processes and refreshes network state, and it is a reliable last-resort local fix.
When You Should Just Wait
Sometimes the correct move is to do nothing. If the live status confirms a service-side problem, no amount of cache clearing or reinstalling will bring Grok back faster. Provider-side incidents, capacity throttling, and integration outages are resolved by xAI’s engineers, not by you. In those moments, the productive thing is to step away and check back rather than burn time on fixes that cannot work.
The same applies to high-demand slowdowns. When a service is overloaded, hammering it with retries can make your own experience worse. Give it a few minutes, then try again. For a complete playbook on staying productive during a confirmed disruption, including how to set expectations and avoid losing work, read our guide on what to do when an AI tool is down.
Keep Working During an Outage
If you have a deadline and Grok is genuinely down, switching tools temporarily is often the pragmatic choice. Other assistants such as Claude, ChatGPT, and Gemini handle many of the same tasks, and you can check their live status alongside Grok’s on our main dashboard before you commit. Our roundup of the best AI alternatives to use during an outage compares them by strength so you can pick a stand-in quickly. If you are curious why these disruptions happen in the first place, our explainer on why AI tools go down covers the infrastructure side in plain language.
How We Track Grok Status
The status data on this site comes from continuous automated monitoring combined with reports submitted by real users. When you see a spike on the Grok status page, it reflects both our checks and a surge of people reporting the same trouble at the same time, which is a far more reliable signal than a single failed request on your own machine. You can read exactly how we measure availability on our methodology page, and you can browse every other tool we track from the guides hub. The goal is simple: give you a fast, honest answer to “is it Grok or is it me?” so you can stop guessing and get back to work.
Frequently asked questions
How do I know if Grok is down for everyone or just me?
Check the live Grok status page first. If it shows a problem and user reports are spiking, the issue is service-side and affects everyone. If it looks healthy, test Grok on a second device or a different network, such as switching from Wi-Fi to mobile data. If it works elsewhere, the fault is local to your original device or connection rather than Grok itself.
Why does Grok load but refuse to respond to my messages?
This usually points to an authentication or capacity issue rather than a full outage. Your session token may have expired, your linked account may need reauthentication, or the feature may require a subscription tier you are not on. Signing out and back in fixes most session problems. If the status page shows high demand, the service may simply be throttling responses, in which case waiting a few minutes is the fix.
Can a VPN cause Grok to stop working?
Yes. A VPN can route your traffic through a region where Grok access is limited or blocked, which produces errors even when your normal connection would work fine. Turn the VPN off and retry. If Grok then loads, the VPN exit location was the cause. Switching to a server in a supported region can help, but always stay within Grok's terms of use for your actual location.
Why does Grok work in the X app but not the standalone app, or vice versa?
Grok runs in several places, and they can fail independently. When you use Grok inside X, you depend on both systems working together, so an X-side problem can break the embedded assistant while the dedicated Grok app stays healthy. Testing both versions tells you whether the issue is the integration layer or Grok's core service. Use whichever one is currently responding.
Grok is confirmed down. Should I keep retrying or just wait?
If the live status confirms a service-side outage, wait rather than retry. Cache clearing, reinstalling, and repeated requests will not bring it back faster, and hammering an overloaded service can worsen your own experience. Step away and check the status page periodically. If you have a deadline, switch temporarily to another assistant like Claude, ChatGPT, or Gemini, checking their status first on the main dashboard.