Cursor billing dashboard degraded for 5 h 15 min, 4.4x its typical incident

What broke and for how long

Cursor is an AI coding editor and agent platform with a desktop app, a CLI, web and mobile agents, and cloud agents that run tasks in remote environments. The incident, titled "Service Degradation - Billing and Usage Dashboard", started at Nov 1, 05:38 UTC and was resolved at Nov 1, 10:53 UTC. The status page lists two affected components: cursor.com and the Enterprise Dashboard. Impact was rated minor, and no other products had this incident open in our data. The facts do not explain the cause.

How it compares with Cursor's usual incidents

Cursor's typical incident lasts 1 h 12 min, so this one ran well past the norm. It is still short of the longest incident in the past 12 months, which lasted 13 h 19 min. Incidents are frequent for this product: 23 in the last 30 days and 152 on the status page over the last 12 months; most are rated minor, like this one.

What the components cover

The listed components are cursor.com and the Enterprise Dashboard, where teams check spend, usage and seat data; the editor is not listed. The status page does not say whether coding sessions or agents were affected.

What it means for you

• Teams that budget around Cursor usage data should not rely on the dashboard alone during an open incident; check the incident page for updates.
• Subscribe to alerts on AgentGid or the Cursor status page; Cursor logged 23 incidents in 30 days.