Is Grok Bot down right now?

Check Cursor's status page at status.cursor.com, which lists Grok Bot as its own component; xAI's status page at status.x.ai covers the Grok apps and API but has no Grok Bot entry. If the Grok Bot component shows an incident, wait rather than reset anything. If it shows operational and only your account is affected, the likely cause is your account's shared computer or a Bot waiting on you, and the official recovery steps apply.

When we checked on September 23, 2026, every component on Cursor's status page, including Grok Bot, was operational. A green page only means no incident has been declared. It says nothing about your account.

Grok Bot signs in with your Cursor account, and the docs say the computers Bots work on run in Cursor's cloud. That is why the two components worth watching are Grok Bot, for the Bots and their computer, and cursor.com, for sign-in.

Documentation: Cursor status page (Grok Bot component) ↗ SpaceXAI status (Grok apps and API; no Grok Bot entry) ↗ Grok Bot overview ↗ Official troubleshooting ↗

Where to check, in order

Declared incidents and user reports do not always arrive together. On September 16 the first post in the main unresponsive-Bots forum thread went up at 11:06 UTC and a Cursor staff member replied at 11:23 that they were investigating; the Grok Bot incident on the status page opened at 14:27 UTC. On a bad day, check the forum as well as the status page.

Documentation: Cursor status page (Grok Bot component) ↗ Cursor status: incident history ↗ SpaceXAI status (Grok apps and API; no Grok Bot entry) ↗ Cursor forum: grok-bot tag ↗ Forum: some Bots became unresponsive (September 16, staff replies) ↗ Cursor status: Grok Bot degradation, September 16 ↗

SourceWhat it coversWhen to use it
Cursor status pageDeclared incidents for Grok Bot, cursor.com sign-in, Cloud Agents, Automations, the IDE and the CLIFirst, every time; subscribe or use the RSS or Atom feed
Cursor status historyPast incidents with start and resolve timesTo match a bad evening against a past incident
SpaceXAI status (status.x.ai)Grok on web, iOS, Android and X, Grok Build, the API, SSO and the docs; no Grok Bot entryWhen Grok itself is also failing
Cursor forum, grok-bot tagUser reports and Cursor staff repliesWhen the status page is green but many people report the same symptom in the same hour

Grok Bot incidents in September 2026

These are the incidents on Cursor's status page in September that listed Grok Bot as affected, plus one cursor.com sign-in incident. Times are UTC, from when Cursor opened each incident to when it marked it resolved. The history also shows Grok Bot incidents on August 18, when connectors hung, and August 27.

In the forum, a Cursor staff member wrote on September 17 that services should be back after about 24 hours of disruption, although two more Grok Bot incidents followed on September 18. Staff closed the main thread on September 21, saying things were stable, and asked people to open a new thread for fresh reports. Our not-responding guide describes what those days looked like from the user side.

Documentation: Cursor status: incident history ↗ Cursor status: degradation across Grok models and Grok Bot, September 3 ↗ Cursor status: routine trigger fires dropped, September 3 to 4 ↗ Cursor status: Grok Bot computers unreachable, September 7 ↗ Cursor status: service degradation including Grok Bot, September 15 ↗ Cursor status: Grok Bot degradation, September 16 ↗ Cursor status: Grok Bot degradation, September 17 ↗ Cursor status: Cloud Agents and Automations degradation, September 17 ↗ Cursor status: Grok Bot degradation, September 18 (morning UTC) ↗ Cursor status: Grok Bot degradation, September 18 (evening UTC) ↗ Cursor status: sign-in and dashboard errors, September 18 ↗ Forum: some Bots became unresponsive (September 16, staff replies) ↗

Date (UTC)What the status page saidDuration
September 3, 13:41 to 17:07Degradation affecting all Grok models, Automations, Cloud Agents, Grok Bot and Review Agents (marked critical)About 3.5 hours
September 3 to 4, 23:42 to 00:42Degraded performance for Grok Bot routine triggers; some trigger fires may be dropped1 hour
September 7, 20:32 to 21:37Some users unable to reach their Grok Bot computer; Recover or Reset may fail; data not affectedAbout 1 hour
September 15, 21:26 to 22:00Degradation across Cursor components, including Grok BotAbout 35 minutes
September 16, 14:27 to 20:57Grok Bot degradation: degraded performance or bots that don't respondAbout 6.5 hours
September 17, 12:30 to 14:34The same Grok Bot degradationAbout 2 hours
September 17, 15:20 to 20:04Cloud Agents and Automations degradation, with Grok Bot listed as affectedAbout 4.75 hours
September 18, 11:37 to 14:33Grok Bot degradation: degraded performance or bots that don't respondAbout 3 hours
September 18, 17:19 to 23:02Grok Bot service degradationAbout 5.75 hours
September 18, 23:02 to 23:13Sign-in and dashboard errors on cursor.com; existing sessions kept working11 minutes

