Cursor

Affected: Review Agents, Cloud Agents

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-10-21 17:40 UTC

   We are investigating an issue affecting Cursor's Bitbucket Cloud integration. More information: https://bitbucket.status.atlassian.com/incidents/ldlx0fdgls28.

2. resolved 2026-10-21 17:53 UTC

   Atlassian has reported the issue as resolved and they are continuing to monitor for service restoration.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: cursor.com, Grok Bot

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-21 15:46 UTC

   We are investigating a service degradation affecting billing dashboards. You may notice errors in regards to billing, usage, and plan changes.

2. monitoring 2026-10-21 15:56 UTC

   A fix has been implemented and we are monitoring for service restoration.

3. resolved 2026-10-21 17:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Anthropic (Claude).

1. resolved 2026-10-21 10:21 UTC

   We experienced service degradation affecting Anthropic models between 5:56 ET and 6:21 ET, which has since been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Grok Bot

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-19 18:09 UTC

   We are investigating a service degradation affecting Grok Bot and grok.com. You may notice errors related to billing, plans, and usage.

2. resolved 2026-10-19 18:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Grok Bot

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-19 16:15 UTC

   We are investigating a service degradation affecting Grok Bot where routines may be delayed.

2. investigating 2026-10-19 16:52 UTC

   We are continuing to investigate this issue. We will provide updates as more information becomes available.

3. monitoring 2026-10-19 17:10 UTC

   A fix has been implemented and we are monitoring for service restoration.

4. resolved 2026-10-19 17:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: CLI, Cloud Agents, cursor.com, IDE

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Anthropic (Claude).

1. investigating 2026-10-19 13:24 UTC

   We are investigating elevated errors for Anthropic Opus 5.5.

2. monitoring 2026-10-19 13:35 UTC

   A fix has been implemented and we are monitoring for service restoration.

3. resolved 2026-10-19 13:52 UTC

   This incident has been resolved. Thank you for your patience!

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: CLI, Cloud Agents, IDE

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-15 22:25 UTC

   We are investigating elevated errors affecting Grok models in Cursor. Some requests may fail with a capacity error. Retrying the request or switching to another model may help.

2. monitoring 2026-10-15 22:58 UTC

   A fix has been implemented and we are monitoring for service restoration.

3. resolved 2026-10-16 05:20 UTC

   This incident has been resolved. Grok models in Cursor are working normally again.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Grok Bot

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-14 15:46 UTC

   We are investigating a service degradation affecting Grok Bot and preventing some users from reaching their computers

2. identified 2026-10-14 20:08 UTC

   We've identified the issue impacting Grok Bot for some users and are working on a fix.

3. resolved 2026-10-14 21:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-10-13 20:29 UTC

   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...

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Automations, Review Agents, CLI, Cloud Agents, cursor.com, IDE, Origin, Grok Bot

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-13 00:22 UTC

   We are investigating a widespread issue affecting Cursor. Users may see errors or failed requests across the IDE, Cloud Agents, Automations, Grok Bot, and Origin. Our team is actively working to restore service.

2. monitoring 2026-10-13 00:53 UTC

   A fix has been implemented and services are recovering. Some users may still see intermittent errors while we monitor for full restoration.

3. monitoring 2026-10-13 01:32 UTC

   We are continuing to monitor recovery. Some users may still see intermittent errors.

4. monitoring 2026-10-13 01:49 UTC

   Grok Bot has recovered and is operating normally. We are continuing to monitor recovery across the IDE, Cloud Agents, and other affected services, and some users may still see intermittent errors.

5. monitoring 2026-10-13 02:23 UTC

   All Cursor services have recovered and are operating normally, except Cloud Agents. Some Cloud Agents may still be slow to start or fail to run, and we're actively working to restore full service. We'll share another update as soon as we have more information.

6. resolved 2026-10-13 03:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Cloud Agents, Grok Bot

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-09 22:37 UTC

   We are investigating a service degradation affecting Cloud Agents and Grok Bot. Some new Cloud Agents and Grok Bot sessions may fail to start.

2. resolved 2026-10-09 23:09 UTC

   This incident has been resolved. New Cloud Agents and Grok Bot sessions are starting normally again.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Cloud Agents

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-09 21:31 UTC

   We are investigating a service degradation affecting Cloud Agents.

2. resolved 2026-10-09 21:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Automations, CLI, Cloud Agents, IDE, Grok Bot

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-08 19:52 UTC

   We are investigating a service degradation affecting Opus 5.5. Users may see intermittent errors or failed requests when using Opus 5.5.

