Computer use in Grok Bot fails for users in a few regions.
Computer use in Grok Bot fails for users in a few regions. Cursor reports that the issue is resolved. The outage lasted 14 minutes.
State
Resolved
Started
Lasted
14 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
14 min 100%
Updates
Times in UTCAs posted by Cursor
The issue is resolved and computer use in Grok Bot is working normally again for all users.
We've identified an issue where computer use in Grok Bot is failing for users in some regions. Other Grok Bot features are working normally. Our team is working on a fix, and we'll share an update as soon as we have more information.
Affected components
1Cursor in the last 90 days
Full historyIncidents in 90 days
53
Days with an incident
34
Median duration
1 h 7 min
This incident
80% shorter than the median
Other Cursor incidents
All incidentsCursor·composer-2.5 degraded
Cursor reports that composer-2.5 requests were degraded. This affected Automations, Bugbot, Cloud Agents, CLI, IDE, and Cursor IDE (iOS). Cursor resolved the incident after 50 minutes.
Cursor·Degraded Performance - Grok Bot
The Grok Bot component had degraded performance. Cursor reports that the issue is resolved. The incident lasted 75 minutes.
Cursor·3 "Slow clones from GH due to Github degradation"
Cursor Cloud Agents and Bugbot had slow startups and slow runs. The cause was a GitHub incident that affected Git operations. Cursor reports that the incident is resolved. It lasted about 72 minutes.
Cursor·Issues with source control integrations
Source control integrations do not work in the Cursor IDE and Grok Bot. Cursor reports that the issue is resolved. The outage lasted 1 hour and 15 minutes.
Cursor·Service Degradation - Billing and Usage Dashboard
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.
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.
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.
https://outages.live/feed.xml?providers=cursor/feed subscribe https://outages.live/feed.xml?providers=cursorFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane