outages.live
Live

Cursor

Cursor is operational

Checked 58 s ago Operational

History

90 days agoToday

Incidents in 90 days

48

Days with an incident

30

Median duration

1 h 7 min

Longest incident

9 h 34 min

Components

11
Cursor IDE (iOS) Operational
90 days ago13 days with an incidentToday
IDE Operational
90 days ago16 days with an incidentToday
Cloud Agents Operational
90 days ago21 days with an incidentToday
CLI Operational
90 days ago14 days with an incidentToday
Automations Operational
90 days ago15 days with an incidentToday
BugBot Operational
90 days ago3 days with an incidentToday
Review Agents Operational
90 days ago8 days with an incidentToday
Grok Bot Operational
90 days ago23 days with an incidentToday
cursor.com Operational
90 days ago9 days with an incidentToday
Origin Operational
90 days ago4 days with an incidentToday
Enterprise Dashboard Operational
90 days ago1 day with an incidentToday

Past incidents

Provider status pageTimes in UTC

Nov 1, 2026

Duration5 h 15 min05:38 to 10:53Service Degradation - Billing and Usage DashboardDegraded

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.

Oct 31, 2026

Duration44 min06:04 to 06:47Multiple services degradedDegraded

This incident has been resolved.

Oct 29, 2026

Duration1 h 36 min23:44 to 01:20Auto Review DegradationDegraded

This has been resolved

Duration7 h 42 min23:29 to 07:11Cloud Agent DegradationDegraded

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

Duration9 h 34 min21:38 to 07:12Investigating Service Degradation with VS Code ExtensionsDegraded

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

Duration17 min09:01 to 09:18Degraded performance — Origin and Cloud AgentsDegraded

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

Oct 28, 2026

Duration1 h 58 min21:15 to 23:13Multiple services degradedPartial outage

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

Oct 27, 2026

Duration10 min20:33 to 20:43Delayed responses in Grok BotPartial outage

This issue has been resolved. For a short period, some Grok Bot responses were delayed. Responses are back to normal and we're sorry for the disruption.

Duration46 min07:33 to 08:18Elevated errors affecting repository integrationsNotice

This incident has been resolved. Affected services returned to normal operation at approximately 08:02 UTC.

Duration5 min00:19 to 00:24Payment System Sync IssuesDegraded

This has been resolved.

Oct 26, 2026

Duration3 h 17 min22:02 to 01:19Degraded agent personalization and codebase syncDegraded

This has been resolved.

Duration1 h 24 min14:02 to 15:25Elevated errors for Claude Sonnet 5.5Degraded

This incident has been resolved.

Oct 24, 2026

Duration1 min00:03 to 00:04Degraded Model PerformanceDegraded

We have identified and resolved the issue.

Oct 23, 2026

Duration41 min23:39 to 00:20Investigating service outage - Grok models unavailablePartial outage

This incident has been resolved.

Oct 21, 2026

Duration13 min17:40 to 17:53Elevated errors for Bitbucket Cloud integrationsDegraded

Atlassian has reported the issue as resolved and they are continuing to monitor for service restoration.

Duration1 h 54 min15:46 to 17:40Investigating service degradationDegraded

This incident has been resolved.

Oct 19, 2026

Duration19 min18:09 to 18:28Investigating service degradation — Grok BotDegraded

This incident has been resolved.

Duration1 h 7 min16:15 to 17:21Investigating service degradation — Grok BotDegraded

This incident has been resolved.

Duration27 min13:24 to 13:52Investigating service degradationDegraded

This incident has been resolved. Thank you for your patience!

Oct 15, 2026

Duration6 h 56 min22:25 to 05:20Elevated errors affecting Grok modelsDegraded

This incident has been resolved. Grok models in Cursor are working normally again.

Oct 14, 2026

Duration5 h 18 min15:46 to 21:04Investigating service degradation — Grok BotDegraded

This incident has been resolved.

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

Go from tracking outages to fixing production issues with Polylane.

Try Polylane