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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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: A model or AI component. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-27 19:38 UTC

   This incident has been resolved. Sign-in to Cursor has returned to normal operation.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-27 15:05 UTC

   This incident has been resolved.

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

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-25 21:28 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-25 17:36 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-24 16:33 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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-08-24 08:51 UTC

   This incident has been resolved. More information: https://status.claude.com/

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-20 01:51 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-19 15:54 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: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Names an upstream provider: GitHub.

1. resolved 2026-08-19 02:43 UTC

   The incident affecting GitHub-connected workflows in Cloud Agents has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-18 20:15 UTC

   This incident has been resolved. Affected Grok Bot sessions have been restored, and connectors are operating normally.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-18 11:45 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-18 08:50 UTC

   This incident has been resolved.

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

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-17 22:57 UTC

   This incident has been resolved. Grok 4.6 requests, including API traffic, have returned to normal.

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

Names an upstream provider: GitHub.

Started during GitHub: Incident with GitHub.com.

1. resolved 2026-08-17 20:40 UTC

   The affected Cursor services have recovered. We’re resolving this incident and will continue monitoring service health.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-08-17 13:40 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-13 18:49 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-12 05:29 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-08-12 04:11 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-11 23:38 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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-08-07 18:50 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-06 20:27 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-05 18:47 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-05 14:36 UTC

   This incident has been resolved. Mythos 5, Fable 5, Opus 5 and Sonnet 5 inference has returned to normal.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-05 00:01 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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

   This incident has been resolved. All services have returned to normal operation.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-30 09:48 UTC

   This incident has been resolved. Fable 5 and Opus 5 inference has returned to normal.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-30 06:33 UTC

   This incident has been resolved. Claude inference has returned to normal.

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: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

Names an upstream provider: Anthropic (Claude).

Started during Anthropic (Claude): Elevated errors across all models.

1. resolved 2026-07-29 23:15 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.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-29 11:38 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-28 18:24 UTC

   This incident has been resolved.

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

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-28 10:19 UTC

   This incident has been resolved. GPT-5.4 was temporarily slightly degraded.

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

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-28 00:45 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-27 19:39 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-27 11:41 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-27 09:50 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-23 16:36 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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

Names an upstream provider: Anthropic (Claude).

Started during Anthropic (Claude): Elevated errors on several models.

Started during Anthropic (Claude): Elevated errors on Haiku 4.5.

1. resolved 2026-07-21 18:53 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-20 12:23 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-07-20 02:19 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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

Names an upstream provider: Anthropic (Claude).

Started during Anthropic (Claude): Elevated errors on Sonnet 5 and Haiku 4.5.

1. resolved 2026-07-17 12:27 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-07-17 00:15 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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-16 10:46 UTC

   This incident has been resolved.

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

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-16 09:36 UTC

   This incident has been resolved.

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

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: A model or AI component. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-16 06:15 UTC

   This has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-15 11:31 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-15 11:32 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-14 20:10 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-15 09:11 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-13 07:58 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-13 07:37 UTC

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

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-08 14:38 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-08 14:58 UTC

   This incident has been resolved. Usage should display correctly in the dashboard.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Names an upstream provider: Anthropic (Claude).

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

1. resolved 2026-07-07 22:25 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-06 11:02 UTC

   This incident has been resolved.

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

Names an upstream provider: Anthropic (Claude).

Started during Anthropic (Claude): Elevated error rate across multiple models.

1. resolved 2026-06-23 16:47 UTC

   This incident has been resolved.

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

1. resolved 2026-06-22 04:53 UTC

   This incident has been resolved.

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

1. resolved 2026-06-17 17:19 UTC

   This incident has been resolved.

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

1. resolved 2026-06-17 10:20 UTC

   This incident has been resolved.

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

Names an upstream provider: Anthropic (Claude).

Started during Anthropic (Claude): Elevated errors across many models.

1. resolved 2026-06-16 19:41 UTC

   This incident has been resolved.

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

1. resolved 2026-06-16 13:38 UTC

   This incident has been resolved.

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

1. resolved 2026-06-10 19:46 UTC

   This incident has been resolved.

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

1. resolved 2026-06-10 18:14 UTC

   This incident has been resolved.

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

1. resolved 2026-06-09 01:31 UTC

   This incident has been resolved.

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

1. resolved 2026-06-02 18:42 UTC

   This incident has been resolved.

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

