If Grok just stopped responding mid-conversation, won’t load, keeps throwing errors, or the app is frozen — you’re not imagining it. Grok does go down. Here’s how to confirm it in under 30 seconds and exactly what to do about it, depending on your situation.
Is Grok Down Right Now?
How to check: Visit status.x.ai — the only official Grok status page. No login needed.
Fastest fix: Hard-refresh (Ctrl+Shift+R / Cmd+Shift+R) or switch networks before assuming it’s a real outage.
App issues: Force-close the Grok or X app, clear app cache, then reopen. Works for 80% of “frozen” reports.
API down? Check status.x.ai for API-specific incidents — tracked separately from the web interface.
Typical outage length: Most disruptions resolve within 15–45 minutes. Major incidents run 2–4 hours.
Best workaround: Use Grok inside X.com if standalone app is down — they run on partially separate infrastructure.
🔎 How to Check If Grok Is Actually Down (Not Just You)
The single biggest mistake people make: spending 20 minutes refreshing when Grok’s servers are fine — or doing local fixes when Grok really is down globally. Know which one it is first.
User-reported outages. Great for spotting regional issues before official status updates.
Pings grok.com from multiple locations — useful to isolate if it’s your region or global.
Quick test: open grok.com in a private/incognito window. If it loads there but not your normal browser, the problem is on your end — a bad cookie or extension conflict, not a Grok outage.
What the Status Page Colors Mean
| Status | What It Means | What To Do |
|---|---|---|
| 🟢 Operational | All systems working — problem is on your end | Troubleshoot locally (see section below) |
| 🟡 Degraded | Service is slow or partially broken | Wait 5–10 min, retry, or use X.com’s Grok |
| 🔴 Outage | Major disruption — widespread impact | Nothing to fix on your end; use an alternative |
| 🔵 Maintenance | Planned downtime (usually announced ahead) | Check when it’s expected to finish |
🛠️ Grok Not Working? Fix It Step by Step
This is the exact order to follow. Don’t skip steps — each rules out a different cause. Most issues resolve by step 3.
Check status.x.ai first. If it shows red, stop here. There’s nothing you can do locally. Skip to the workarounds section.
Hard refresh the page. Chrome/Edge/Firefox: Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac). Bypasses cache and forces a fresh load.
Try incognito/private mode. Open a private window and go to grok.com. If it loads there, a browser extension or corrupted cookie is the problem — not Grok’s servers.
Clear Grok cookies specifically. In Chrome: Settings → Privacy → Cookies → See all site data → search “grok” → delete. Don’t nuke all cookies — unnecessary.
Switch your network. Toggle off Wi-Fi and use mobile data (or vice versa). Some ISPs and corporate firewalls block xAI services. Confirms instantly if it’s a network-level block.
Disable your VPN. VPNs cause a surprising number of Grok issues — especially if routed through a region where xAI has limited infrastructure. Turn it off temporarily to test.
Try a different browser. Chrome, Firefox, Edge, Safari each handle authentication slightly differently. A five-second test tells you a lot.
Log out and log back in. Go to grok.com → profile → sign out → sign back in. Stale auth tokens cause “endless loading” that looks like server problems but isn’t.
What most guides miss: If you’re using Grok through X Premium and your subscription recently lapsed or renewed, you can get a broken experience that looks like an outage — Grok loads but won’t process requests. Check your X Premium status at x.com/settings/subscription before anything else.
📱 Grok App Not Working — Mobile-Specific Fixes
The Grok app and X app (iOS and Android) have slightly different failure modes than the web version. These fixes are specific to mobile.
Swipe up to fully close the app. Wait 5 seconds, reopen. Solves frozen UI and stuck chat states.
Android: Settings → Apps → Grok → Storage → Clear Cache. iOS: Offload app via Settings → General → iPhone Storage.
Toggle airplane mode on/off, or switch Wi-Fi ↔ mobile data. Works surprisingly often for timeout errors.
Go to App Store or Play Store. Outdated versions cause auth failures after xAI backend updates.
Last resort but effective. Uninstall, reinstall fresh. Your chats are server-side — you won’t lose them.
Open Safari or Chrome → grok.com. Mobile web is separate from the app and often works when the app doesn’t.
❌ Common Grok Error Messages — What They Actually Mean
Generic error messages are infuriating. Here’s what each one actually means and the fastest fix.
| Error / Symptom | Real Cause | Fastest Fix | Severity |
|---|---|---|---|
| “Something went wrong” | Server error or auth token expired | Log out, log back in | Medium |
| Blank/white screen | JavaScript failed to load — CDN or extension block | Hard refresh + disable extensions | Medium |
| Infinite loading spinner | Stale auth token or slow server response | Wait 30s, then hard refresh | Low |
| “Rate limit exceeded” | Hit your plan’s usage cap | Wait for daily reset or check your limits | Info |
| “Network Error” / 504 | Request timeout — server took too long | Retry the message, or switch networks | Medium |
| 403 Forbidden | Access denied — subscription issue or IP block | Check X Premium sub, try different IP | High |
| 500 Internal Server Error | xAI server-side failure | Check status.x.ai, wait for resolution | High |
| Grok replies but no images | Aurora image model separately down | See Grok image generation guide | Medium |
| Login loop | Corrupted session cookie | Clear grok.com cookies specifically, re-login | Medium |
📡 Grok API Down? Developer-Specific Checks
If you’re calling the Grok API (api.x.ai) and getting failures, the web interface being fine doesn’t mean your API calls will work. They can fail independently.
Check the API-specific status. Go to status.x.ai and look at the “API” row specifically — not just the general status indicator.
Verify your API key is valid. Run: curl https://api.x.ai/v1/models -H “Authorization: Bearer YOUR_KEY”. A 401 response means the key is invalid or expired — not an outage.
Check your rate limits. A 429 error means you’ve hit per-minute or per-day limits, not that the API is down. Extremely common — constantly misdiagnosed as an outage.
Confirm your endpoint URLs. xAI updated several endpoints in 2025. Make sure you’re hitting https://api.x.ai/v1/chat/completions — not an old URL.
Test with a minimal payload. Strip your request to the minimum — model, one user message, no system prompt, no tools. If that works, the issue is in your request structure.
Common developer mistake: Confusing a 429 (rate limit) with a 503 (server down). A 429 means slow down. A 503 means something’s actually wrong with xAI’s servers. Read the response body — not just the status code.
🕐 How Long Does Grok Stay Down During Outages?
Based on observed patterns from Grok’s launch through mid-2026, here’s what to realistically expect:
Brief slowdowns, occasional timeout errors. Most common type. Usually resolves before hitting the status page. Just wait and retry.
Slow responses, partial failures, some features down while chat works. Common during peak traffic hours. Status page usually updates within 10 minutes.
Service completely inaccessible. Rare but does happen, especially after major feature launches. xAI typically posts updates every 30–60 minutes.
Usually announced in advance via @xAI on X. The most predictable — check scheduled maintenance on status.x.ai to see upcoming windows.
Peak hours to avoid: Grok tends to slow down most during US business hours on weekdays (9am–6pm ET) and after major news events. Early mornings before 8am ET tend to be the most stable for important work.
🔄 Best Workarounds While Grok Is Down
Waiting isn’t always an option. Here’s what actually works as a temporary replacement depending on what you were using Grok for.
| If you were using Grok for… | Best Temporary Alternative | How to access |
|---|---|---|
| General chat / Q&A | Claude.ai or ChatGPT | claude.ai / chatgpt.com |
| Real-time web search | Perplexity AI | perplexity.ai |
| Image generation | DALL-E via ChatGPT or Ideogram | chatgpt.com |
| Coding help | Claude or GitHub Copilot | claude.ai |
| Grok inside X | X’s built-in AI features | Still available on x.com even if grok.com is down |
- Accessing old Grok chat history (sometimes)
- Using Grok inside X.com (different infra)
- API calls may still work if web is down
- Checking status page for ETA
- Refreshing repeatedly (won’t fix server outages)
- Clearing browser data (server-side issue)
- Reinstalling the app while servers are down
- Contacting Grok support for outage ETAs
🔔 How to Get Alerted When Grok Is Back Online
Don’t keep manually checking. Set up one of these and forget about it.
- ✓Subscribe on status.x.ai — Click “Subscribe to Updates.” You’ll get email notifications the moment an incident is posted or resolved.
- ✓Follow @xAI on X — xAI posts outage updates and resolution notices here — sometimes faster than the status page.
- ✓Set a Downdetector alert — Free notification feature. Get pinged when user reports spike or drop off.
- ✓Use UptimeRobot (free) — Create a free monitor for grok.com. It’ll ping you via email or SMS when the site comes back online.
🚀 Fastest way to know Grok is back: Subscribe to status alerts now so you stop wasting time checking manually.
Subscribe to Grok Status →🚫 Things to Avoid Doing When Grok Is Down
These are the time-wasters that don’t help and occasionally make things worse.
Don’t reset your password during an outage. If you can’t log in because of a server issue and you reset your password, you’ll add a confusing variable when things come back up — and sometimes trigger additional verification steps unnecessarily.
- Don’t spam refresh for more than 2–3 minutes — if it’s not loading after a hard refresh, refreshing more won’t help.
- Don’t reinstall the app during an active outage — you’ll lose local cache for nothing; the problem will still be there.
- Don’t assume your account is banned — outages look identical to account-level blocks. Check status first.
- Don’t contact X support for Grok technical outages — X support handles X issues, not xAI infrastructure problems.
- Don’t post “is Grok down?” without checking first — status.x.ai is 10 seconds away and far more reliable than crowd-sourcing answers.
📋 Why Grok Goes Down — The Actual Technical Reasons
Knowing why it fails helps you predict and respond faster. Grok’s infrastructure runs on xAI’s own Colossus GPU cluster — one of the largest in the world. But that doesn’t make it immune to these real failure modes:
Major news events or product launches drive sudden surges that overwhelm capacity. The most common cause of brief slowdowns.
When xAI deploys a new Grok version, backend migration causes partial disruptions. Usually brief but can cause odd behavior.
GPU or networking hardware failures at the data center level. Rare but results in the longest outages — typically 1–4 hours.
High-profile AI services are frequent targets. Protective measures can temporarily block legitimate users.
Scheduled updates, database migrations, infrastructure upgrades. Announced in advance on status.x.ai.
Content delivery network problems can make Grok appear down in specific regions even when core servers are fine globally.
🛡️ How to Make Grok More Reliable for Your Workflow
If you rely on Grok regularly — for work, API integration, or daily use — build resilience into your setup so outages hurt less.
Always have a second AI tool ready. Keep Claude or ChatGPT bookmarked and logged in. Switching takes 5 seconds — not 5 minutes of troubleshooting.
For API users: implement exponential backoff. Don’t hammer a failing API. Start with a 1-second retry, then 2, 4, 8. Handles transient errors automatically and avoids compounding rate limit issues.
Save important conversations locally. Grok doesn’t currently offer bulk chat export. Copy-paste important outputs. If Grok is inaccessible, you can’t access your history.
Use Grok inside X as a backup. Grok embedded in X.com and standalone grok.com operate on partially different infrastructure. When one has issues, the other sometimes doesn’t.
Monitor your API usage proactively. Getting cut off during critical work because you hit a rate limit is avoidable. Know your Grok usage limits and set up usage alerts where available.
📞 How to Report a Grok Outage or Get Support
Most outages self-resolve, but if you’re experiencing a persistent issue unrelated to a global outage, here are your actual options.
| Channel | Best for | Response time |
|---|---|---|
| @xAI on X | Reporting bugs, getting outage updates | No direct reply usually, but monitored |
| X Help Center | Billing, account, subscription issues | 24–72 hours |
| status.x.ai | Checking incident status and updates | Real-time |
| X Community (Grok topics) | User troubleshooting, workarounds | Minutes (community-driven) |
No dedicated Grok live chat support exists as of mid-2026. For billing issues tied to an outage, use X Help Center with a clear description of the dates/times affected and screenshots from status.x.ai during that period.
❓ Frequently Asked Questions
Check status.x.ai right now — this article can’t provide a real-time status. If the page shows green across the board and Grok still isn’t working, the issue is local to your device, network, or account.
This usually means a server-side issue (check status.x.ai) or an expired auth token. Fastest fix: log out completely, wait 30 seconds, log back in. If it persists, clear your grok.com cookies specifically and try again.
Check two things: (1) status.x.ai for official status, and (2) open grok.com in an incognito window. If incognito works, the problem is on your end. If nothing works and status.x.ai shows an incident, it’s affecting everyone.
xAI doesn’t have an automatic SLA-based refund policy for outages as of mid-2026. For extended outages that impact your paid use, contact X Help Center and document the outage times using screenshots from status.x.ai.
Grok embedded in X.com and standalone grok.com are served through different front-end systems, even though they share the same underlying AI model. When grok.com has a CDN or front-end issue, the X-integrated version can still function normally, and vice versa.
Based on observed patterns, Grok experiences minor slowdowns a few times per month and significant outages (30+ minutes) roughly once every 4–8 weeks. Planned maintenance happens less frequently, usually monthly.
Yes — Grok’s image generation (powered by Aurora) can fail independently of the main chat. Check status.x.ai for image-service-specific status. Also see our guide on Grok image generation for usage limits that might explain why generation stops.
Grok has had notable outages tied to major product launches (Grok 2, Grok 3) when traffic spiked dramatically. The status page archives past incidents — check the history at status.x.ai.
“Degraded performance” happens when servers are overloaded — not crashed. During these periods, the model still responds but takes 3–10x longer. The status page labels this “degraded” rather than “outage.” Wait 15–20 minutes or use a different AI tool in the meantime.
⚡ Quick recap: Check status.x.ai → hard refresh → incognito test → clear grok.com cookies → switch network. In that order. Works 95% of the time.
Expanded free tier messages help but voice has separate caps—check Grok Voice Mode setup and limits.
