Grok Bot is Broke

Support Bug Reports
1

since yesterday afternoon around 3PM Central Grok Bot is says overbooked and then it will say failed to respond.

Reset computer it didnt help. its just stuck. I’ve tried at various times and its always the same.

I have plenty of usage remaining as well.

Screenshot 2026-08-26 at 07.42.22
Screenshot 2026-08-26 at 07.42.22835×325 6.93 KB

2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

6

Hey, thanks for the report. What you’re seeing (“overbooked”, then “Bot failed to respond” in the screenshot) isn’t anything with your account, usage, or your computer. Those are all fine. This is a service-side issue. The model behind Grok Bot is sometimes under very heavy load right now, and requests get rejected in waves, starting around the time you described.

We’re tracking it. The same symptom is showing up in a few threads, for example here Cursor Grok 4.6 We're having trouble connecting to the model and here We're experiencing high demand for Cursor Grok 4.6 right now. Please switch to Auto, another model, or try again in a few moments. Please try again a bit later. During lower-load periods, requests go through normally.

If it still keeps getting stuck on “failed to respond” after that, reply here and I’ll look into your specific case.

7

i did manage to get the computer to reset and it fixed it the 2nd try.