1. resolved 2026-05-30 07:09 UTC

   This incident has been resolved.

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

1. resolved 2026-05-27 20:12 UTC

   This incident has been resolved.

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

1. resolved 2026-05-27 11:49 UTC

   This incident has been resolved.

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

1. resolved 2026-05-27 09:26 UTC

   This incident has been resolved.

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

1. resolved 2026-05-27 06:54 UTC

   This incident has been resolved.

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

1. resolved 2026-05-26 19:07 UTC

   This incident has been resolved.

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

1. resolved 2026-05-26 07:11 UTC

   This incident has been resolved.

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

1. resolved 2026-05-24 18:49 UTC

   This incident has been resolved.

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

1. resolved 2026-05-24 17:26 UTC

   This incident has been resolved.

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

1. resolved 2026-05-21 15:31 UTC

   This incident has been resolved.

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

1. resolved 2026-05-20 15:26 UTC

   This incident has been resolved.

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

1. resolved 2026-05-19 21:09 UTC

   This incident has been resolved.

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

1. resolved 2026-05-19 03:36 UTC

   This incident has been resolved.

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

1. resolved 2026-05-19 05:15 UTC

   This incident has been resolved.

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

Names an upstream provider: Anthropic (Claude).

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

1. resolved 2026-05-18 22:26 UTC

   This incident has been resolved.

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

1. resolved 2026-05-15 01:43 UTC

   This incident has been resolved.

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

1. resolved 2026-05-13 17:26 UTC

   This incident has been resolved.

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

1. resolved 2026-05-12 02:38 UTC

   This incident has been resolved.

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

1. resolved 2026-05-11 14:44 UTC

   This incident has been resolved.

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

1. resolved 2026-05-09 00:22 UTC

   This incident has been resolved.

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

Names an upstream provider: OpenAI.

1. resolved 2026-05-08 14:58 UTC

   This incident has been resolved.

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

1. resolved 2026-05-08 02:14 UTC

   This incident has been resolved.

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

1. resolved 2026-05-06 18:23 UTC

   This incident has been resolved.

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

1. resolved 2026-05-05 17:41 UTC

   This incident has been resolved.

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

1. resolved 2026-05-05 00:33 UTC

   This incident has been resolved.

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

Names an upstream provider: Anthropic (Claude).

1. resolved 2026-04-29 18:29 UTC

   This incident has been resolved.

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

1. resolved 2026-04-23 15:41 UTC

   This incident has been resolved.

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

1. resolved 2026-04-23 04:37 UTC

   This incident has been resolved.

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

Names an upstream provider: OpenAI.

1. resolved 2026-04-16 19:43 UTC

   This incident has been resolved.

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

1. resolved 2026-04-16 12:37 UTC

   This incident has been resolved.

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

1. resolved 2026-04-15 20:19 UTC

   This incident has been resolved.

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

1. resolved 2026-04-15 16:19 UTC

   This incident has been resolved.

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

1. resolved 2026-04-14 02:19 UTC

   This incident has been resolved.

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

1. resolved 2026-04-13 23:38 UTC

   This incident has been resolved.

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

1. resolved 2026-04-09 21:37 UTC

   This incident has been resolved.

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

1. resolved 2026-04-08 22:23 UTC

   This incident has been resolved.

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

1. resolved 2026-04-08 22:09 UTC

   This incident has been resolved.

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

1. resolved 2026-04-08 00:40 UTC

   This incident has been resolved.

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

Names an upstream provider: Anthropic (Claude).

Started during Anthropic (Claude): Elevated errors on Claude.ai.

1. resolved 2026-04-06 17:13 UTC

   This incident has been resolved.

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

Names an upstream provider: OpenAI.

1. resolved 2026-04-03 18:31 UTC

   This incident has been resolved.

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

1. resolved 2026-04-03 01:15 UTC

   This incident has been resolved.

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

1. resolved 2026-04-02 18:37 UTC

   This incident has been resolved.

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

1. resolved 2026-04-02 18:37 UTC

   This incident has been resolved.

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

Names an upstream provider: Anthropic (Claude).

1. resolved 2026-04-01 19:18 UTC

   This incident has been resolved.

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

1. resolved 2026-03-30 20:18 UTC

   This incident has been resolved.

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

1. resolved 2026-03-30 20:18 UTC

   This incident has been resolved.

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

1. resolved 2026-03-30 18:55 UTC

   This incident has been resolved.

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

Names an upstream provider: Anthropic (Claude).

