← Cursor status now

Cursor problems on 28 October 2026

Timeline

1. 28 Oct 2026, 21:15 UTC
   We started seeing problems. Our verdict: Some users report problems.
2. 28 Oct 2026, 21:15 UTC · official update
   Multiple services degraded: Cloud Agents, Grok Bot, Origin (investigating): “We are investigating service degradation for multiple services. Users may see failures across Cloud Agents, Grok Bot, and Origin. Apologies for the trouble.” Source
3. 28 Oct 2026, 21:40 UTC · official update
   Multiple services degraded (investigating): “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.” Source
4. 28 Oct 2026, 22:07 UTC · official update
   Multiple services degraded (investigating): “A fix has been implemented and services are starting to recover. We will share another update shortly.” Source
5. 28 Oct 2026, 22:41 UTC
   Looking normal again. We'll keep watching for 15 minutes before closing this.
6. 28 Oct 2026, 22:42 UTC
   Our verdict changed to: Some users report problems.
7. 28 Oct 2026, 22:42 UTC · official update
   Multiple services degraded (investigating): “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.” Source
8. 28 Oct 2026, 23:14 UTC
   Looking normal again. We'll keep watching for 15 minutes before closing this.
9. 28 Oct 2026, 23:28 UTC
   Everything has looked normal for 15 minutes, so we marked this incident as resolved.

Times are shown in your local time zone. “Official update” entries quote Anysphere's status page; follow the source link for the full text.

How we track incidents

We open an incident when Cursor stops looking normal or Anysphere posts an official incident, and close it after 15 minutes with everything back to normal. More about our method.