Resolvido · durou 3 h
Falha do Cursor a 13 de outubro
Os relatos do Cursor subiram para 609 por hora e mantiveram-se elevados durante 3 h.
- Início
- 0:00
- 13 de outubro de 2026 · UTC
- De volta ao normal
- 3:00
- 3 h depois
- Pico
- 609/h
- 122× o normal
- Incidente de Cursor
- 2 h 46 min
- Degraded performance and errors across Cursor services
Relatos durante a falha
O que Cursor disse
status.cursor.comDegraded performance and errors across Cursor services
- Resolvido · 3:07
This incident has been resolved.
- Monitorização · 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.
- Monitorização · 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.
- Monitorização · 1:32
We are continuing to monitor recovery. Some users may still see intermittent errors.
- Monitorização · 0:53
A fix has been implemented and services are recovering. Some users may still see intermittent errors while we monitor for full restoration.
- A investigar · 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 publicou a primeira atualização 22 min depois de os relatos começarem a subir.
O que as pessoas disseram
- BR1Ciudad Guzmán, MX · 0:26
No carga
1 comentários durante a falha
O Cursor está inativo neste momento?
Estado em direto, relatos de hoje e outras falhas anteriores.