1. resolved 2026-03-30 17:46 UTC

   This incident has been resolved.

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

1. resolved 2026-03-27 21:45 UTC

   This incident has been resolved.

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

1. resolved 2026-03-27 20:59 UTC

   This incident has been resolved.

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

1. resolved 2026-03-27 21:59 UTC

   This incident has been resolved.

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

1. resolved 2026-03-24 22:32 UTC

   This incident has been resolved.

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

1. resolved 2026-03-21 03:33 UTC

   This incident has been resolved.

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

1. resolved 2026-03-21 03:41 UTC

   This incident has been resolved.

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

1. resolved 2026-03-19 10:30 UTC

   This incident has been resolved.

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

1. resolved 2026-03-17 20:42 UTC

   This incident has been resolved.

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

1. resolved 2026-03-17 23:07 UTC

   This incident has been resolved.

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

1. resolved 2026-03-06 09:22 UTC

   This incident has been resolved.

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

1. resolved 2026-03-06 09:16 UTC

   This incident has been resolved.

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

1. resolved 2026-03-06 08:44 UTC

   This incident has been resolved.

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

1. resolved 2026-03-05 20:30 UTC

   This is now resolved

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

1. resolved 2026-03-05 20:48 UTC

   This incident has been resolved.

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

Names an upstream provider: GitHub.

Started during GitHub: Incident with all GitHub services.

1. resolved 2026-03-03 20:04 UTC

   This incident has been resolved.

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

1. resolved 2026-03-01 02:53 UTC

   This incident has been resolved.

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

1. resolved 2026-02-28 02:53 UTC

   This incident has been resolved.

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

1. resolved 2026-02-27 02:44 UTC

   This incident has been resolved.

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

1. resolved 2026-02-25 00:01 UTC

   This incident has been resolved.

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

1. resolved 2026-02-24 11:46 UTC

   This incident has been resolved.

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

1. resolved 2026-02-24 11:28 UTC

   This incident has been resolved.

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

1. resolved 2026-02-24 11:47 UTC

   This incident has been resolved.

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

1. resolved 2026-02-20 19:08 UTC

   This incident has been resolved.

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

Names an upstream provider: Anthropic (Claude).

Started during Anthropic (Claude): Elevated error rates across multiple models.

Started during Anthropic (Claude): Elevated errors on Claude Sonnet 4.6.

Started during Anthropic (Claude): Intermittent errors in skills-related functionality.

1. resolved 2026-02-18 17:24 UTC

   This incident has been resolved.

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

1. resolved 2026-02-17 19:35 UTC

   This incident has been resolved.

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

1. resolved 2026-02-11 18:52 UTC

   This incident has been resolved.

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

1. resolved 2026-02-11 03:15 UTC

   This incident has been resolved.

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

1. resolved 2026-02-10 19:36 UTC

   This incident has been resolved.

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

1. resolved 2026-02-10 17:10 UTC

   This incident has been resolved.

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

1. resolved 2026-02-10 19:36 UTC

   This incident has been resolved.

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

1. resolved 2026-02-09 20:23 UTC

   This incident has been resolved.

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

1. resolved 2026-02-09 20:23 UTC

   This incident has been resolved.

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

1. resolved 2026-02-09 18:36 UTC

   This incident has been resolved.

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

Names an upstream provider: Anthropic (Claude).

Started during Anthropic (Claude): Elevated errors on Claude models.

1. resolved 2026-02-07 16:33 UTC

   This incident has been resolved.

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

Names an upstream provider: Anthropic (Claude).

Started during Anthropic (Claude): Elevated errors on Claude models.

1. resolved 2026-02-04 17:21 UTC

   This incident has been resolved.

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

1. resolved 2026-01-30 02:50 UTC

   This incident has been resolved.

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

1. resolved 2026-01-22 22:34 UTC

   This incident has been resolved.

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

1. resolved 2026-01-20 21:54 UTC

   This incident has been resolved.

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

Names an upstream provider: GitHub.

Started during GitHub: Incident with Issues and Pull Requests.

1. resolved 2026-01-15 17:55 UTC

   GitHub API error rates have recovered

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

1. resolved 2026-01-14 16:16 UTC

   This incident has been resolved.

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

1. resolved 2026-01-13 08:17 UTC

   This incident has been resolved.

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

1. resolved 2026-01-12 20:35 UTC

   This incident has been resolved.

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