2. resolved 2026-10-08 20:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Automations, Review Agents, CLI, Cloud Agents, IDE, Grok Bot

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-08 13:54 UTC

   We are investigating a service degradation with Opus 5.5 being used across all product components.

2. monitoring 2026-10-08 14:08 UTC

   A fix has been implemented and we are monitoring for service restoration.

3. resolved 2026-10-08 15:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Grok Bot

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-07 15:59 UTC

   We are investigating a service degradation affecting Grok Bot's computers in certain regions.

2. resolved 2026-10-07 17:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Cloud Agents, Grok Bot

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-06 22:48 UTC

   We are investigating a service degradation affecting Cloud Agents.

2. investigating 2026-10-06 22:52 UTC

   We are currently investigating this issue. We will provide updates as more information becomes available.

3. investigating 2026-10-06 22:53 UTC

   We are currently investigating this issue. We will provide updates as more information becomes available.

4. investigating 2026-10-06 22:53 UTC

   We are currently investigating this issue. We will provide updates as more information becomes available.

5. resolved 2026-10-06 23:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Cloud Agents, Grok Bot

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-06 19:27 UTC

   We are investigating a service degradation affecting some Cloud Agents and Grok Bot features.

2. investigating 2026-10-06 21:23 UTC

   We are currently investigating this issue. We will provide updates as more information becomes available.

3. investigating 2026-10-06 21:25 UTC

   Grok Bot has been restored. We are continuing to investigate a service degradation affecting some Cloud Agents.

4. resolved 2026-10-06 22:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Review Agents

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-06 17:49 UTC

   We are investigating a service degradation affecting Security Reviewer agents.

2. resolved 2026-10-06 18:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Automations, CLI, Cloud Agents, IDE

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Anthropic (Claude).

Started during Anthropic (Claude): Elevated errors for Claude Opus 5.5.

1. investigating 2026-10-06 12:40 UTC

   We are investigating a service degradation affecting Opus 5.5. More information: https://status.claude.com/incidents/ch27pb90bn85

2. resolved 2026-10-06 16:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Review Agents, Grok Bot

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-03 06:50 UTC

   We are investigating a service degradation affecting Grok Bot and Review Agents.

2. monitoring 2026-10-03 07:21 UTC

   A fix has been implemented and we are monitoring for service restoration.

3. resolved 2026-10-03 07:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: CLI, Cloud Agents, IDE, Grok Bot

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-29 19:43 UTC

   We are investigating a service degradation affecting xAI models. Some Agent requests may fail.

2. identified 2026-09-29 20:01 UTC

   We have identified the cause of degraded performance affecting xAI models and are working to restore full capacity. Users may see errors, slow responses, or rate limiting on these models, and some Cloud Agent tasks may fail. We will post another update shortly.

3. resolved 2026-09-29 20:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Cloud Agents, Grok Bot

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-29 14:25 UTC

   We are investigating a service degradation affecting Cloud Agents and Grok Bot.

2. identified 2026-09-29 15:26 UTC

   The root cause has been identified and a fix is being implemented.

3. monitoring 2026-09-29 17:54 UTC

   Fixes are being implemented and we are monitoring for service restoration.

4. resolved 2026-09-29 18:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Grok Bot

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-28 20:23 UTC

   We are investigating a service degradation affecting Grok Bot.

2. resolved 2026-09-28 20:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Grok Bot

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-25 23:47 UTC

   We are investigating a service degradation affecting Grok Bot.

2. monitoring 2026-09-26 00:22 UTC

   A fix has been implemented and we are monitoring for service restoration.

3. resolved 2026-09-26 00:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Grok Bot

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-25 05:17 UTC

   We are investigating a service degradation affecting Grok Bot. Grok Bot computers may temporarily not be able to be created, reached, or reset.

2. monitoring 2026-09-25 05:52 UTC

   We have identified the cause and are deploying a fix. We are monitoring recovery as the fix rolls out. Some Grok Bot computers may remain temporarily unavailable or unable to be created or reset during this time.

3. resolved 2026-09-25 06:51 UTC

   The service degradation affecting Grok Bot has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Automations, CLI, Cloud Agents, IDE

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-23 20:28 UTC

   We are investigating degraded performance for requests that use Grok 4.7.

2. monitoring 2026-09-23 20:31 UTC

   A fix has been implemented and we are monitoring for service restoration.

3. resolved 2026-09-23 20:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Cloud Agents

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-23 17:14 UTC

   Customers using Cloud Agents with Dockerfile-based builds may be unable to create new builds. Existing Cloud Agents continue to run on their current image; only new Dockerfile builds are affected.

