Cursor incident: Increased error rates for Composer 2.5

Affected components

• Automations
• CLI
• Cloud Agents
• IDE
• cursor.com

1. resolvedAug 19, 2026, 15:54 UTC

   This incident has been resolved.

2. monitoringAug 19, 2026, 14:26 UTC

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

3. identifiedAug 19, 2026, 14:20 UTC

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

4. investigatingAug 19, 2026, 12:52 UTC

   We are investigating a service degradation affecting Composer 2.5 (non-fast). Users may experience errors when making requests using this model.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Cursor's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• DigitalOcean: Major Service Interruption in MKC1Critical · Aug 19, 2026, 11:10 UTC
• Elasticsearch: Elasticsearch 9.5.1: false-positive matches in certain boolean queriesMajor · Aug 14, 2026, 09:22 UTC
• Telnyx: AI Assistants with Data Locality Australia FailingMajor · Aug 19, 2026, 14:28 UTC
• Supabase: 401 errors due to JWT rejectionsMinor · Aug 14, 2026, 02:23 UTC
• Telnyx: Programmable Wireless data loss in AustraliaMinor · Aug 17, 2026, 19:27 UTC
• Supabase: Sign-in failures for `signInWithIdToken` (OIDC) logins on free-tier projectsMinor · Aug 19, 2026, 12:47 UTC
• Linear: Delayed actions for Linear agent and loops automationsMinor · Aug 19, 2026, 15:26 UTC

How often does Cursor have incidents?

Cursor reported 50 incidents in the last 90 days, 15 of them major or critical. A typical incident lasted 1h 8m. See Cursor's uptime and incident history