Outage history

Cursor Outage History

Recent incidents Anysphere has published for Cursor, newest first, with how long each one lasted.

18in the last 30 days
32in the last 90 days
6h 35mlongest outage
16 Sep 2026most recent

Showing 32 published incidents back to 29 Jul 2026.

  1. Minor16 Sep 202640 min

    Investigating service degradation

  2. Minor15 Sep 202633 min

    Investigating service degradation

  3. Minor14 Sep 202653 min

    Investigating Grok service degradation

  4. Minor11 Sep 202627 min

    Investigating service degradation

  5. Minor3 Sep 20261h 39m

    Degraded performance of Grok 4.6

  6. Minor3 Sep 20261h 48m

    Elevated errors for OpenAI Models

  7. Major3 Sep 20262h 15m

    Elevated errors for Anthropic Models

  8. Critical3 Sep 20263h 26m

    Investigating service degradation

  9. Minor2 Sep 20262h 19m

    Investigating service degradation

  10. Minor1 Sep 20261h 58m

    Degraded performance of Grok 4.5

  11. Minor1 Sep 202613 min

    Investigating service degradation

  12. Critical27 Aug 20267 min

    Investigating service degradation — cursor.com and IDE

  13. Minor25 Aug 202654 min

    Degraded performance of Grok models

  14. Minor25 Aug 20262h 43m

    Degraded performance of Grok 4.6

  15. Minor24 Aug 20263h 12m

    Elevated errors for Claude Opus 5

  16. Minor21 Aug 202647 min

    Investigating service degradation

  17. Major19 Aug 20262h 41m

    Fable 5 unavailable

  18. Minor19 Aug 20263h 2m

    Increased error rates for Composer 2.5

  19. Minor18 Aug 20261h 7m

    Investigating service degradation

  20. Minor17 Aug 20261h 7m

    Grok 4.6 availability issues

  21. Minor17 Aug 20264h 8m

    Investigating service degradation

  22. Major13 Aug 20264h 4m

    Investigating service degradation — Automations, Cloud Agents, and IDE

  23. Minor12 Aug 202621 min

    Investigating service degradation

  24. Minor12 Aug 20262h 32m

    Investigating service degradation — Automations, Cloud Agents, and IDE

  25. Minor11 Aug 20266h 16m

    Investigating service degradation — Automations, Cloud Agents, and IDE

  26. Minor6 Aug 202628 min

    Degraded Performance for Grok 4.5

  27. Minor5 Aug 20266h 35m

    Investigating service degradation

  28. Critical31 Jul 20261h 20m

    Investigating service degradation

  29. Minor30 Jul 202651 min

    Investigating service degradation — IDE

  30. Minor30 Jul 202617 min

    Investigating service degradation — IDE

  31. Critical29 Jul 20263h 18m

    Elevated errors affecting Anthropic models

  32. Minor29 Jul 20262h 47m

    Investigating Composer degradation

What this record shows

This list is scoped to Cursor’s own systems. It does not include the most common reason Cursor stops working, which is an incident at Anthropic or OpenAI — the providers whose models actually answer your requests. When one of those has trouble, Cursor fails while its own status stays green and nothing appears here.

So a quiet history alongside a bad week of your own is not a contradiction. Check the model providers before concluding the record is wrong: an outage at a provider is invisible to Anysphere’s status page by design.

Cursor reports separately on the IDE, Tab completions, Agent and Cloud Agents, and the CLI, so many entries affect one feature rather than the whole editor.

How to read the durations

Each entry runs from when Anysphere opened the incident to when it was marked resolved. That is a generous measure: an incident is usually opened once the problem is confirmed and closed after it has been stable for a while, so the window is wider than the period in which most people were actually affected.

Severity comes from the provider. Only major and critical entries count against the uptime figure on the Cursor status page, because a minor incident normally means degraded performance for some users rather than the service being unavailable.

This list is limited to what the provider has published and still exposes. Providers cap how far their public feed reaches, so an empty stretch further back means the record has aged out, not that nothing happened.

🔗 Keep checking