Behoben · dauerte 9 Std.
Cursor-Ausfall am 28. Oktober
Die Meldungen zu Cursor stiegen auf 261 pro Stunde und blieben 9 Std. lang hoch.
- Beginn
- 14:00
- 28. Oktober 2026 · UTC
- Wieder normal
- 23:00
- 9 Std. später
- Spitze
- 261/Std.
- 52× normal
- Vorfall bei Cursor
- 1 Std. 58 Min.
- Multiple services degraded
Meldungen während des Ausfalls
Was Cursor sagte
status.cursor.comMultiple services degraded
- Gelöst · 23:13
This incident has been resolved. All services have returned to normal operation.
- Analyse · 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.
- Gelöst · 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.
- Analyse · 22:06
A fix has been implemented and services are starting to recover. We will share another update shortly.
- Analyse · 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.
- Analyse · 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 veröffentlichte das erste Update 7 Std. 15 Min., nachdem die Meldungen zu steigen begannen.
Was Nutzer sagten
- DimitarEnschede, NL · 21:43
can't login
1 Kommentare während des Ausfalls
Ist Cursor gerade ausgefallen?
Live-Status, heutige Meldungen und weitere frühere Ausfälle.