Tell a real Grok Bot outage from a problem on your side using the official status page and a short checklist, before you reset or reinstall anything.
Who it is for
Owners whose bots suddenly stop answering and who need to know in two minutes whether to wait or fix.
Tools
A browser
status.x.ai, the official status page
Your exact error text, if there is one
Steps
Open status.x.ai and look at the Grok Bot row. xAI's docs name the status page because the app itself does not show service status, and you can subscribe to updates there. The page moved from status.cursor.com to status.x.ai on Oct 26, 2026.
If the page shows an incident: wait for it to resolve, then send your message again. Do not Reset the computer or reinstall the app; the docs warn Reset can lose very recent changes.
If the page shows no incident: note the exact error. Bot failed to respond or Model provider is overloaded usually clears: wait a moment, resend, then fully quit and reopen the app.
If the computer says Reconnecting or Couldn't reach Grok Bot's Computer: wait, choose Retry, then quit and reopen, then Update, then Recover. The docs put Reset last in that order for a reason.
Still stuck: contact support with the error title, the request ID, and a screenshot of the computer status, which is exactly what the docs say to include.
Optional: add a morning routine that checks the status page and pings you only when something is down, so you hear about outages before your report fails.
The prompt
Check [STATUS PAGE URL] for Grok Bot right now. Tell me: is there an active incident, which components it affects, and when it started? If there is no incident, say so plainly. Do not troubleshoot my setup yet; I only want to know whether the problem is on the platform side.
Tips
Subscribe to status updates once, on a calm day, so the next outage tells you about itself.
Screenshot the error before you restart anything. Support will ask for it.
A full quit means quit from the menu bar, not closing the window.