An outage, or just your account?

Every Bot on an account shares one cloud computer, so a problem with that computer looks like an outage: all your Bots stop together. The difference is whether other people are affected at the same time. Use the status page and the forum to answer that before you change anything.

Documentation: Official troubleshooting ↗ Grok Bot FAQ ↗ Cursor status page (Grok Bot component) ↗ SpaceXAI status (Grok apps and API; no Grok Bot entry) ↗

What you seeMost likelyWhat to do
Several Bots stop at once and the status page shows a Grok Bot incidentA service outageWait; do not Reset. Note the time and your app version
Every Bot stops but the status page is green and the forum is quietYour account's shared computer is stuck or unreachableRetry, restart the app, Recover computer, then Update under Grok Bot's Computer; Reset only last
One Bot is silent while others replyThat Bot is waiting on a question, approval, login, CAPTCHA or secret requestOpen the computer view, answer it, or send a short redirect or "Stop now"
Bots stop after a busy week, or show a usage messageWeekly usage is used up or the on-demand spending limit is reachedCheck Usage & Billing; see our weekly usage limit guide
Sign-in never completesA cursor.com sign-in incident, an SSO step, or Legacy Privacy ModeCheck the cursor.com component, then the official sign-in checks
A scheduled routine did not runA routine-trigger incident, or a disabled or misconfigured routineCompare the time with the status history, then run the routine checklist
Grok on grok.com or in X is failing tooA wider xAI problemCheck status.x.ai as well

What to do during an outage

The goal is to avoid making things worse. User-side recovery rarely helps during a declared incident, and the one destructive option, Reset, can discard recent work.

Documentation: Grok Bot FAQ ↗ Official troubleshooting ↗ Cursor status: Grok Bot computers unreachable, September 7 ↗ Cursor status: routine trigger fires dropped, September 3 to 4 ↗ Cursor status RSS feed ↗

  1. Leave running work alone. Bot work runs on the cloud computer, and the FAQ says closing the app, laptop or phone does not stop a background turn or routine.
  2. Do not use Reset. It restores the last saved snapshot and can lose recent or unsynced work, and during the September 7 incident Cursor said Recover or Reset might fail anyway.
  3. Subscribe to the Cursor status page or its RSS feed so you know when the incident is marked resolved.
  4. Once it is resolved, open each Bot, read its last message, and resend anything that did not go through.
  5. Check routines that were due during the incident window; the September 3 to 4 incident dropped some routine trigger fires.
  6. If Bots still do not respond after the incident is resolved, treat it as your computer and follow the recovery order in our not-responding guide.
  • Before contacting support, collect your Grok Bot version and operating system.
  • Copy the exact error message and the Bot or routine name.
  • Note the approximate time and your time zone, and any request or conversation ID shown.
  • Record whether Retry, an app restart, or updating Grok Bot's computer changed anything.
  • Leave out passwords, one-time codes, private keys and secret values.

Quick answers

Is there an official Grok Bot status page?

Yes, on Cursor's status page. status.cursor.com lists Grok Bot as its own component next to cursor.com, Cloud Agents, Automations, the IDE and the CLI. xAI's status page at status.x.ai covers the Grok apps, Grok Build and the API, and had no Grok Bot entry when we checked on September 23, 2026.

Why is the status page green when my Bots are not responding?

Two reasons. The status page reports incidents Cursor has declared, not the state of your account, and every Bot on an account shares one cloud computer, so a stuck computer stops them all at once without affecting anyone else. And declared incidents can lag: on September 16 the first report in the main forum thread came about three hours before the Grok Bot incident was opened. Check the forum's grok-bot tag, then follow the official recovery order.

Will I lose my Bots or files during an outage?

Not from the outage itself, going by 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 risk is Reset: it restores the last saved snapshot and can lose recent or unsynced work, so leave it until last.

How do I get notified when Grok Bot is down?

Subscribe on status.cursor.com, or add its RSS feed (status.cursor.com/history.rss) or Atom feed to a reader. Both carry every declared incident, including ones for other Cursor products, so filter for Grok Bot and cursor.com if you only care about sign-in and Bots.

Sources & next steps

Capabilities are grounded in the documentation below. The workflow design and acceptance checks are editorial suggestions.

Build your own workflow brief ↗