> Markdown version of https://getuptimely.com/service-status/cursor — the page itself is the canonical copy. Service status # Cursor status Is Cursor down? This is Cursor’s current status, its components and its recent incidents, read from [Cursor’s official status page](https://status.cursor.com) and refreshed every 2 minutes. ## All Systems Operational As reported by Cursor’s status page, read Oct 24, 2026, 18:03 UTC. ## Scheduled maintenance - **[Cursor status updates are moving to status.x.ai](https://stspg.io/x7nspq96xvck)** · Oct 19, 2026, 12:04 UTC · scheduled, maintenance impact ## Components __Cursor components and their status__ | Component | Status | | ------------- | ----------- | | Automations | Operational | | Review Agents | Operational | | CLI | Operational | | Cloud Agents | Operational | | cursor.com | Operational | | IDE | Operational | | Origin | Operational | | Grok Bot | Operational | What a [degraded performance](https://getuptimely.com/glossary/degraded-performance) status means, and how much downtime an SLA allows: [the uptime calculator](https://getuptimely.com/tools/uptime-calculator). ## Recent Cursor incidents - **[Investigating service outage - Grok models unavailable](https://stspg.io/gr52z37rn6l2)** · Oct 23, 2026, 23:39 UTC · resolved, major impact, lasted 41 min This incident has been resolved. - **[Elevated errors for Bitbucket Cloud integrations](https://stspg.io/fh455gbmxf9q)** · Oct 21, 2026, 17:40 UTC · resolved, minor impact, lasted 13 min Atlassian has reported the issue as resolved and they are continuing to monitor for service restoration. - **[Investigating service degradation](https://stspg.io/jythbn6wf94k)** · Oct 21, 2026, 15:46 UTC · resolved, minor impact, lasted 1 h 54 min This incident has been resolved. - **[Investigating service degradation](https://stspg.io/sp4pggjpwr95)** · Oct 21, 2026, 10:21 UTC · resolved, minor impact, lasted 0 min We experienced service degradation affecting Anthropic models between 5:56 ET and 6:21 ET, which has since been resolved. - **[Investigating service degradation — Grok Bot](https://stspg.io/m85mb3fzh2nh)** · Oct 19, 2026, 18:09 UTC · resolved, minor impact, lasted 19 min This incident has been resolved. - **[Investigating service degradation — Grok Bot](https://stspg.io/0s6t57vsg1nl)** · Oct 19, 2026, 16:15 UTC · resolved, minor impact, lasted 1 h 7 min This incident has been resolved. - **[Investigating service degradation](https://stspg.io/zf1tvrpck8sj)** · Oct 19, 2026, 13:24 UTC · resolved, minor impact, lasted 27 min This incident has been resolved. Thank you for your patience! - **[Elevated errors affecting Grok models](https://stspg.io/nbsrtgp6pr7p)** · Oct 15, 2026, 22:25 UTC · resolved, minor impact, lasted 6 h 56 min This incident has been resolved. Grok models in Cursor are working normally again. - **[Investigating service degradation — Grok Bot](https://stspg.io/tp05ff30h17j)** · Oct 14, 2026, 15:46 UTC · resolved, minor impact, lasted 5 h 18 min This incident has been resolved. - **[Grok Bot routines not triggering](https://stspg.io/6x4hzfm1n6v7)** · Oct 13, 2026, 20:29 UTC · resolved, major impact, lasted 0 min Between 10:52 AM and 1:29 PM PT on October 13, many Grok Bot routines started by webhooks, Slack, git, email and Linear events didn't run. Webhook callers may have seen an HTTP 400 "Automation run rate limit exceeded" error, and other triggers failed without an error. Your own… - **[Degraded performance and errors across Cursor services](https://stspg.io/wb9c5pzxfnz6)** · Oct 13, 2026, 00:22 UTC · resolved, minor impact, lasted 2 h 46 min This incident has been resolved. - **[Investigating service degradation — Cloud Agents and Grok Bot](https://stspg.io/zb0nz52c9qjh)** · Oct 9, 2026, 22:37 UTC · resolved, minor impact, lasted 31 min This incident has been resolved. New Cloud Agents and Grok Bot sessions are starting normally again. - **[Investigating service degradation — Cloud Agents](https://stspg.io/0d7b5swpyrhd)** · Oct 9, 2026, 21:31 UTC · resolved, minor impact, lasted 12 min This incident has been resolved. - **[Elevated errors affecting Opus 5.5](https://stspg.io/g415ws29757p)** · Oct 8, 2026, 19:52 UTC · resolved, minor impact, lasted 58 min This incident has been resolved. - **[Opus 5.5 is Experiencing 429s](https://stspg.io/4lwl9qsfhlln)** · Oct 8, 2026, 13:54 UTC · resolved, minor impact, lasted 1 h 37 min This incident has been resolved. Source: [Cursor](https://status.cursor.com), Cursor’s public status page, read Oct 24, 2026, 18:03 UTC. Uptimely is not affiliated with Cursor; incident text is Cursor’s own. ## Is it down for you, or for everyone? A status page shows what the vendor has confirmed, which often lags what users see. [Run a live check of cursor.com](https://getuptimely.com/is-it-down/cursor.com) to see whether it answers right now. ## Get alerted when Cursor has an incident Uptimely’s External Status Page monitor watches Cursor’s status page and alerts your team by email, SMS, phone call, Slack, Discord or browser push when it reports a problem, next to the monitors for your own services. [Watch Cursor free →](https://app.getuptimely.com/accounts/register) ## Status of similar services - [ChatGPT status](https://getuptimely.com/service-status/chatgpt) - [OpenAI status](https://getuptimely.com/service-status/openai) - [Claude status](https://getuptimely.com/service-status/claude) - [Perplexity status](https://getuptimely.com/service-status/perplexity) - [Groq status](https://getuptimely.com/service-status/groq) - [ElevenLabs status](https://getuptimely.com/service-status/elevenlabs) [Every service status we track](https://getuptimely.com/service-status) ### Is Cursor down right now? The status at the top of this page is Cursor's own, read from its public status page every couple of minutes. It shows what Cursor's team has confirmed. For an independent check of whether cursor.com answers right now, use the live check on the is-it-down page. ### Where is Cursor's official status page? Cursor publishes its status at https://status.cursor.com. This page shows the same data with the recent incident history in one place, and links each incident to Cursor's own write-up. ### Why does Cursor not work for me when its status says operational? A status page lists the incidents a vendor has confirmed, and confirmation takes time: problems often reach users minutes before they reach the status page, and some partial or regional problems never appear on it. Your own network, account or region can also be the cause. ### How can I get alerted when Cursor has an incident? Add an External Status Page monitor in Uptimely pointed at https://status.cursor.com. It reads the page on a schedule and alerts your team by email, SMS, phone call, Slack, Discord or browser push when Cursor reports a problem, beside the monitors for your own services.