Cursor Status
System status
View historical uptime →Incident overview
Total incidents
88
Active now
1
Resolved
87
Avg. resolution
2h 3m
Recent incidents
View all →Investigating service degradation — Grok Bot and Review Agents
Investigating service degradation - xAI models
Investigating service degradation — Cloud Agents and Grok Bot
Investigating service degradation — Grok Bot
Investigating service degradation — Grok Bot
Investigating service degradation — Grok Bot
Investigating service degradation - Grok 4.7
Investigating — Cloud Agent Dockerfile Builds
Investigating service degradation — Automations and Cloud Agents w/ Grok 4.7
Investigating service degradation
Frequently asked questions
Is Cursor down right now?
Cursor is currently experiencing issues with 1 active incident. Current status: Degraded. Check the incident details above for more information.
What is Cursor's current uptime?
Cursor has a measured 30-day uptime of 99.61%. Over the last 24 hours, uptime is 100.00%, and over 7 days it is 99.95%. These figures are computed from Cursor's official status page data.
How many incidents has Cursor had recently?
Cursor has experienced 88 incidents in the recent monitoring window. Resolved incidents were fixed in an average of 2h 3m. 1 incident is currently active.
What components does Cursor monitor?
DevHelm tracks 8 individual components for Cursor, including Automations, Review Agents, CLI, Cloud Agents, cursor.com, and 3 more. Each component has its own status and 90-day uptime history shown above.
How can I get notified about Cursor outages?
You can subscribe to Cursor's incident feed via Atom/RSS at devhelm.io/status/cursor/feed.xml for use in any feed reader. For real-time alerts via Slack, email, PagerDuty, or webhooks, add Cursor as a dependency in your DevHelm workspace.
About Cursor status monitoring
This page provides real-time operational status for Cursor, powered by DevHelm's continuous monitoring infrastructure. We track Cursor's official status page and aggregate component-level data into uptime percentages, incident timelines, and historical trends.
Cursor status data is refreshed every 30 seconds. We currently track 8 individual components, each with its own operational status and 90-day uptime history.
Uptime percentages represent the proportion of time all monitored components reported operational status. Incident data comes from vendor-published incident timelines and includes status updates, affected components, and resolution times.
Track Cursor in your stack
Get alerted when Cursor has issues — before your users notice. Set up in 30 seconds.