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
12:00 a.m.
13 de octubre de 2026 · UTC
De vuelta a la normalidad
3:00 a.m.
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

10:00 p.m.4:50 a.m. UTC

Lo que dijo Cursor

status.cursor.com
Resuelto12:22–3:07 a.m. · 2 h 46 min

Degraded performance and errors across Cursor services

  1. Resuelto · 3:07 a.m.

    This incident has been resolved.

  2. Supervisando · 2:23 a.m.

    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.

  3. Supervisando · 1:49 a.m.

    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.

  4. Supervisando · 1:32 a.m.

    We are continuing to monitor recovery. Some users may still see intermittent errors.

  5. Supervisando · 12:53 a.m.

    A fix has been implemented and services are recovering. Some users may still see intermittent errors while we monitor for full restoration.

  6. Investigando · 12:22 a.m.

    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 comenzaran a subir.

Lo que dijeron los usuarios

  • BR1Ciudad Guzmán, MX · 12:26 a.m.

    No carga

1 comentarios durante la caída

¿Está Cursor caído ahora mismo?

Estado en vivo, informes de hoy y otras caídas anteriores.

Estado de Cursor ahora →