2. identified 2026-09-23 17:15 UTC

   The root cause has been identified and a fix is being implemented.

3. monitoring 2026-09-23 18:39 UTC

   A fix has been implemented and we are monitoring for service restoration.

4. resolved 2026-09-23 18:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Automations, Cloud Agents

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-22 13:02 UTC

   We are aware of an issue where Grok 4.7 fails to be selected as a model for Cloud Agents. We are investigating the issue.

2. identified 2026-09-22 13:08 UTC

   The root cause has been identified and a fix is being implemented.

3. resolved 2026-09-22 13:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Automations, CLI, Cloud Agents, IDE

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-22 01:07 UTC

   We are investigating degraded performance for requests that use Grok models. Users may see failed or retried requests in Automations, Cloud Agents, the CLI, and the IDE when Grok models are used. Other models are unaffected.

2. resolved 2026-09-22 01:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Automations, CLI, Cloud Agents, IDE

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-21 06:39 UTC

   We are investigating degraded performance for requests that use Grok 4.6. Users may see failed or retried requests in Automations, Cloud Agents, the CLI, and the IDE when Grok 4.6 is used. Other models are unaffected.

2. resolved 2026-09-21 07:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: cursor.com

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-18 23:02 UTC

   We are investigating an issue affecting sign-in. Signing in, signing out, and loading the dashboard may hang or fail. If you are already signed in, your session should continue to work normally. We will provide another update shortly.

2. monitoring 2026-09-18 23:07 UTC

   Sign-in is recovering. The issue came from our authentication provider, who has identified the cause and is seeing recovery on their side. We are monitoring to confirm everything is back to normal.

3. resolved 2026-09-18 23:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Grok Bot

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-18 17:19 UTC

   We are investigating a service degradation affecting Grok Bot.

2. identified 2026-09-18 19:01 UTC

   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.

3. monitoring 2026-09-18 19:53 UTC

   A fix has been implemented and we are monitoring for service restoration. Grok Bot should be responding normally again.

4. resolved 2026-09-18 23:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Grok Bot

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-18 11:37 UTC

   We are investigating a service degradation affecting Grok Bot. Users may experience degraded performance or bots that don't respond.

2. resolved 2026-09-18 14:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Automations, Review Agents, Cloud Agents, Grok Bot

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-17 15:20 UTC

   We are investigating a service degradation affecting Cloud Agents and Automations

2. investigating 2026-09-17 15:50 UTC

   We are currently investigating this issue. We will provide updates as more information becomes available.

3. investigating 2026-09-17 15:58 UTC

   We are continuing to investigate this issue.

4. investigating 2026-09-17 17:31 UTC

   We are continuing to investigate this issue. Cloud Agents, Automations, and Review Agents (resulting from Cloud Agents) are affected. Bugbot is not affected.

5. investigating 2026-09-17 18:02 UTC

   Affected services are back to normal operation. Our team continues to monitor everything closely.

6. monitoring 2026-09-17 18:12 UTC

   A fix has been implemented and we are monitoring for service restoration.

7. resolved 2026-09-17 20:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Grok Bot

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-17 12:30 UTC

   We are investigating a service degradation affecting Grok Bot. Users may experience degraded performance or bots that don't respond.

2. resolved 2026-09-17 14:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Grok Bot

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-16 14:27 UTC

   We are investigating a service degradation affecting Grok Bot. Users may experience degraded performance or bots that don't respond.

2. identified 2026-09-16 19:51 UTC

   The root cause has been identified and a fix is being implemented.

3. resolved 2026-09-16 20:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: CLI, IDE

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-16 08:03 UTC

   We are investigating elevated error rates affecting xAI models in the Cursor IDE and CLI. Some Agent requests may fail.

2. monitoring 2026-09-16 08:09 UTC

   A fix has been implemented. We are monitoring recovery and will provide another update once the incident is fully resolved.

3. resolved 2026-09-16 08:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Automations, Review Agents, CLI, Cloud Agents, IDE, Origin, Grok Bot

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-15 21:26 UTC

   We are investigating a service degradation. Affected agent surfaces: Composer and xAI.

2. monitoring 2026-09-15 21:38 UTC

   A fix has been implemented and we are monitoring for service restoration.

3. monitoring 2026-09-15 21:41 UTC

   A fix has been implemented and we are monitoring for service restoration. Only Grok 4.6 (non-fast) is affected in Cursor.

