Resuelto · duró 4 h

Caída de Cursor el 11 de agosto

Los informes de Cursor subieron a 78 por hora y se mantuvieron altos durante 4 h.

Inicio
3:00 p.m.
11 de agosto de 2026 · UTC
De vuelta a la normalidad
7:00 p.m.
4 h después
Pico
78/h
16× lo normal
Incidente de Cursor
6 h 16 min
Investigating service degradation — Automations, Cloud Agents, and IDE

Informes durante la caída

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

Lo que dijo Cursor

status.cursor.com
Resuelto5:22–11:38 p.m. · 6 h 16 min

Investigating service degradation — Automations, Cloud Agents, and IDE

  1. Resuelto · 11:38 p.m.

    This incident has been resolved.

  2. Supervisando · 10:29 p.m.

    We are continuing to monitor for service restoration.

  3. Supervisando · 8:29 p.m.

    We are continuing to monitor this issue.

  4. Investigando · 6:52 p.m.

    We found the root cause and are working on implementing a fix.

  5. Investigando · 6:13 p.m.

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

  6. Investigando · 5:35 p.m.

    This service degradation is affecting Claude Fable 5 as well.

  7. Investigando · 5:22 p.m.

    We are investigating a service degradation affecting Automations, Cloud Agents, and IDE. Affected agent surfaces: Composer, Claude Fable 5

Cursor publicó su primera actualización 2 h 22 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 →