1. resolved 2026-01-12 20:37 UTC

   This incident has been resolved.

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

1. resolved 2026-01-02 20:34 UTC

   This incident has been resolved.

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

1. resolved 2025-12-22 21:48 UTC

   This incident has been resolved.

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

1. resolved 2025-12-16 02:28 UTC

   We have resolved the issues with Cursor Tab and are seeing full recovery.

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

1. resolved 2025-12-15 21:51 UTC

   This incident has been resolved.

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

1. resolved 2025-12-15 21:17 UTC

   This incident has been resolved.

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

1. resolved 2025-12-10 17:58 UTC

   This incident has been resolved.

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

Names an upstream provider: Cloudflare.

1. resolved 2025-12-05 09:27 UTC

   This incident has been resolved.

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

1. resolved 2025-11-25 22:22 UTC

   This incident has been resolved.

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

1. resolved 2025-11-18 22:20 UTC

   This incident has been resolved.

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

Names an upstream provider: Cloudflare.

1. resolved 2025-11-18 16:12 UTC

   We experienced service degradation affecting Authentication and other services due to a Cloudflare issue. The Cloudflare degradation has been resolved, and full system functionality is now restored.

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

1. resolved 2025-11-06 06:44 UTC

   This incident has been resolved.

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

1. resolved 2025-10-29 19:54 UTC

   This incident has been resolved.

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

1. resolved 2025-10-29 02:33 UTC

   This incident has been resolved.

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

1. resolved 2025-10-27 22:32 UTC

   A fix has been implemented, and we are seeing services return to full functionality. We apologize for any inconvenience caused during this incident.

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

1. resolved 2025-10-22 22:00 UTC

   The incident is now resolved.

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

1. resolved 2025-10-22 16:23 UTC

   This incident has been resolved.

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

Names an upstream provider: AWS.

1. resolved 2025-10-21 02:38 UTC

   This incident has been resolved.

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

Names an upstream provider: AWS.

1. resolved 2025-10-20 09:37 UTC

   Cursor services appear to be resolved, with reliability back to normal levels. The team will continue to monitor for any further degredation, but all Cursor services should be fully functional.

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

1. resolved 2025-10-16 10:54 UTC

   This incident has been resolved.

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

1. resolved 2025-10-15 20:10 UTC

   This incident has been resolved.

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

1. resolved 2025-10-15 18:47 UTC

   The service degredation regarding Stripe-related services, such as the Cursor dashboard and checkout functionality, is now resolved. For any further billing / checkout issues, please contact the team via hi@cursor.com

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

1. resolved 2025-10-13 11:37 UTC

   This incident has been resolved.

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

1. resolved 2025-10-10 16:37 UTC

   This incident has been resolved.

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

Names an upstream provider: GitHub.

Started during GitHub: Incident with Webhooks.

1. resolved 2025-10-09 18:31 UTC

   This incident has been resolved.

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

Names an upstream provider: GitHub.

Started during GitHub: Multiple GitHub API endpoints are experiencing errors.

1. resolved 2025-10-09 13:58 UTC

   This incident has been resolved.

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

1. resolved 2025-10-07 15:58 UTC

   This incident has been resolved.

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

1. resolved 2025-09-26 23:48 UTC

   This incident has been resolved.

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

1. resolved 2025-09-23 16:30 UTC

   This incident has been resolved.

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

1. resolved 2025-09-19 00:36 UTC

   This incident has been resolved.

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

1. resolved 2025-09-18 01:20 UTC

   This incident has been resolved.

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

1. resolved 2025-09-17 18:30 UTC

   This incident has been resolved.

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

Names an upstream provider: Anthropic (Claude).

Started during Anthropic (Claude): API, Claude.ai, and Console services impacted.

1. resolved 2025-09-10 19:23 UTC

   This incident has been resolved.

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

1. resolved 2025-09-10 05:16 UTC

   This incident has been resolved.

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

1. resolved 2025-09-09 17:30 UTC

   This incident has been resolved.

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

1. resolved 2025-09-08 15:59 UTC

   This incident has been resolved.

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

1. resolved 2025-09-03 16:00 UTC

   This incident has been resolved.

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

1. resolved 2025-09-03 01:44 UTC

   This incident has been resolved.

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

1. resolved 2025-09-02 18:50 UTC

   This incident has been resolved.

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

1. resolved 2025-09-01 08:56 UTC

   This incident has been resolved.

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

