Is Cursor down? › Outage history › Sep 7, 2026
Cursor partial outage on Sep 7, 2026: what happened
On Sep 7, 2026, the Cursor status page reported "Grok Bot computers unreachable for some users". About 1 hour 5 min: from Sep 7, 2026, 20:32 UTC to Sep 7, 2026, 21:37 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 7, 2026, 20:32 UTC
- Resolved
- Sep 7, 2026, 21:37 UTC
- Duration
- 1 hour 5 min
- Official impact
- Major
- Affected
- Grok Bot
- Source
- Grok Bot computers unreachable for some users 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. When it identified the problem at 20:33 UTC on Sep 7, 2026, it said: "The root cause has been identified and a fix is being implemented."
When was it fixed?
The Cursor status page marked it resolved at Sep 7, 2026, 21:37 UTC, 1 hour 5 min after it started. A fix was in place and being monitored from Sep 7, 2026, 20:41 UTC.
Timeline of official updates
Every update the Cursor status page posted, oldest first. Times are UTC.
Sep 7, 2026, 20:32 UTC investigating
We have identified an issue affecting Grok Bot. Some users may be unable to reach their Grok Bot computer, and Recover or Reset may fail. Your data is not affected. A fix is rolling out and we will post another update shortly.
Sep 7, 2026, 20:33 UTC identified
The root cause has been identified and a fix is being implemented.
Sep 7, 2026, 20:41 UTC monitoring
A fix has been implemented and we are monitoring for service restoration.
Sep 7, 2026, 21:37 UTC resolved
This incident has been resolved.
Cursor partial outage questions
What caused the Cursor partial outage on Sep 7, 2026?
The Cursor status page has not published a cause. When it identified the problem (Sep 7, 2026, 20:33 UTC) it said: "The root cause has been identified and a fix is being implemented."
When was the Cursor partial outage on Sep 7, 2026 fixed?
The Cursor status page marked it resolved at Sep 7, 2026, 21:37 UTC, 1 hour 5 min after it started. A fix was in place and being monitored from Sep 7, 2026, 20:41 UTC.
How long did the Cursor partial outage last?
About 1 hour 5 min: from Sep 7, 2026, 20:32 UTC to Sep 7, 2026, 21:37 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: Grok Bot.
Which parts of Cursor were affected?
The Cursor status page listed: 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.