Is Cursor down? › Outage history › Sep 18, 2026
Cursor partial outage on Sep 18, 2026: what happened
On Sep 18, 2026, the Cursor status page reported "Investigating service degradation - Grok Bot". About 5 hours 43 min: from Sep 18, 2026, 17:19 UTC to Sep 18, 2026, 23:02 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 18, 2026, 17:19 UTC
- Resolved
- Sep 18, 2026, 23:02 UTC
- Duration
- 5 hours 43 min
- Official impact
- Major
- Affected
- Grok Bot
- Source
- Investigating service degradation - Grok Bot 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 19:01 UTC on Sep 18, 2026, it said: "The root cause has been identified and a fix is being rolled out. Some users may see Grok Bot respond slowly or not respond at all. We will provide another update shortly."
When was it fixed?
The Cursor status page marked it resolved at Sep 18, 2026, 23:02 UTC, 5 hours 43 min after it started. A fix was in place and being monitored from Sep 18, 2026, 19:53 UTC.
Timeline of official updates
Every update the Cursor status page posted, oldest first. Times are UTC.
Sep 18, 2026, 17:19 UTC investigating
We are investigating a service degradation affecting Grok Bot.
Sep 18, 2026, 19:01 UTC identified
The root cause has been identified and a fix is being rolled out. Some users may see Grok Bot respond slowly or not respond at all. We will provide another update shortly.
Sep 18, 2026, 19:53 UTC monitoring
A fix has been implemented and we are monitoring for service restoration. Grok Bot should be responding normally again.
Sep 18, 2026, 23:02 UTC resolved
This incident has been resolved.
Cursor partial outage questions
What caused the Cursor partial outage on Sep 18, 2026?
The Cursor status page has not published a cause. When it identified the problem (Sep 18, 2026, 19:01 UTC) it said: "The root cause has been identified and a fix is being rolled out. Some users may see Grok Bot respond slowly or not respond at all. We will provide another update shortly."
When was the Cursor partial outage on Sep 18, 2026 fixed?
The Cursor status page marked it resolved at Sep 18, 2026, 23:02 UTC, 5 hours 43 min after it started. A fix was in place and being monitored from Sep 18, 2026, 19:53 UTC.
How long did the Cursor partial outage last?
About 5 hours 43 min: from Sep 18, 2026, 17:19 UTC to Sep 18, 2026, 23:02 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.