Behoben · dauerte 3 Std.
Cursor-Ausfall am 13. Oktober
Die Meldungen zu Cursor stiegen auf 609 pro Stunde und blieben 3 Std. lang hoch.
- Beginn
- 0:00
- 13. Oktober 2026 · UTC
- Wieder normal
- 3:00
- 3 Std. später
- Spitze
- 609/Std.
- 122× normal
- Vorfall bei Cursor
- 2 Std. 46 Min.
- Degraded performance and errors across Cursor services
Meldungen während des Ausfalls
Was Cursor sagte
status.cursor.comDegraded performance and errors across Cursor services
- Gelöst · 3:07
This incident has been resolved.
- Überwachung · 2:23
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.
- Überwachung · 1:49
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.
- Überwachung · 1:32
We are continuing to monitor recovery. Some users may still see intermittent errors.
- Überwachung · 0:53
A fix has been implemented and services are recovering. Some users may still see intermittent errors while we monitor for full restoration.
- Analyse · 0:22
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 veröffentlichte das erste Update 22 Min., nachdem die Meldungen zu steigen begannen.
Was Nutzer sagten
- BR1Ciudad Guzmán, MX · 0:26
No carga
1 Kommentare während des Ausfalls
Ist Cursor gerade ausgefallen?
Live-Status, heutige Meldungen und weitere frühere Ausfälle.