Résolu · a duré 3 h
Panne de Cursor le 13 octobre
Les signalements pour Cursor ont grimpé à 609 par heure et sont restés élevés pendant 3 h.
- Début
- 0 h 00
- 13 octobre 2026 · UTC
- Retour à la normale
- 3 h 00
- 3 h plus tard
- Pic
- 609/h
- 122× la normale
- Incident de Cursor
- 2 h 46 min
- Degraded performance and errors across Cursor services
Signalements pendant la panne
Ce que Cursor a dit
status.cursor.comDegraded performance and errors across Cursor services
- Résolu · 3 h 07
This incident has been resolved.
- Surveillance · 2 h 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.
- Surveillance · 1 h 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.
- Surveillance · 1 h 32
We are continuing to monitor recovery. Some users may still see intermittent errors.
- Surveillance · 0 h 53
A fix has been implemented and services are recovering. Some users may still see intermittent errors while we monitor for full restoration.
- En cours d'investigation · 0 h 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 a publié sa première mise à jour 22 min après le début de la hausse des signalements.
Ce que les utilisateurs ont dit
- BR1Ciudad Guzmán, MX · 0 h 26
No carga
1 commentaires pendant la panne
Cursor est-il en panne en ce moment?
État en direct, signalements du jour et autres pannes passées.