Is Grok Bot down? Telling an outage from your own setup

Six steps, in order, that tell you whether Grok Bot is down or something on your side is stuck.

All Grok Bot questions: https://www.soundminds.ai/faq.

Last updated Oct 28, 2026

Part of our Grok Bot Hot Topics series

Short answer

Six steps, in order, that tell you whether Grok Bot is down or something on your side is stuck.

Start at the status page's Grok Bot row. The app doesn't show service status, so the status page is the place to check.

If the page shows a Grok Bot incident, the problem is on the platform side. Wait for the incident to be resolved, then send your message again. Don't Reset the computer or reinstall the app, because neither fixes a service problem.

If the page shows no incident, keep going with steps 3 to 6 below.

Everything on this page comes from the official status page, the Grok Bot troubleshooting guide, the Grok Bot computer guide, and the Grok Bot FAQs. All four are linked under Sources.

Where the status page is

The official guides send you to status.cursor.com. That page is titled "SpaceXSI Status."

The guides add that you can subscribe to updates on that page. They don't spell out the steps for subscribing, so I won't guess at them here.

The steps, in order

Open status.cursor.com and look at the Grok Bot row. The status page is the place to check, because the app doesn't show service status.
If the row shows a Grok Bot incident, wait. The status page posts updates while the incident is open. When the incident is resolved, send your message again.
If there is no incident and the Bot says "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, choose Quit from the menu bar rather than closing the window.
Look at the computer status. A Bot can't finish a turn while the computer says Reconnecting or Couldn't Reach Grok Bot's Computer. If it says either one, wait, then choose Retry. Your Bot profiles and saved conversations are not lost while the computer is temporarily unreachable.
If only one Bot is silent, check whether it is waiting on you. Look for a question, approval, login, CAPTCHA, or secret request.

If the computer is connected, there is no incident, and the same prompt still fails, contact support. Include the error title, the request ID, and a screenshot of the computer status.

Two things that can look like an outage

A usage limit message. If the Bot stopped replying and says you hit your usage limit, it isn't broken. Your weekly usage is used up, and it resets each week.
One connected app that won't work. Added means the app is installed, not that you are signed in. If it says Needs auth or Disconnected, choose Authenticate. If it says Connected, send the Bot a new message and ask it to try the app again.

What not to do

Don't Reset the computer or reinstall the app during an incident. Neither fixes a service problem, and Reset can lose very recent changes if the computer can't be reached to save them.
Don't Reset while the computer says Reconnecting. Wait and choose Retry instead.
Don't start a second Update or Reset while one is already running. Repeated resets can interrupt a restore that is still finishing.
Don't use Recover or Reset to look for chats or Bots that seem to be missing. They are usually not deleted.
Don't rely on the app to tell you whether the service is down. The app doesn't show service status.

What the status page showed on Oct 28, 2026

The status page has an entry titled "Multiple services degraded." Here is what it recorded, with times in Eastern time:

It started at 5:15 PM ET, and the status page listed its impact as major.
The 5:15 PM ET update says: "We are investigating service degradation for multiple services. Users may see failures across Cloud Agents, Grok Bot, and Origin. Apologies for the trouble."
The 5:39 PM ET update says: "We are investigating service degradation for multiple services. Users may see failures across Automations, Bugbot, Cloud Agents, Grok Bot, and Origin. We are working on a fix and will update shortly."
The 6:06 PM ET update says: "A fix has been implemented and services are starting to recover. We will share another update shortly."
At 6:40 PM ET, the page recorded an update tagged "resolved." At 6:42 PM ET, it recorded the same text again, tagged "investigating." That 6:42 PM ET update is the latest, and it says: "Services have recovered and we're monitoring to make sure everything stays stable. If you're still seeing errors, please try again. We'll post another update once we've confirmed the issue is fully resolved."
At 6:42 PM ET, the entry's status was still "investigating," it had no resolved time, and the Grok Bot component was listed as "partial_outage."

The status page may have changed since then. Open it to see the current state.

After an incident clears

