Is Grok Bot down, or is it just you?

When a Bot stops answering, the first question is whether anything you do will help. If Grok Bot itself is having an incident, the answer is no, and some “fixes” make things worse.

Where to check

Grok Bot runs on Cursor's infrastructure, which is why its official status lives on Cursor's status page (the address now redirects to status.x.ai). That page also lists other products, so look for the Grok Bot row specifically.

Our live status page reads that same official feed, then adds three things it doesn't show: whether real share links from our directory load, whether the Marketplace loads, and how many people reported problems in the last 24 hours.

If there is an incident

Wait for it to be resolved, then send your message again. Two things not to do, straight from the docs:

If there's no incident: read the message

The text in the app tells you which problem you have:

• “Bot failed to respond” or “Model provider is overloaded”: wait a moment and send the message again. If the Bot still doesn't reply, fully quit and reopen Grok Bot (on a Mac, Quit from the menu bar, not just closing the window).
• “Reconnecting” or “Couldn't Reach Grok Bot's Computer”: the Bot can't finish a turn until its computer is back. Wait, then choose Retry. Your Bots, files and logins are safe while it reconnects. The escalation order is in our bot not responding fix.
• A message that you hit your usage limit: nothing is broken. Your weekly usage is used up and resets each week. See the usage-limit fix.
• No error, just silence: open the computer view. The Bot may be waiting on a question, an approval card, a login, a CAPTCHA or a secret request.

If the computer is connected and the same prompt still fails, xAI asks you to contact support with the error title, the request ID and a screenshot of the computer status.

What “down” looked like recently

The official feed is a good reminder that incidents are usually partial and short. In the second half of October 2026 it listed, among others, “Delayed responses in Grok Bot” on October 27 (resolved in about ten minutes), an outage where Grok models were unavailable on October 23–24, and an “Auto Review Degradation” on October 29–30. Our status page keeps the recent ones with links to the official updates.

How our status page decides

• Grok Bot service follows the official “Grok Bot” row. An open incident on that row counts as degraded even if the row still says operational.
• Share links loads a few real share pages from our directory; a live one returns its page with an “Add to Grok Bot” button.
• Marketplace loads x.ai/bot/marketplace and looks for bot listings.
• User reports: when reports in the last hour exceed three times the hourly median of the past week (and at least five people reported), the banner turns amber even if every check passes.

If our own checker fails, the page shows the last known state with its timestamp, never a guess. Want an email next time? Subscribe to alerts on the status page.