Is Grok Bot down, or is it just your account?

Check status.x.ai first: since October 26, 2026 it hosts Cursor's status page and lists Grok Bot as its own component. If Grok Bot shows an incident, wait and change nothing. If it is green and only your Bots are stuck, the problem is almost certainly your account's shared computer or a Bot waiting on you.

This page is a dated copy, not a live feed. The incident details below were last checked on 2026-10-29. For what is happening right now, open status.x.ai first.

The short answer#

Grok Bot signs in with your Cursor account, and the docs say Bots run on computers in Cursor's cloud. So two components matter: Grok Bot for the Bots and their computer, and cursor.com for sign-in. Cursor's October 19 notice said status.cursor.com would stop sending notifications from October 26; by October 27 every old status.cursor.com link redirected to status.x.ai.

Why a green page can still mean an outage#

Declared incidents often trail user reports. On September 16 the first post in the main unresponsive-Bots forum thread landed at 11:06 UTC, a Cursor staff member replied at 11:23 that they were investigating, and the Grok Bot incident opened on the status page at 14:27 UTC.

Some problems never get an entry. Routines were held back, delayed or marked Failed from about 10 AM ET on October 8 into October 9 with no status entry. Since October 1 some Grok Bot computers can only make outbound HTTPS connections, so mail, database, SSH and FTP connections time out; staff called it unintended, said resetting does not help, and had posted no fix by October 14.

The not-responding guide's count is useful context: Cursor's status page recorded 21 incidents involving Grok Bot on 14 different days between September 3 and October 9.

Outage or your account: five checks#

Run these in order. Stop as soon as one gives you an answer.

1. Read the Grok Bot and cursor.com components#

An open incident on either means wait. Note the time and your app version.

2. Compare with the forum#

Open the grok-bot tag. If several people report your symptom within the same hour, treat it as an outage even if the page is green.

3. Count how many Bots are affected#

Every Bot on an account shares one computer, so a stuck computer stops them all at once. All Bots silent on a quiet day points to your computer. One Bot silent while others reply points to that Bot.

4. Open the computer view#

A silent Bot may be waiting on a question, approval, login, CAPTCHA or secret request. Answer it, or send a short redirect or "Stop now".

5. Check the app version and usage#

Grok Bot 0.71.2 (October 14) replaced misleading errors: an idle computer now shows Your computer is asleep instead of Couldn't refresh or a connection error. Update before calling anything an outage, and check Usage & Billing in case your weekly allowance ran out.

Symptom → Likely cause → Fix

• Several Bots stop and status shows a Grok Bot incident → service outage → wait; do not Reset.
• Every Bot stops, status green, forum quiet → your shared computer is stuck → Retry, restart the app, Recover computer, then Settings → Computer → Update Bot's Computer; Reset only last. See not responding.
• "Your computer is asleep" → idle computer, not an outage → on 0.71.2 or later, click the Computer is asleep preview to wake it in place. Switching chats does not wake it.
• "Blocked by a safety check" with "Try a different message" → a safety check blocked that Bot's reply → rephrase or use another Bot.
• One Bot silent, others fine → it is waiting on you → open the computer view and answer.
• Bots stop after a heavy week or show a usage message → weekly usage gone or on-demand limit reached → see usage limits.
• Sign-in never completes → cursor.com incident, an SSO step or Legacy Privacy Mode → check the cursor.com component, then sign-in errors.
• A scheduled routine did not run → routine-trigger incident or misconfigured routine → compare with the history, then routines not running.
• Bots missing after switching to The X Subscription → account split during the switch (Cursor staff, October 21), not an outage → do not reset, delete or buy a second plan.
• Grok on grok.com or X failing too → wider xAI problem → check status.x.ai.

Grok Bot incidents, October 2026 (UTC)#

Times below are exactly as the status history recorded them, newest first. "Major" or "minor" is Cursor's own impact label where we have it.

Two October events are worth knowing even though they were messy on the status page. On October 3 a staff member said the fix landed at about 3:10 AM ET, messages sent during the outage were not retried, and routines due between about 2:00 and 3:10 AM ET did not run. On October 13, webhook callers in the 17:52 to 20:29 window may have seen HTTP 400 "Automation run rate limit exceeded"; Cursor said user usage did not cause it and those events will not be retried.

Grok Bot incidents, September 2026 (UTC)#

The history also shows Grok Bot incidents on August 18, when connectors hung, and August 27.

During and after an outage#

While it is open#

• Leave running work alone. The FAQ says closing the app, laptop or phone does not stop a background turn or routine.
• Do not Reset. It restores the last saved snapshot and can lose recent or unsynced work. During the September 7 incident Cursor said Recover or Reset might fail anyway.
• Subscribe to updates on status.x.ai so you see when it is resolved.

Once it is resolved#

1. Open each Bot, read its last message and resend anything that failed.
2. List routines that were due in the incident window and run missed ones by hand. Missed runs on October 3, 8 and 13 were not replayed.
3. Resend any webhook, Slack, git, email or Linear events from the October 13 trigger window.
4. If Bots still do not reply, treat it as your computer and follow the not-responding recovery order.

Support report template#

Copy this before you contact support or post in the forum. Leave out passwords, one-time codes, private keys and secret values.

Grok Bot version:

Operating system:

Exact error text:

Bot or routine name:

First seen (time + time zone):

Request or conversation ID (if shown):

Status page at the time: [incident title / green]

Tried so far: Retry [y/n], app restart [y/n], Update Bot's Computer [y/n]

Result of each:

Our take#

Bookmark status.x.ai and the forum tag together, because neither alone tells the full story: the page lags, and the forum is noisy. If the page shows an incident, your only jobs are to wait and keep a list of what to resend. If it is green and your whole account is down, it is your computer, and the recovery order in our troubleshooting hub applies, with Reset strictly last.

Frequently asked questions#

Where is the official Grok Bot status page?#

At status.x.ai. Cursor said on October 19 that its status updates would move there from October 26, 2026, and by October 27 every status.cursor.com address redirected to it. The page lists Grok Bot as its own component next to cursor.com, Cloud Agents, Automations, the IDE and the CLI, and its history holds Cursor's incidents back to September.

Why are my Bots not responding when status.x.ai is green?#

The status page only shows incidents Cursor has declared, not your account. Every Bot on an account shares one cloud computer, so if that computer is stuck, all your Bots stop while everyone else is fine. Declared incidents can also lag or never appear: the October 8 routine failures had no status entry. Check the forum's grok-bot tag, then follow the recovery order.

Should I reset my Grok Bot computer after an outage?#

Usually not. After the October 3, 6 and 8 incidents, Cursor staff said the fix was on their side, no reset or reinstall was needed, and any message showing Bot failed to respond should just be sent again. Reset restores the last saved snapshot and can lose recent or unsynced work, so keep it as the very last step.

Will an outage delete my Bots or files?#

Not according to what Cursor has published. The September 7 status notice said data was not affected, and the troubleshooting page says Bot profiles and saved conversations are not necessarily lost when the computer is temporarily unreachable. The real risk is a Reset you trigger yourself during the incident, which can discard recent work.

How do I get notified when Grok Bot has an outage?#

Subscribe on status.x.ai. Email subscriptions moved over automatically, with mail from status@email.api.x.ai, and the RSS feed is status.x.ai/feed.xml, which Slack users can add with /feed subscribe. SMS, Microsoft Teams and webhook notifications stopped on October 26, so re-subscribe by email or RSS. Grok Bot items in the feed are prefixed [Grok Bot].