Cursor outage on October 13, 2026: Degraded performance and errors across Cursor services
Cursor reported an incident affecting Cursor for 2 hours 46 minutes on 13 October 2026, from 00:22 to 03:07 UTC.
Resolved
Official incident reported by Cursor
- Started
- 00:22
- 13 Oct 2026 UTC
- Resolved
- 03:07
- 13 Oct 2026 UTC
- Duration
- 2h 46m
- 2 hours 46 minutes
- Impact
- Minor
- as rated by Cursor
- Updates
- 6
- posted by Cursor
Timeline
All times UTC.
Official incident from Cursor
Degraded performance and errors across Cursor services
-
Official
Investigating
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.
-
Official
Monitoring
A fix has been implemented and services are recovering. Some users may still see intermittent errors while we monitor for full restoration.
-
Official
Monitoring
We are continuing to monitor recovery. Some users may still see intermittent errors.
-
Official
Monitoring
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.
-
Official
Monitoring
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.
-
Official
Resolved
This incident has been resolved.
"Official" rows are quoted from Cursor's public status page, status.cursor.com. Very long posts are shortened.
What our checkpoints saw
HostTracker's checkpoints, which test cursor.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live Cursor status shows what our checks see right now.
Does your product depend on Cursor?
An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.
You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.
Independent measurement by HostTracker. Not affiliated with Cursor. Official updates are quoted from Cursor's public status page and remain Cursor's own words.