Opus 5.5 errors in Grok Bot on Oct 8

Update, Oct 8: A second Opus 5.5 incident listed Grok Bot from 3:52 PM to 4:51 PM ET, with "intermittent errors or failed requests."

Cursor's status page reported rate-limit errors on Claude Opus 5.5 starting at 9:54 AM ET today. Grok Bot was listed with Automations, Review Agents, the CLI, Cloud Agents, and the IDE. A fix was in by 10:08 AM ET, and the incident was resolved at 11:31 AM ET.

Why it matters#

Grok Bot now sends some work to Opus 5.5, so problems at that model can show up as failed Bot replies. If your Bot stalled today, it may not have been your computer.

How to use it#

Cursor's FAQ has the steps for a service problem.

1. Check status.cursor.com and look at the Grok Bot row. The app doesn't show service status. You can subscribe to updates there.
2. Wait for the incident to be resolved.
3. Don't Reset the computer or reinstall the app. The FAQ says neither fixes a service problem.
4. If there's no incident and you see Bot failed to respond or Model provider is overloaded, wait a moment and send the message again.

Good to know#

• Grok Bot doesn't show which model handled a request, so you can't confirm a failure came from Opus 5.5.
• Cursor didn't say how many requests failed or which plans were affected.