4. resolved 2026-09-15 22:00 UTC

   This incident has been resolved at 6pm Eastern.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Automations, CLI, Cloud Agents, IDE

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-14 08:14 UTC

   We are investigating a service degradation affecting Grok 4.6.

2. monitoring 2026-09-14 08:15 UTC

   We are monitoring Grok 4.6 for service restoration.

3. resolved 2026-09-14 09:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Automations, CLI, Cloud Agents, IDE

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: OpenAI.

1. investigating 2026-09-11 11:08 UTC

   We are investigating a service degradation. Affected agent surfaces: OpenAI models.

2. resolved 2026-09-11 11:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Review Agents, Cloud Agents

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-10 17:07 UTC

   We are investigating a service degradation affecting Review Agents and Cloud Agents. Cloud Agents using "Privacy Mode" may experience errors and start delays. For Review Agents, Security Agents and PR Approval agents are impacted.

2. resolved 2026-09-10 17:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Grok Bot

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-07 20:32 UTC

   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.

2. identified 2026-09-07 20:33 UTC

   The root cause has been identified and a fix is being implemented.

3. monitoring 2026-09-07 20:41 UTC

   A fix has been implemented and we are monitoring for service restoration.

4. resolved 2026-09-07 21:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-09-07 13:08 UTC

   Between 12:12 and 13:08 UTC on September 7, 2026, some users may have experienced login or account-related errors. This incident has been resolved. All services have returned to normal operation.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Grok Bot

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-03 23:42 UTC

   We are investigating a service degradation affecting Grok Bot. Some trigger fires may be dropped.

2. identified 2026-09-04 00:13 UTC

   The root cause has been identified and a fix is being implemented.

3. resolved 2026-09-04 00:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: CLI, Cloud Agents, IDE, Grok Bot

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-03 17:42 UTC

   We are investigating a service degradation affecting Grok 4.6

2. monitoring 2026-09-03 18:57 UTC

   A fix has been implemented and we are monitoring for service restoration.

3. resolved 2026-09-03 19:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Automations, CLI, Cloud Agents, IDE

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: OpenAI.

1. investigating 2026-09-03 15:17 UTC

   An upstream OpenAI issue is causing elevated errors for ChatGPT. Some users may experience errors or failed Agent turns. We're monitoring recovery and will provide updates.

2. resolved 2026-09-03 17:05 UTC

   Elevated errors affecting OpenAI models have been resolved. Service has been restored.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Automations, CLI, Cloud Agents, IDE

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Anthropic (Claude).

Started during Anthropic (Claude): Elevated errors for multiple models.

1. investigating 2026-09-03 14:17 UTC

   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.

2. investigating 2026-09-03 15:55 UTC

   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.

3. resolved 2026-09-03 16:31 UTC

   Elevated errors affecting Anthropic models have been resolved. Service has been restored.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Automations, Review Agents, Cloud Agents, IDE, Grok Bot

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-03 13:41 UTC

   We are investigating a service degradation affecting All Grok Models, Automations, Cloud Agents, Grok Bot and Review Agents

2. identified 2026-09-03 15:33 UTC

   We have identified the cause and are actively working on a mitigation.

3. resolved 2026-09-03 17:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Automations, Review Agents, Cloud Agents

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-02 14:50 UTC

   We are investigating a service degradation affecting Automations, Cloud Agents, and Review Agents where they are failing to start.

2. resolved 2026-09-02 16:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Automations, CLI, Cloud Agents, IDE

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-02 00:48 UTC

   We're currently investigating degraded performance affecting requests made with Composer 2.5 and Grok 4.6 Fast. While these models are in use, you may encounter failed or retried requests across Automations, Cloud Agents, the CLI, and the IDE. Other models are unaffected.

2. monitoring 2026-09-02 01:00 UTC

   A fix has been implemented and we are monitoring for service restoration.

3. resolved 2026-09-02 03:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: CLI, Cloud Agents, IDE, Grok Bot

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-01 16:42 UTC

   We are investigating a service degradation affecting Grok 4.5

2. monitoring 2026-09-01 17:14 UTC

   A fix has been implemented and we are monitoring for service restoration.

3. resolved 2026-09-01 18:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.

Affected: Automations, CLI, Cloud Agents, IDE

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-01 01:01 UTC

   We are investigating degraded performance for requests that use Composer 2.5. Users may see failed or retried requests in Automations, Cloud Agents, the CLI, and the IDE when Composer 2.5 is used. Other models are unaffected.

2. resolved 2026-09-01 01:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cursor's status page.