← Back to the carnage
CURSOR

🟡 Cursor's usage dashboard decided to play hide-and-seek with actual data. Some users seeing either glacial load times or pure void where their metrics used to be. Engineering team is currently speed-reading the docs on how their own APIs work. (Auto-resolved: no updates in 24h)

⏰ Nov 10, 2026 Fixed (for now) spotted via status_rss

// The official story

[grok.com] Usage data slow or unavailable for some users.

// Status page says

Status: ACTIVE Severity: disruption Updates: Tue, 10 Nov 2026 18:32:45 GMT Investigating We are investigating an issue where usage data on the dashboard and the usage APIs may be slow or show no usage for some users.

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

https://status.x.ai/grok-com/ps_bf5495b2ac4634a8

Cursor's Greatest Hits

🟢 CURSOR Oct 23, 2026
🟡 Cursor's Grok models decided to pull a Houdini act. Engineers are currently investigating what can only be described as an existential crisis in the model layer. The irony of an AI reasoning engine becoming unreasonable is not lost on anyone. (Auto-resolved: no updates in 24h)
🟢 CURSOR Oct 13, 2026
🟡 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. (Auto-resolved: no updates in 24h)
🟢 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)