← Back to the carnage
CURSOR
🟡 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)
// The official story
Investigating service degradation — Bugbot and Cloud Agents
// Status page says
Aug 12 , 20:55 UTC Investigating - We are investigating a service degradation affecting Cloud Agents and Bugbot due to an ongoing GitHub outage. Users may see failures or delays when starting or running Cloud Agents and when Bugbot attempts to run.
🔗 Official status page (for the PR-approved version)
https://status.cursor.com/incidents/xm5pw3sqdyc9Cursor'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
Sep 25, 2026
🟠 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)
🟢 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)