Resuelto · duró 3 h
Caída de Cursor el 13 de octubre
Los informes de Cursor subieron a 609 por hora y se mantuvieron altos durante 3 h.
- Inicio
- 0:00
- 13 de octubre de 2026 · UTC
- Vuelta a la normalidad
- 3:00
- 3 h después
- Pico
- 609/h
- 122× lo normal
- Incidente de Cursor
- 2 h 46 min
- Degraded performance and errors across Cursor services
Informes durante la caída
Lo que dijo Cursor
status.cursor.comDegraded performance and errors across Cursor services
- Resuelto · 3:07
This incident has been resolved.
- Supervisando · 2:23
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.
- Supervisando · 1:49
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.
- Supervisando · 1:32
We are continuing to monitor recovery. Some users may still see intermittent errors.
- Supervisando · 0:53
A fix has been implemented and services are recovering. Some users may still see intermittent errors while we monitor for full restoration.
- Investigando · 0:22
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 publicó su primera actualización 22 min después de que los informes empezaran a subir.
Lo que dijeron los usuarios
- BR1Ciudad Guzmán, MX · 0:26
No carga
1 comentarios durante la caída
¿Está Cursor caído ahora mismo?
Estado en directo, informes de hoy y otras caídas anteriores.