1. resolved 2025-08-29 05:20 UTC

   This incident has been resolved.

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

1. resolved 2025-08-28 03:54 UTC

   This incident has been resolved.

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

1. resolved 2025-08-27 20:19 UTC

   This incident has been resolved.

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

1. resolved 2025-08-26 01:40 UTC

   This incident has been resolved.

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

1. resolved 2025-08-21 20:01 UTC

   This incident has been resolved.

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

1. resolved 2025-08-20 20:34 UTC

   This incident has been resolved.

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

1. resolved 2025-08-16 03:25 UTC

   This incident has been resolved.

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

1. resolved 2025-08-16 06:16 UTC

   This incident has been resolved.

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

1. resolved 2025-08-14 20:20 UTC

   This incident has been resolved.

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

1. resolved 2025-08-14 08:35 UTC

   This incident has been resolved.

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

1. resolved 2025-08-07 18:50 UTC

   This incident has been resolved.

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

1. resolved 2025-08-07 15:27 UTC

   This incident has been resolved.

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

Names an upstream provider: GitHub.

Started during GitHub: Incident with pull requests.

1. resolved 2025-08-05 16:50 UTC

   This incident has been resolved.

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

1. resolved 2025-08-04 21:41 UTC

   This incident has been resolved.

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

1. resolved 2025-08-04 20:45 UTC

   This incident has been resolved.

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

1. resolved 2025-08-02 06:50 UTC

   The team has deployed a fix and all services have been restored to normal functionality.

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

1. resolved 2025-08-01 16:16 UTC

   This incident has been resolved.

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

1. resolved 2025-07-29 01:24 UTC

   This incident has been resolved.

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

1. resolved 2025-07-25 16:16 UTC

   This incident has been resolved.

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

1. resolved 2025-07-25 06:59 UTC

   This incident has been resolved.

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

1. resolved 2025-07-25 00:10 UTC

   This incident has been resolved.

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

1. resolved 2025-07-24 21:37 UTC

   This incident has been resolved.

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

1. resolved 2025-07-24 01:44 UTC

   This incident has been resolved.

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

1. resolved 2025-07-23 18:36 UTC

   This incident has been resolved.

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

Names an upstream provider: Anthropic (Claude), GitHub.

Started during GitHub: Some Copilot Models Experiencing Degraded Performance.

Started during GitHub: Incident with Issues.

Started during Anthropic (Claude): Elevated errors on Claude 4 Sonnet.

1. resolved 2025-07-21 10:03 UTC

   GitHub and Anthropic services are returning to normal function. BugBot and Background Agent should be fully functional.

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

Names an upstream provider: Anthropic (Claude).

Started during Anthropic (Claude): Elevated errors for requests to Claude Sonnet and Opus models.

1. resolved 2025-07-17 21:54 UTC

   This incident has been resolved.

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

Names an upstream provider: OpenAI.

1. resolved 2025-07-17 11:06 UTC

   This incident has been resolved.

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

1. resolved 2025-07-17 08:32 UTC

   This incident has been resolved.

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

1. resolved 2025-07-17 06:55 UTC

   This incident has been resolved.

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

1. resolved 2025-07-16 21:10 UTC

   This incident has been resolved.

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

Names an upstream provider: Cloudflare.

1. resolved 2025-07-15 01:38 UTC

   The upstream issue with Cloudflare DNS has been resolved.

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

1. resolved 2025-07-14 21:05 UTC

   This incident has been resolved.

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

1. resolved 2025-07-10 17:57 UTC

   This incident has been resolved.

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

1. resolved 2025-07-08 12:28 UTC

   This incident has been resolved.

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

1. resolved 2025-07-04 20:28 UTC

   This incident has been resolved.

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

1. resolved 2025-07-03 19:40 UTC

   This incident has been resolved.

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

Names an upstream provider: GitHub.

1. resolved 2025-06-30 20:52 UTC

   Background Agents on Web, and it's related GitHub features, should now be fully accessible again.

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

1. resolved 2025-06-30 12:07 UTC

   The issue is now resolved and Anysphere-published extensions are available in-app again.

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

1. resolved 2025-06-29 10:18 UTC

   The system has remained stable, and all functionality remains fully restored.

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

Names an upstream provider: OpenAI.

1. resolved 2025-06-24 20:46 UTC

   OpenAI have confirmed the incident is resolved, and OpenAI models are restored to full availability within Cursor.

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

