Is Cursor down? › Outage history › Sep 3, 2026
Cursor partial outage on Sep 3, 2026: what happened
On Sep 3, 2026, the Cursor status page reported "Elevated errors for Anthropic Models". About 2 hours 15 min: from Sep 3, 2026, 14:17 UTC to Sep 3, 2026, 16:31 UTC, by the official start and resolution times.
Cursor right now
At our last refresh (Oct 22, 2026, 12:35 UTC) Cursor was up: All Systems Operational.
- Started
- Sep 3, 2026, 14:17 UTC
- Resolved
- Sep 3, 2026, 16:31 UTC
- Duration
- 2 hours 15 min
- Official impact
- Major
- Affected
- Automations, CLI, Cloud Agents, IDE
- Source
- Elevated errors for Anthropic Models on the Cursor status page
The Cursor status page rated the impact "Major": a partial outage. Some parts or some users were affected; it was not a complete outage.
What caused the Cursor partial outage?
The Cursor status page has not published a cause. Its updates describe the symptoms only.
When was it fixed?
The Cursor status page marked it resolved at Sep 3, 2026, 16:31 UTC, 2 hours 15 min after it started. Its resolution note: "Elevated errors affecting Anthropic models have been resolved. Service has been restored."
Timeline of official updates
Every update the Cursor status page posted, oldest first. Times are UTC.
Sep 3, 2026, 14:17 UTC investigating
An upstream Anthropic issue is causing elevated errors for Fable 5.1, Fable 5, Opus 5, Opus 4.8, and Opus 4.6 requests. Some users may experience errors or failed Agent turns. We're monitoring recovery and will provide updates.
Sep 3, 2026, 15:55 UTC investigating
Anthropic reports recovery across most models. The affected models right now are Opus 4.8 and Opus 5. Please see https://status.claude.com/ for provider updates.
Sep 3, 2026, 16:31 UTC resolved
Elevated errors affecting Anthropic models have been resolved. Service has been restored.
Cursor partial outage questions
What caused the Cursor partial outage on Sep 3, 2026?
The Cursor status page has not published a cause.
When was the Cursor partial outage on Sep 3, 2026 fixed?
The Cursor status page marked it resolved at Sep 3, 2026, 16:31 UTC, 2 hours 15 min after it started. Its resolution note: "Elevated errors affecting Anthropic models have been resolved. Service has been restored."
How long did the Cursor partial outage last?
About 2 hours 15 min: from Sep 3, 2026, 14:17 UTC to Sep 3, 2026, 16:31 UTC, by the official start and resolution times.
Was Cursor completely down?
No. The Cursor status page rated the impact "Major": a partial outage. Some parts or some users were affected; it was not a complete outage. The affected parts listed were: Automations, CLI, Cloud Agents, IDE.
Which parts of Cursor were affected?
The Cursor status page listed: Automations, CLI, Cloud Agents, IDE.
Other recent Cursor incidents
- Elevated errors for Bitbucket Cloud integrations Oct 21, 2026, 17:40 UTC, 13 minutes
- Investigating service degradation Oct 21, 2026, 15:46 UTC, 1 hour 54 min
- Investigating service degradation Oct 21, 2026, 10:37 UTC, duration not stated
- Investigating service degradation - Grok Bot Oct 19, 2026, 18:09 UTC, 19 minutes
- Investigating service degradation - Grok Bot Oct 19, 2026, 16:15 UTC, 1 hour 7 min
- Investigating service degradation Oct 19, 2026, 13:24 UTC, 27 minutes
Full Cursor outage history and biggest outages → · Recent outages across all services →
Quotes are the Cursor status page's own words, from the official incident. Is It Up or Down is independent and not affiliated with Cursor. Times are UTC.