Is Cursor down? › Outage history › Sep 3, 2026
Cursor outage on Sep 3, 2026: what happened
On Sep 3, 2026, the Cursor status page reported "Investigating service degradation". About 3 hours 26 min: from Sep 3, 2026, 13:41 UTC to Sep 3, 2026, 17:07 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, 13:41 UTC
- Resolved
- Sep 3, 2026, 17:07 UTC
- Duration
- 3 hours 26 min
- Official impact
- Critical
- Affected
- Automations, Review Agents, Cloud Agents, IDE, Grok Bot
- Source
- Investigating service degradation on the Cursor status page
The Cursor status page rated it "Critical", its highest impact level: an outage of the affected parts, not only slowness.
What caused the Cursor outage?
The Cursor status page has not published a cause. When it identified the problem at 15:33 UTC on Sep 3, 2026, it said: "We have identified the cause and are actively working on a mitigation."
When was it fixed?
The Cursor status page marked it resolved at Sep 3, 2026, 17:07 UTC, 3 hours 26 min after it started.
Timeline of official updates
Every update the Cursor status page posted, oldest first. Times are UTC.
Sep 3, 2026, 13:41 UTC investigating
We are investigating a service degradation affecting All Grok Models, Automations, Cloud Agents, Grok Bot and Review Agents
Sep 3, 2026, 15:33 UTC identified
We have identified the cause and are actively working on a mitigation.
Sep 3, 2026, 17:07 UTC resolved
This incident has been resolved.
Cursor outage questions
What caused the Cursor outage on Sep 3, 2026?
The Cursor status page has not published a cause. When it identified the problem (Sep 3, 2026, 15:33 UTC) it said: "We have identified the cause and are actively working on a mitigation."
When was the Cursor outage on Sep 3, 2026 fixed?
The Cursor status page marked it resolved at Sep 3, 2026, 17:07 UTC, 3 hours 26 min after it started.
How long did the Cursor outage last?
About 3 hours 26 min: from Sep 3, 2026, 13:41 UTC to Sep 3, 2026, 17:07 UTC, by the official start and resolution times.
Was Cursor completely down?
The Cursor status page rated it "Critical", its highest impact level: an outage of the affected parts, not only slowness. The affected parts listed were: Automations, Review Agents, Cloud Agents, IDE, Grok Bot.
Which parts of Cursor were affected?
The Cursor status page listed: Automations, Review Agents, Cloud Agents, IDE, Grok Bot.
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.