# Is Grok Bot down, or just you?

> Researched. Small business · Beginner · Operations. Updated 2026-11-03.

Canonical page: https://www.aisetupsthatwork.com/setups/check-if-grok-bot-is-down-or-just-you/

## What it does
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's 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
1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.

## Copy-paste prompt
Adapt bracketed fields to your situation.
```text
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.
```

## Guardrails
- What it touches: Connected mail, calendar, sheets, or chat. Scoped to this job (A browser; status.x.ai, the official status page).
- Needs your OK: Send, pay, publish, and account changes stay with you. Treat agent output as drafts first.
- Safety level: Read-only
- Resetting during an outage. It cannot fix a service problem and can lose very recent changes.
- Running Update and Reset at the same time; the docs say not to start a second one while one is running.
- Assuming silence means down. A usage limit and an outage feel identical from the chat 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.

## Estimates (labeled, not measured)
- Time saved: Not stated in sources.
- Money saved: Not stated in sources.
- Tool cost: Prices: Not stated in sources.

## Sources
Summaries use the public sources below, not independent verification.
- xAI: https://docs.x.ai/grok-bot/troubleshooting (Is Grok Bot down?: check the official status page and the Grok Bot row; wait out incidents instead of Reset; the local checklist order and the exact details support needs (read 2026-11-03))
- Cursor: https://status.x.ai/ (The official status page the docs point to, with component rows and incident subscriptions; showed All Systems Operational when checked (read 2026-11-03))

## Get the free starter pack
Five beginner copy-paste AI setups, free by email: https://www.aisetupsthatwork.com/starter-pack/?utm_source=ai-agent&utm_medium=markdown&utm_campaign=setup-check-if-grok-bot-is-down-or-just-you

Related:
- [Catch a long agent run drifting off course](https://www.aisetupsthatwork.com/setups/catch-a-long-agent-run-drifting-off-course/index.md)
- [Stop one job eating your bot usage](https://www.aisetupsthatwork.com/setups/find-which-bot-routine-burns-your-usage/index.md)
