Resuelto · duró 9 h

Caída de Cursor el 28 de octubre

Los informes de Cursor subieron a 261 por hora y se mantuvieron altos durante 9 h.

Inicio
14:00
28 de octubre de 2026 · UTC
Vuelta a la normalidad
23:00
9 h después
Pico
261/h
52× lo normal
Incidente de Cursor
1 h 58 min
Multiple services degraded

Informes durante la caída

12:000:50 UTC

Lo que dijo Cursor

status.cursor.com
Resuelto21:15–23:13 · 1 h 58 min

Multiple services degraded

  1. Resuelto · 23:13

    This incident has been resolved. All services have returned to normal operation.

  2. Investigando · 22:42

    Services have recovered and we're monitoring to make sure everything stays stable. If you're still seeing errors, please try again. We'll post another update once we've confirmed the issue is fully resolved.

  3. Resuelto · 22:40

    Services have recovered and we're monitoring to make sure everything stays stable. If you're still seeing errors, please try again. We'll post another update once we've confirmed the issue is fully resolved.

  4. Investigando · 22:06

    A fix has been implemented and services are starting to recover. We will share another update shortly.

  5. Investigando · 21:39

    We are investigating service degradation for multiple services. Users may see failures across Automations, Bugbot, Cloud Agents, Grok Bot, and Origin. We are working on a fix and will update shortly.

  6. Investigando · 21:15

    We are investigating service degradation for multiple services. Users may see failures across Cloud Agents, Grok Bot, and Origin. Apologies for the trouble.

Cursor publicó su primera actualización 7 h 15 min después de que los informes empezaran a subir.

Lo que dijeron los usuarios

  • DimitarEnschede, NL · 21:43

    can't login

1 comentarios durante la caída

¿Está Cursor caído ahora mismo?

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

Estado de Cursor ahora →