Cursor Outage History

Cursor experienced degraded behavior in its MCP Allowlist & Blocklist features on version 3.0 for 6.4 hours. The issue was identified and a fix was implemented before the incident was resolved.

Cursor experienced degraded performance for Cloud Agents for 6 minutes on April 2nd, 2026. The service team investigated and resolved the issue within the same timeframe. No specific details about the nature of the performance degradation or affected user operations were provided.

Cursor experienced degraded performance affecting Anthropic 4.6 models for 3.6 hours. The service team identified the root cause and implemented a fix. The incident has been fully resolved.

Cursor experienced degraded performance affecting its analytics functionality for 42 minutes. The service team investigated and resolved the issue. The incident was classified as minor with no major service disruption.

Cursor experienced a marketplace indexing issue that affected some teams for 26 minutes. The stale indexing prevented certain teams from accessing up-to-date marketplace content. The issue was investigated and resolved within the same timeframe.

Cursor experienced degraded performance for Anthropic models for 3.8 hours. The service team investigated the issue and successfully resolved it. No specific details about the scope of impact or resolution method were provided.

Cursor experienced degraded performance for Cloud Agent initialization for 3.6 hours. The service team investigated the issue and successfully resolved it. No specific details about user impact or affected functionality were provided during the incident.

Cursor experienced elevated latencies with their Bugbot service for 3.4 hours. The incident was classified as minor and has been resolved. The service team investigated and successfully addressed the latency issues.

Cursor experienced service degradation affecting some users for 4.1 hours. The team identified the root cause and worked to gradually restore services, prioritizing agent workloads during recovery. The incident was fully resolved with all functionality restored.

Cursor experienced increased errors with the Opus 4.6 model from their model provider, resulting in a minor service disruption. The issue affected users' ability to properly utilize the Opus 4.6 model functionality. The incident was resolved after 3.2 hours of investigation and remediation efforts.