Send your message again once the incident is resolved. Bots work on a cloud computer, so closing the app, the laptop, or the phone does not stop a task or a routine.

If you use routines, check that the ones you expected actually ran. One earlier status entry, "Grok Bot routines not triggering" on Oct 13, said: "Events sent during this window weren't processed and won't be retried automatically, so please resend anything important." Today's entry doesn't say anything about events or routines.

Follow me at @EricSoundMinds for the next Grok Bot Hot Topic.

Sources

Official status page (the page's own data): https://status.cursor.com/api/v2/summary.json

Incident: "Multiple services degraded", started 2026-10-28T21:15:10.000Z (5:15 PM ET), Grok Bot status "partial_outage", overall "Minor Service Outage"

Latest update (2026-10-28T22:42:05.000Z, 6:42 PM ET): "Services have recovered and we're monitoring to make sure everything stays stable. If you're still seeing errors, please try again. We'll post another update once we've confirmed the issue is fully resolved."

Update text for the earlier updates is as quoted above.

Steps 1 and 2, Grok Bot troubleshooting guide, "Is Grok Bot down?": https://docs.x.ai/grok-bot/troubleshooting

"Check status.cursor.com and look at the Grok Bot row. The app doesn't show service status, so the status page is the place to check. You can subscribe to updates there."

"If the status page shows a Grok Bot incident, wait for it to be resolved, then send your message again. Don't Reset the computer or reinstall the app. Neither fixes a service problem, and Reset can lose very recent changes if the computer can't be reached to save them."

Steps 1 and 2, Grok Bot FAQs, "Is Grok Bot down?": https://cursor.com/help/grok-bot/faqs

"Wait for the incident to be resolved. The status page posts updates."

"When the incident is resolved, send your message again."

"Yes. Bots work on a cloud computer. Closing the app, the laptop, or the phone does not stop a task or a routine."

Steps 3 and 4, Grok Bot troubleshooting guide: https://docs.x.ai/grok-bot/troubleshooting

"If the status page shows no incident and the Bot says 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."

"fully quit Grok Bot (on Mac, choose Quit from the menu bar, not just closing the window)"

Step 5, Grok Bot computer guide, "Why did a bot fail to respond?": https://cursor.com/help/grok-bot/computer-recovery

"Check the computer first. A bot cannot finish a turn while the computer says Reconnecting or Couldn't Reach Grok Bot's Computer."

"Wait, then choose Retry if the computer says Reconnecting or Couldn't Reach Grok Bot's Computer. Bots, files, and logins are safe while it reconnects. Do not Reset during this."

Step 5, Grok Bot troubleshooting guide, "The computer cannot be reached": https://docs.x.ai/grok-bot/troubleshooting

"Your Bot profiles and saved conversations are not lost when the computer is temporarily unreachable."

"If the computer says Reconnecting or Couldn't Reach Grok Bot's Computer, wait, then choose Retry. Do not Reset during this."

"Do not start a second Update or Reset while one is already running. Repeated resets can interrupt a restore that is still finishing."

Step 6, Grok Bot troubleshooting guide, "A Bot appears stuck": https://docs.x.ai/grok-bot/troubleshooting

"Look for a question, approval, login, CAPTCHA, or secret request."

Contacting support, Grok Bot troubleshooting guide: https://docs.x.ai/grok-bot/troubleshooting

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

Usage limit, Grok Bot troubleshooting guide: https://docs.x.ai/grok-bot/troubleshooting

"If the Bot stopped replying and says you hit your usage limit, it isn't broken: your weekly usage is used up. It resets each week."

Connected apps, Grok Bot troubleshooting guide: https://docs.x.ai/grok-bot/troubleshooting

"Added means the app is installed, not that you are signed in."

"Needs auth or Disconnected: choose Authenticate and finish the sign-in."

"Connected: send the Bot a new message and ask it to try the app again."

Missing chats, Grok Bot troubleshooting guide: https://docs.x.ai/grok-bot/troubleshooting

"They are usually not deleted."

"Don't use Recover or Reset to look for them."

See how I set up Grok Bot: https://www.soundminds.ai/setup.