Grok stuck on “Something went wrong”, not replying on X, logging you out, or throwing a 429 error in your code? Most Grok problems fall into one of five groups: an xAI outage, a usage limit, an account or plan issue, a broken app or browser cache, or a network block such as a VPN.
This guide gives you a 60-second check to find which one you have, then exact fixes for grok.com, the iPhone and Android apps, Grok inside X, Tesla cars and the xAI API. It also covers what each error code means and what to use while Grok is down.
- Check status.x.ai first. It lists the API, grok.com, mobile apps, Voice and Grok Build separately. If there is an incident, wait.
- Hit your limit? Free and paid plans have caps. Wait for the reset or upgrade.
- Web fixes: hard refresh (Ctrl+Shift+R), try incognito, allow cookies for grok.com and x.com, disable ad blockers, turn off VPN.
- App fixes: update the app, force close, sign out and in, restart the phone, clear cache (Android) or offload (iPhone).
- @grok not replying on X? Use the Grok tab directly and check your X plan includes Grok.
- API: 401 or 400 = bad key, 429 = rate limit or no credit, 5xx = xAI side.
60-Second Diagnosis
- Open status.x.ai. Any open incident for grok.com, mobile apps or API? If yes, it is not you.
- Try another device or network. Works on mobile data but not Wi-Fi? It is your network, VPN or firewall.
- Open grok.com in a private window. Works there? Your cache or an extension is the problem.
- Read the exact message. “Limit reached” or “upgrade” means a plan cap, not a bug.
- Check you are signed into the right account, especially if you have both an X login and an email login.
Is Grok Down Right Now?
xAI runs an official status page at status.x.ai. It tracks the API, the US endpoint, Grok Build, grok.com, the mobile apps and Voice as separate rows, so one can fail while others work.
Recent examples show how varied outages are:
| Date | What broke |
|---|---|
| September 22, 2026 | Datacenter incident hit the API, grok.com and Grok Build together |
| October 7, 2026 | grok.com outage while the API stayed up |
| November 5, 2026 | Grok Bot errors for about 75 minutes (00:34 to 01:49 UTC), rated minor |
| November 10, 2026 | Usage data slow or unavailable for some users |
Other quick signals: search “Grok down” on X for live reports, or follow @xAI for incident posts. If status.x.ai is green but many people report problems, it may be high demand that has not been logged yet.
Common Grok Errors and What They Mean
| What you see | Likely cause | Fix |
|---|---|---|
| “Something went wrong” | Server hiccup, stale session or cache | Refresh, start a new chat, sign out and in, check status page |
| Endless loading / no reply | Network, VPN, extensions or overload | Switch network, disable VPN and ad blockers, retry shorter prompt |
| Limit reached / upgrade prompt | Plan usage cap | Wait for reset or upgrade |
| Login loop or blank screen | Corrupted session or blocked cookies | Clear cookies for grok.com and x.com, sign in again |
| Grok not available in your region | Regional restriction or VPN exit country | Turn off VPN; check Grok is offered in your country |
| @grok ignores you on X | Tag queue lag, plan access or VPN | Use the Grok tab, check plan, retry later |
| Image or video won’t generate | Content filter, feature cap or load | Rephrase prompt, check plan limits, try later |
Fix Grok on grok.com (Web)
- Hard refresh: Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac.
- Open a private or incognito window and sign in. If it works, the problem is your cache or extensions.
- Allow cookies for grok.com and x.com (and accounts.x.ai for sign-in).
- Disable ad blockers and privacy extensions for grok.com.
- Clear site data: in Chrome, click the icon left of the address, choose Site settings, then Delete data.
- Turn off VPN, proxy or DNS filters (some corporate or school firewalls block AI sites).
- Try another browser (Chrome, Edge, Firefox, Safari), fully updated.
- Start a new conversation. Very long chats can fail or slow down.
Fix the Grok App on iPhone
- Update Grok in the App Store.
- Force close: swipe up from the bottom, then swipe the Grok card away. Reopen.
- Sign out and back in from the app’s settings.
- Restart the iPhone.
- Check iOS is up to date in Settings > General > Software Update.
- Check background data: Settings > Grok > Mobile Data should be on.
- Offload and reinstall: Settings > General > iPhone Storage > Grok > Offload App, then reinstall. This resets local data without losing cloud chats.
Fix the Grok App on Android
- Update Grok in Google Play.
- Force stop: Settings > Apps > Grok > Force stop.
- Clear cache: Settings > Apps > Grok > Storage > Clear cache. (Clear storage signs you out.)
- Sign out and back in.
- Turn off battery saver or data saver for Grok, which can kill long replies.
- Restart the phone and update Android.
- Reinstall if nothing else works.
Fix Grok in X (Twitter)
- Use the Grok tab instead of tagging @grok. Tag replies queue up under heavy load.
- Check your X plan includes the Grok features you are trying to use.
- Update the X app and sign out and in.
- Turn off VPN or proxy.
- Clear the X app cache (Android) or reinstall (iPhone).
- Test on x.com in a browser to see whether the app or account is the issue.
Remember that Grok in X and grok.com have separate chat histories and settings. See delete Grok history for where each is controlled.
Login, Verification and Account Problems
- Wrong account: you may have one account via X and another via email or Google. Sign out and pick the one with your chats or subscription.
- Phone verification fails: wait a few minutes, try again, and do not use a VoIP number. If it keeps failing, contact support with a screenshot.
- Account recently deleted: you can usually restore by signing in within 30 days.
- Subscription not showing: sign in with the account you paid with, and restore purchases in the app if you bought through Apple or Google.
- Age checks: some features need age confirmation in certain countries.
Usage Limits and “Upgrade” Messages
Grok has message and generation caps on every plan, and they vary by model and feature. When you hit one, Grok tells you to wait or upgrade.
- Wait for the reset shown in the message.
- Switch to a lighter model if the app offers one; caps are usually higher.
- Upgrade to a paid tier of The X Subscription (Plus $8, Premium $30, Super $100 or Ultra $200 a month since October 12, 2026). Compare in our Grok pricing guide and is Grok free.
Image, Video and Voice Not Working
| Feature | Common cause | Fix |
|---|---|---|
| Grok Imagine images | Prompt blocked by content rules, daily cap | Rephrase, remove real people’s names, wait for reset |
| Grok Imagine video | Plan limits, long queue | Check plan, try shorter clips. See our Grok video guide |
| Voice mode | Mic permission off, Voice incident | Allow microphone in phone settings, check the Voice row on status.x.ai |
| File uploads | File too large or unsupported type | Use PDF, DOCX, TXT or images; split big files |
| Web search answers old | Search not triggered | Ask “search the web for…” explicitly |
Grok Not Working in a Tesla
- Install pending updates under Controls > Software.
- Check connectivity: Premium Connectivity or strong Wi-Fi.
- Confirm Grok is offered in your region and on your car.
- Reboot the touchscreen by holding both scroll wheels until the screen turns off and restarts.
Grok API Errors (Developers)
| Code | Meaning | Fix |
|---|---|---|
| 400 (invalid-argument) | Bad request or wrong key format | Check JSON body, model name and key |
| 401 | Missing, wrong or expired API key | Create a new key in the xAI console; remove stray spaces |
| 402 | Prepaid credit or weekly pool used up | Add credit or wait for the reset |
| 429 | Rate limit for your plan, team or model | Back off and retry with exponential delay; do not loop resend |
| 500 | Internal xAI error | Retry; if it persists, check status.x.ai |
| 502 / 503 / 504 | Busy, unavailable or timeout | Retry later; check for an incident |
A simple retry pattern in Python:
import time, random
for attempt in range(6):
try:
resp = client.chat.create(model="grok-4.7", messages=msgs) # your call
break
except Exception as e:
if attempt == 5: raise
time.sleep(min(30, 2 ** attempt) + random.random())
If only the global API fails, xAI offers a US regional endpoint (https://us.api.x.ai/v1) for some models, at a higher per-token price. Full setup is in our Grok API Python tutorial, and rate limit tiers across providers are in LLM API rate limits explained.
What to Use While Grok Is Down
- ChatGPT for general chat and images.
- Claude for writing, coding and long documents. New? Read how to use Claude.
- Gemini for Google search-backed answers.
- A local model that never goes down, such as one running in Ollama on your own PC.
How to Contact xAI Support
- In grok.com or the app, open Settings and look for Help or Feedback.
- Describe the problem, device, app version and time it happened.
- Attach a screenshot of the exact error.
- For billing through Apple or Google, contact that store for refunds.
FAQ
Why does Grok keep saying “Something went wrong”?
Usually a temporary server error, a stale login or a cache problem. Refresh, start a new chat, sign out and in, and check status.x.ai.
Is Grok down for everyone or just me?
Check status.x.ai and search “Grok down” on X. If both look normal, try another network or device to find the cause on your side.
Why is Grok not responding on X?
Tagged replies can lag under load, your plan may not include that feature, or a VPN may block it. Use the Grok tab directly.
Why does the Grok app keep logging me out?
A corrupted session or blocked cookies. Update the app, clear cache, sign in again and avoid switching between X and email logins.
Does a VPN break Grok?
It can. Some VPN exit locations are blocked or flagged. Turn the VPN off and try again.
What does API error 429 mean on xAI?
You exceeded your rate limit or ran out of credit. Slow down, add exponential backoff, and check your billing balance.
How long do Grok outages last?
Most incidents on the status page are resolved within one to two hours, like the 75-minute Grok Bot incident on November 5, 2026.




