Grok Bot computers are reachable again after today's outage

If your Grok Bot couldn't reach its computer earlier today, try again now. Cursor marked the status incident Resolved at 5:04 PM ET, and the status page shows Grok Bot as Operational again. Fully quit and reopen the app if a Bot is still stuck. Staff now say the freeze that blocked Update was resolved last night; keep Recover and Reset last, as the docs advise.

• Status: Resolved at 5:04 PM ET (21:04 UTC). The incident ran about 5 hours 18 minutes from the Investigating post at 11:46 AM ET.
• Scope during the outage: "some users." Cursor never named how many, which regions, or what the issue was.
• No Monitoring step was posted. Status went Investigating, then Identified at 4:08 PM ET, then Resolved.

Update, Oct 15, 10:30 AM ET#

Staff have now answered the 6:40 AM ET report. Colin said at 9:18 AM ET that it is "a different issue from the others in this thread": "The computer itself is working fine, but for a while now it hasn't been able to save its backup copy." He called it "a known issue we're already tracking" and said: "Please don't use Reset Computer." Details are in our known-issue entry.

Update, Oct 15, 7:00 AM ET#

Cursor staff member Colin said at 5:35 AM ET that "From about 13:00 to 21:00 UTC on October 14, many Bot computers stopped responding." That is about 9 AM to 5 PM ET, more than two and a half hours before the 11:46 AM ET status post.

He also explained the Update error: "While a computer is frozen, Update can't make the backup it needs before moving your computer, so it shows "Your computer's files aren't ready" and leaves everything as it is. That was resolved last night." In other words, Update refused to run rather than risk your files. One user replied at 6:40 AM ET that they still get the same message this morning; staff hadn't answered as of 7:00 AM ET.

In a separate reply at 5:43 AM ET, Colin said one user's computer "ran very low on memory (several Bots had browser windows open at the same time), and the part of it the app talks to stopped responding." That user's Bots could still chat but couldn't use the computer, and the computer came back around 10:25 AM ET. Colin told them "Your Bots and their data are safe, and your computer's backup is complete and up to date." He did not say whether memory was the cause of the wider outage.

What to do now: if a Bot still can't use its computer this morning, quit and reopen Grok Bot first. Staff haven't posted a blanket all-clear for Recover or Reset, so keep those last, as the docs advise, and ask in the forum first if your computer has been frozen since yesterday.

Update, 6:24 PM ET#

At 5:04 PM ET Cursor posted "This incident has been resolved." The status summary now reads All Systems Operational, and the Grok Bot component is Operational. Cursor still has not named a cause.

Staff had told affected users during the outage to avoid Update, Recover, and Reset. As of 6:24 PM ET no staff post has said that advice is lifted. If a Bot still can't reach its computer after you quit and reopen, post in the forum or send in-app feedback, say you want your files kept, and ask before using Update, Recover, or Reset.

Forum threads from this afternoon still show users who were stuck before the Resolved post, including reports after 4:14 PM ET on Android and on Update blocked by "Your computer's files aren't ready." We found no new Cursor staff replies in those threads between the Identified post and this check.

What changed#

Users on X began posting around 11:26 AM ET, 20 minutes before the incident. One wrote at 11:31 AM ET, "Seems like Grok @bot computer is down. Had to manually restart it." Another said at 12:07 PM ET that their Bot "responds to me but never comes back from working."

Update, 4:16 PM ET#

At 4:08 PM ET Cursor moved the incident from Investigating to Identified: "We've identified the issue impacting Grok Bot for some users and are working on a fix." It didn't name the issue or give a time for the fix.

Reports kept coming in the meantime. On the forum, one user wrote at 2:30 PM ET that since about noon ET "none of them can run commands, use the browser or run their routines," and that Update Computer kept returning "Your computer's files aren't ready. Try again in a moment." Another said at 2:40 PM ET that the Update button was greyed out and Update didn't work from the iOS app either. A third said at 3:12 PM ET that even newly created Bots don't answer.

Update, 2:19 PM ET#

Two Cursor staff replies tighten what people were told during the outage. At 1:40 PM ET, deanrie told a user whose computer had been frozen since Oct 12 to "keep avoiding Update, Recover, and Reset. On a frozen computer, those can fail or overwrite data," and pointed them to this status incident. deanrie added that Bots and their saved data "are stored separately from the computer." At 1:16 PM ET, kevinn told an Android user whose Bots had gone silent that the computer "is running but isn’t responding," that it "isn’t caused by anything on your end or by your usage," and "Please don’t use Reset in the meantime, since it can clear files on the computer."

Both staff asked follow-up questions that hint at what they were checking: deanrie asked whether a Bot had started "something heavy on the computer, like a large build, a test suite, or multiple scripts at the same time," and kevinn asked whether the user had tapped Update around Oct 12 or 13. Cursor never named a cause.

Why it matters#

Anything that needs the computer (browsing, files, code, many routines) stalled for some users while chat often looked normal. Cursor's docs say Recover and Reset "both rebuild the computer from your last saved data; if the computer can't be reached to save first, very recent changes don't come back." Staff told people to wait rather than force those paths during the outage.

How to use it#

The docs give this order, least destructive first. Since staff haven't lifted their hold, do steps 1 and 2, then ask in the forum before going further:

1. Press Retry on the error, or reopen the conversation.
2. Fully quit and restart the Grok Bot app and check for an app update.
3. Choose Recover Grok Bot's Computer if the error offers it. It rebuilds from your last saved data, so very recent changes may not come back.
4. Try Settings > Computer > Update Bot's Computer. A computer update keeps files and logins but removes installed apps and packages; a software update keeps apps.
5. Leave Reset Bot's Computer for last. Like Recover, it rebuilds from your last saved data.

If steps 1 and 2 don't help, post in the Cursor forum or send in-app feedback and say you want your files kept. Routines that couldn't run during the window may need a manual rerun; Cursor hasn't said whether they'll retry.

Good to know#

• Conversations are stored outside the computer, so the docs say they "survive even a reset." Colin (Cursor staff) warned earlier today, though, that a Bot whose backup is failing "could come back without its recent messages" after Reset.
• If Update stops because your computer's files aren't ready, that's Update's backup step protecting you. At 12:16 PM ET Colin said "the backups of your Bots are completing normally again" for one account. He didn't link that to this incident.

What to watch#

Whether Cursor posts a cause or postmortem, whether any users remain stuck after Resolved, and whether routines that missed the window need a manual kick. Also watch Update behavior if "files aren't ready" returns for accounts that still have a bad Bot backup.

What changed#

Oct 14, 6:24 PM ET: Cursor marked the incident Resolved at 5:04 PM ET. We updated the title, dek, lead and status bullets, added the 6:24 PM ET update, noted that staff haven't lifted their advice to avoid Update, Recover, and Reset, and refreshed What to watch.

Oct 14, 4:16 PM ET: Cursor moved the status incident to Identified at 4:08 PM ET and said a fix is in progress.