← Back to the carnage
CURSOR
🟠 Cursor's Bugbot and Background Agents got ghosted by GitHub's API for 22 minutes. Turns out when you build on someone else's foundation and they trip, you face-plant too. Crisis averted—GitHub remembered how to internet again. (Auto-resolved: no updates in 24h)
// The official story
Bugbot and Background Agents degraded due to a GitHub outage
// Status page says
Jan 15 , 17:55 UTC Resolved - GitHub API error rates have recovered Jan 15 , 17:47 UTC Monitoring - GitHub API error rates are recovering Jan 15 , 17:33 UTC Investigating - We are investigating this issue.
🔗 Official status page (for the PR-approved version)
https://status.cursor.com/incidents/y9299d2dfcbcCursor's Greatest Hits
🔴 CURSOR
21h 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)