Cursor incident

Investigating service degradation

Critical Resolved View vendor source →

Cursor experienced a critical incident on July 31, 2026 affecting Automations and Bugbot and 1 more component, lasting 1h 19m. The incident has been resolved; the full update timeline is below.

Started
Jul 31, 2026, 07:50 PM UTC
Resolved
Jul 31, 2026, 09:10 PM UTC
Duration
1h 19m
Detected by Pingoru
Jul 31, 2026, 07:50 PM UTC

Affected components

AutomationsBugbotCLICloud Agentscursor.comIDE

Update timeline

  1. investigating Jul 31, 2026, 07:50 PM UTC

    We are investigating a widespread issue affecting Cursor. Users may see failures across the IDE, Cloud Agents, Automations, and related services.

  2. investigating Jul 31, 2026, 08:21 PM UTC

    We are continuing to investigate a widespread issue affecting Cursor. Users may still see failures across the IDE, Cloud Agents, Automations, and related services. We will post another update shortly.

  3. identified Jul 31, 2026, 08:34 PM UTC

    We have identified the issue causing widespread failures across Cursor and are working on a fix. Users may continue to see errors in the IDE, Cloud Agents, Automations, and related services until the fix is fully rolled out.

  4. monitoring Jul 31, 2026, 08:37 PM UTC

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

  5. monitoring Jul 31, 2026, 08:56 PM UTC

    Service is largely recovering. Some intermittent issues may remain as we finish restoring all systems. We are continuing to monitor.

  6. resolved Jul 31, 2026, 09:10 PM UTC

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