Résolu · a duré 9 h
Panne de Cursor le 28 octobre
Les signalements pour Cursor ont grimpé à 261 par heure et sont restés élevés pendant 9 h.
- Début
- 14:00
- 28 octobre 2026 · UTC
- Retour à la normale
- 23:00
- 9 h plus tard
- Pic
- 261/h
- 52× la normale
- Incident de Cursor
- 1 h 58 min
- Multiple services degraded
Signalements pendant la panne
Ce que Cursor a dit
status.cursor.comMultiple services degraded
- Résolu · 23:13
This incident has been resolved. All services have returned to normal operation.
- En cours d'investigation · 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.
- Résolu · 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.
- En cours d'investigation · 22:06
A fix has been implemented and services are starting to recover. We will share another update shortly.
- En cours d'investigation · 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.
- En cours d'investigation · 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 a publié sa première mise à jour 7 h 15 min après le début de la hausse des signalements.
Ce que les utilisateurs ont dit
- DimitarEnschede, NL · 21:43
can't login
1 commentaires pendant la panne
Cursor est-il en panne en ce moment ?
État en direct, signalements du jour et autres pannes passées.