Degraded performance and errors across Cursor services
minor- Started
- Oct 12, 8:22 PM EDT
- Resolved
- Oct 12, 11:07 PM EDT
- Duration
- 2h 45m
Anysphere's updates (6)
- investigating · Oct 12, 8:22 PM EDT
We are investigating a widespread issue affecting Cursor. Users may see errors or failed requests across the IDE, Cloud Agents, Automations, Grok Bot, and Origin. Our team is actively working to restore service.
- investigating · Oct 12, 8:53 PM EDT
A fix has been implemented and services are recovering. Some users may still see intermittent errors while we monitor for full restoration.
- investigating · Oct 12, 9:32 PM EDT
We are continuing to monitor recovery. Some users may still see intermittent errors.
- investigating · Oct 12, 9:49 PM EDT
Grok Bot has recovered and is operating normally. We are continuing to monitor recovery across the IDE, Cloud Agents, and other affected services, and some users may still see intermittent errors.
- investigating · Oct 12, 10:23 PM EDT
All Cursor services have recovered and are operating normally, except Cloud Agents. Some Cloud Agents may still be slow to start or fail to run, and we're actively working to restore full service. We'll share another update as soon as we have more information.
- resolved · Oct 12, 11:07 PM EDT
This incident has been resolved.
What our checks recorded
We checked Cursor 33 times from Anysphere's start time to its resolution, once every five minutes. Every one of them reached Cursor's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 156 ms, against 156 ms over the 24 hours before. Anysphere posted the incident at Oct 12, 8:22 PM EDT.
Updates are Anysphere's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