Resolvido · durou 9 h
Falha do Cursor a 28 de outubro
Os relatos do Cursor subiram para 261 por hora e mantiveram-se elevados durante 9 h.
- Início
- 14:00
- 28 de outubro de 2026 · UTC
- De volta ao normal
- 23:00
- 9 h depois
- Pico
- 261/h
- 52× o normal
- Incidente de Cursor
- 1 h 58 min
- Multiple services degraded
Relatos durante a falha
O que Cursor disse
status.cursor.comMultiple services degraded
- Resolvido · 23:13
This incident has been resolved. All services have returned to normal operation.
- A investigar · 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.
- Resolvido · 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.
- A investigar · 22:06
A fix has been implemented and services are starting to recover. We will share another update shortly.
- A investigar · 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.
- A investigar · 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 publicou a primeira atualização 7 h 15 min depois de os relatos começarem a subir.
O que as pessoas disseram
- DimitarEnschede, NL · 21:43
can't login
1 comentários durante a falha
O Cursor está inativo neste momento?
Estado em direto, relatos de hoje e outras falhas anteriores.