A ti yanjú · ó pẹ́ Wákàtí 3

Ìdádúró Cursor ní October 13

Ìròyìn fún Cursor gòkè sí 609 ní wákàtí kan, ó sì wà lókè fún Wákàtí 3.

Ó bẹ̀rẹ̀
12:00 AM
October 13, 2026 · UTC
Ó ti padà sí déédé
3:00 AM
Lẹ́yìn Wákàtí 3
Òkè jù
609/wákàtí
122× ti déédé
Ìṣẹ̀lẹ̀ Cursor
Wákàtí 2 ìṣẹ́jú 46
Degraded performance and errors across Cursor services

Ìròyìn nígbà ìdádúró

10:00 PM4:50 AM UTC

Ohun tí Cursor sọ

status.cursor.com
A yanjú12:22 – 3:07 AM · Wákàtí 2 ìṣẹ́jú 46

Degraded performance and errors across Cursor services

  1. A yanjú · 3:07 AM

    This incident has been resolved.

  2. Ìbójútó · 2:23 AM

    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. Ìbójútó · 1:49 AM

    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. Ìbójútó · 1:32 AM

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

  5. Ìbójútó · 12:53 AM

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

  6. Ìwádìí · 12:22 AM

    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 fi ìmúdójúìwọ̀n àkọ́kọ́ rẹ̀ sílẹ̀ ní Ìṣẹ́jú 22 lẹ́yìn tí ìròyìn bẹ̀rẹ̀ sí í pọ̀ sí i.

Ohun tí àwọn ènìyàn sọ

  • BR1Ciudad Guzmán, MX · 12:26 AM

    No carga

Ọ̀rọ̀ 1 nígbà ìdádúró

Ṣé Cursor ti dásẹsẹ báyìí?

Ipò ní tààrà, ìròyìn òní àti àwọn ìdádúró mìíràn tẹ́lẹ̀.

Ipò Cursor báyìí →