1. resolved 2025-06-23 22:50 UTC

   This incident has been resolved.

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

1. resolved 2025-06-22 07:27 UTC

   This incident has been resolved.

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

1. resolved 2025-06-19 08:50 UTC

   We have now implemented a mitigation for this issue, and all services should be back to standard operation. We apologise for any inconvenience caused during this brief period of degradation.

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

Names an upstream provider: Google Cloud.

1. resolved 2025-06-12 21:00 UTC

   This incident has been resolved.

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

1. resolved 2025-05-12 10:29 UTC

   This incident has been resolved.

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

1. resolved 2025-04-30 01:07 UTC

   These changes are now finished, and the forum should be back to full functionality!

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

1. resolved 2025-04-24 06:11 UTC

   This incident has been resolved.

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

1. resolved 2025-04-21 23:07 UTC

   Work is now complete, and the forum is now back to full functionality.

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

1. resolved 2025-04-05 13:51 UTC

   Fireworks have now resolved the issue with DeepSeek v3, and functionality should now be restored.

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

1. resolved 2025-04-03 22:44 UTC

   Cursor unfortunately suffered a brief period of decreased performance for ~14 minutes, affecting the Chat's responsiveness and error rate. This is now resolved, and we apologise for any inconvenience caused.

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

Names an upstream provider: Anthropic (Claude).

Started during Anthropic (Claude): Elevated Errors On API And Claude.ai.

1. resolved 2025-04-03 21:37 UTC

   Due to issues with Anthropic, the Claude family of models was experiencing elevated errors for ~10 minutes. This has since been resolved, but more information can be found here: https://status.anthropic.com/incidents/s0c6w5gmlcq3

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

1. resolved 2025-04-01 09:15 UTC

   Codebase indexing should now be fully operational for all users. We are monitoring the situation to ensure no further degradation occurs.

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

1. resolved 2025-03-28 20:27 UTC

   The forum is now back online, apologies for any inconvenience!

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

1. resolved 2025-03-28 05:38 UTC

   This incident has been resolved.

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

1. resolved 2025-03-28 05:33 UTC

   The infrastructure issues are now resolved, and Cursor services should be returning to normal shortly.

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

Names an upstream provider: Anthropic (Claude).

Started during Anthropic (Claude): Claude.ai, Console, and API not available.

1. resolved 2025-03-18 11:32 UTC

   Anthropic have now issued a fix for this issue, and Claude model availability should return to normal shortly.

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

Names an upstream provider: Anthropic (Claude).

Started during Anthropic (Claude): Elevated errors for requests to Claude 3.7 Sonnet.

1. resolved 2025-03-14 22:15 UTC

   This incident has been resolved.

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

1. resolved 2025-02-25 19:48 UTC

   Stripe syncing should now be resolved, and accounts should be up to date shortly.

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

Names an upstream provider: Anthropic (Claude).

Started during Anthropic (Claude): Elevated errors for requests to Claude 3.5 June Sonnet.

1. resolved 2025-02-28 20:59 UTC

   We have implemented a series of mitigations, and should start to see usage return to normal. For any further issues, let us know at forum.cursor.com

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

1. resolved 2025-01-29 14:24 UTC

   Tab is now returning back to full functionality. For any further issues, please post on forum.cursor.com.

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

1. resolved 2025-01-24 05:53 UTC

   This incident has been resolved.

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

Names an upstream provider: OpenAI.

1. resolved 2025-01-21 20:00 UTC

   OpenAI have deployed and are monitoring a fix, but we are confident Cursor's codebase indexing has returned to full functionality. For any further issues, please post on forum.cursor.com

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

Names an upstream provider: OpenAI.

1. resolved 2025-01-21 10:45 UTC

   OpenAI has resolved the degradation with the Embeddings API, and the affected features are now functional.

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

1. resolved 2025-01-07 02:18 UTC

   This incident has been resolved.

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

Names an upstream provider: OpenAI.

1. resolved 2024-12-12 05:00 UTC

   OpenAI has resolved the issue.

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

1. resolved 2024-12-10 23:00 UTC

   This incident has been resolved.

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

1. resolved 2024-11-26 12:09 UTC

   We have implemented changes which should resolve the issues, and all services should return to full functionality. We apologise for any inconvenience caused by this degradation in service.

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

1. resolved 2024-11-18 21:38 UTC

   Increased error rates for Chat

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

1. resolved 2024-11-19 07:45 UTC

   This incident has been resolved.

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