Cursor Outage History

Cursor experienced service degradation for 32 minutes, with users reporting "Service Unavailable" issues. The incident was resolved after investigation and monitoring.

Cursor experienced a service degradation that made all modes (Ask, Chat, Agent, etc.) unavailable, with users encountering errors on every request. The incident lasted 14 minutes before being resolved. All functionality was restored after the investigation and fix were completed.

Cursor experienced elevated automation error rates affecting their Cloud Agent service for 9 minutes. The incident was classified as minor and has been resolved. The service team investigated and fixed the issue within the brief timeframe.

Cursor experienced a major service degradation where the Slack integration failed to trigger Cloud Agents when users mentioned `@Cursor` in Slack channels. The issue affected users' ability to invoke Cursor's AI assistance through Slack commands. The incident was resolved after 11 minutes of investigation.

Cursor's Cloud Agents experienced a major service degradation for 23 minutes due to a GitHub outage. Some Cloud Agents failed to start because they couldn't clone repositories from GitHub due to upstream errors. The incident was resolved once GitHub's service was restored.

Cursor experienced degraded performance for its Auto feature for 27 minutes. The service team investigated and resolved the issue. No specific user impact details were provided beyond the performance degradation.

Cursor's Bugbot and Cloud Agents experienced a major service degradation for 1.7 hours due to rate limits in their GitHub integration caused by heavy traffic. Users encountered provider connection errors when trying to access the AI model services, with error messages indicating temporary connectivity issues. The incident was resolved after implementing mitigations to address the GitHub integration rate limiting.

Cursor's authentication systems experienced degraded performance for 1.9 hours, preventing or impacting user login capabilities. The engineering team identified the issue, implemented mitigations to restore service functionality, and monitored the recovery process. The incident was fully resolved with normal authentication service resuming.