Cursor Outage History

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