Resuelto · duró 3 h

Caída de Cursor el 17 de septiembre

Los informes de Cursor subieron a 102 por hora y se mantuvieron altos durante 3 h.

Inicio
3:00 p.m.
17 de septiembre de 2026 · UTC
De vuelta a la normalidad
6:00 p.m.
3 h después
Pico
102/h
20× lo normal
Incidente de Cursor
4 h 44 min
Investigating service degradation — Cloud Agents and Automations

Informes durante la caída

1:00 p.m.7:50 p.m. UTC

Lo que dijo Cursor

status.cursor.com
Resuelto3:20–8:04 p.m. · 4 h 44 min

Investigating service degradation — Cloud Agents and Automations

  1. Resuelto · 8:04 p.m.

    This incident has been resolved.

  2. Supervisando · 6:12 p.m.

    A fix has been implemented and we are monitoring for service restoration.

  3. Investigando · 6:02 p.m.

    Affected services are back to normal operation. Our team continues to monitor everything closely.

  4. Investigando · 5:31 p.m.

    We are continuing to investigate this issue. Cloud Agents, Automations, and Review Agents (resulting from Cloud Agents) are affected. Bugbot is not affected.

  5. Investigando · 3:58 p.m.

    We are continuing to investigate this issue.

  6. Investigando · 3:50 p.m.

    We are currently investigating this issue. We will provide updates as more information becomes available.

  7. Investigando · 3:20 p.m.

    We are investigating a service degradation affecting Cloud Agents and Automations

Cursor publicó su primera actualización 20 min después de que los informes comenzaran a subir.

¿Está Cursor caído ahora mismo?

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

Estado de Cursor ahora →