CURSOR

🟠 Cursor's Grok Bot is having an existential crisis—some instances went catatonic and new ones refuse to spawn. Engineers found the culprit and are rolling out a fix while computers contemplate their mortality. (Auto-resolved: no updates in 24h)

⏰ Sep 25, 2026 Fixed (for now) spotted via status_rss

// The official story

Investigating service degradation — Grok Bot

// Status page says

Sep 25 , 05:52 UTC Monitoring - We have identified the cause and are deploying a fix. We are monitoring recovery as the fix rolls out. Some Grok Bot computers may remain temporarily unavailable or unable to be created or reset during this time. Sep 25 , 05:17 UTC Investigating - We are investigating a service degradation affecting Grok Bot. Grok Bot computers may tem

🔗 Official status page (for the PR-approved version)

https://status.cursor.com/incidents/n540z31sbqp6

Cursor's Greatest Hits

🔴 CURSOR 18h ago

🟡 Cursor achieved quantum superposition: simultaneously broken everywhere. IDE, agents, bots, automations—basically the entire stack decided to unionize and call in sick. Engineering team is now speed-running 'have you tried turning it off' on production.

🟢 CURSOR Aug 19, 2026

🟡 Cursor's Fable 5 model went full Rip Van Winkle, leaving engineers scrambling to explain why their fancy AI forgot how to AI. Time to dust off those backup models while the team figures out what went wrong. (Auto-resolved: no updates in 24h)

🟢 CURSOR Aug 13, 2026

🟡 Anthropic's model serving decided to take an unscheduled sabbatical, leaving Cursor's AI agents staring at blank screens. The usual suspects (Claude Mythos 5, Fable 5, Sonnet 5) are all no-shows. Not Cursor's fault—they're just the messenger getting shot. (Auto-resolved: no updates in 24h)

🟢 CURSOR Aug 12, 2026

🟡 Bugbot and Cloud Agents went to GitHub for directions and haven't come back. Users watching their deploys hang like a bad internet connection at a Starbucks. GitHub's having a moment, and Cursor's along for the ride. (Auto-resolved: no updates in 24h)