outages.live
Live
CursorIncident · 2026-11-01 05:38 UTC

Service Degradation - Billing and Usage Dashboard

ResolvedOfficial update
0

Cursor reports a service degradation on the billing and usage dashboard. The cursor.com and Enterprise Dashboard components are affected. Cursor states that the incident is resolved. The outage lasted about 5 hours and 15 minutes.

State

Resolved

Started

20 h ago

2026-11-01 05:38 UTC

Lasted

5 h 15 min

until 2026-11-01 10:53 UTC

Worst impact

Degraded

Timeline

3 updates
05:3806:5708:1609:3410:53
DegradedUpdate postedTimes in UTC

Investigating

5 h 15 min 100%

Updates

Times in UTC

As posted by Cursor

Resolved2026-11-01 10:53 UTC

This incident has been resolved.

Investigating2026-11-01 08:45 UTC

We are continuing to work towards a resolution and will share more information as it becomes available.

Investigating2026-11-01 08:39 UTC

We are investigating a service degradation affecting our billing and usage dashboard. We will share updates as more information becomes available.

Affected components

2
cursor.comEnterprise Dashboard

Cursor in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

48

Days with an incident

30

Median duration

1 h 7 min

This incident

4.7× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

9 h 34 min
median 1 h 7 min
90 days agoToday

Other Cursor incidents

All incidents

Cursor·Multiple services degraded

This incident has been resolved.

Resolvedresolved 2 d ago

Cursor·Auto Review Degradation

This has been resolved

Resolvedresolved 3 d ago

Cursor·Cloud Agent Degradation

This incident has been resolved. Cloud Agent services have returned to normal operation.

Resolvedresolved 3 d ago

Cursor·Investigating Service Degradation with VS Code Extensions

This incident has been resolved. All services have returned to normal operation.

Resolvedresolved 3 d ago

Cursor·Degraded performance — Origin and Cloud Agents

This incident has been resolved. Cloud Agents and Origin have returned to normal performance.

Resolvedresolved 4 d ago

Follow Cursor

Your coding agent knows when Cursor is down, and tells you when a failure is theirs, not yours. You can also get Cursor incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "cursor" and tell me if Cursor has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=cursor
Slack
/feed subscribe https://outages.live/feed.xml?providers=cursor

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane