Cursor Outage History

Cursor's Composer 2.5 Fast service experienced degraded performance for 4.6 hours on May 27, 2026. The service was restored after implementing a fix and monitoring confirmed stabilization. The incident was fully resolved with normal service behavior restored.

Cursor experienced a major service degradation affecting Composer 2 performance for 18 minutes. The incident was resolved after investigation and monitoring. Users experienced degraded functionality during this period before normal service was restored.

Cursor experienced a service degradation affecting Composer 2.5 availability for 7 minutes. The incident was quickly identified and investigated by the team. The service was fully restored and the incident resolved.

Cursor experienced a service degradation affecting AI features, including Agent mode, for 17 minutes on May 27th. The incident was classified as minor and has been resolved. Users would have experienced reduced functionality or performance issues with AI-powered features during this timeframe.

Cursor experienced a service degradation that affected Gemini 2.5 Flash functionality and user summarization features. The incident lasted approximately 1.1 hours before being fully resolved. The team investigated and restored normal service operations.

Cursor experienced degraded performance affecting Agent sessions in the IDE for 4.2 hours. The service degradation impacted users' ability to use AI agents within the development environment. The issue was resolved after implementing a fix and monitoring for service restoration.

Cursor experienced a service degradation affecting Composer 2.5 Fast functionality. The incident was classified as minor and lasted approximately 1.2 hours. The service degradation was investigated and fully resolved.

Cursor's Composer 2.5 Fast service experienced degradation for 41 minutes. The service degradation was investigated and resolved without further details on the specific impact or root cause.

Cursor experienced degraded agent performance affecting Composer 2.5 and Auto requests for 3.2 hours. The service degradation impacted users' ability to use these specific features normally. The root cause was identified and a fix was implemented, with the incident fully resolved after monitoring confirmed service restoration.

Cursor experienced a service degradation affecting Opus 4.7 functionality for 20 minutes. The incident was resolved after investigation and monitoring. Users experienced degraded performance during this period before normal service was restored.