Resolved · lasted 3 h
Cursor outage on October 13
Reports for Cursor jumped to 609 an hour and stayed high for 3 h.
- Started
- 12:00 AM
- October 13, 2026 · UTC
- Back to normal
- 3:00 AM
- 3 h later
- Peak
- 609/hr
- 122× normal
- Cursor’s incident
- 2 h 46 min
- Degraded performance and errors across Cursor services
Reports during the outage
What Cursor said
status.cursor.comDegraded performance and errors across Cursor services
- Resolved · 3:07 AM
This incident has been resolved.
- Monitoring · 2:23 AM
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.
- Monitoring · 1:49 AM
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.
- Monitoring · 1:32 AM
We are continuing to monitor recovery. Some users may still see intermittent errors.
- Monitoring · 12:53 AM
A fix has been implemented and services are recovering. Some users may still see intermittent errors while we monitor for full restoration.
- Investigating · 12:22 AM
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.
Cursor posted its first update 22 min after reports started rising.
What people said
- BR1Ciudad Guzmán, MX · 12:26 AM
No carga
1 comments during the outage
Is Cursor down right now?
Live status, today’s reports and other past outages.