Skip to main content

Cursor · 71d ago

Investigating service degradation

Resolved

Yes — Cursor had a problem on July 31, 2026, and Cursor has since marked it resolved. Cursor's latest word: “This incident has been resolved. All services have returned to normal operation.”

See Cursor's live status →

Timeline

Started: 7/31/2026, 7:50:12 PM

Last update: 7/31/2026, 9:10:01 PM

Resolved: 7/31/2026, 9:10:01 PM

Affected: k0trcq273dr6, 2x2chyqwmkzl, vsny1qv7v86c, mwv1g9sc7kdh, jh0714rgjgt4, rflc60xp5jp2

Cursor's official report →

Updates

  • resolved

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

    7/31/2026, 9:10:01 PM

  • monitoring

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

    7/31/2026, 8:56:07 PM

  • monitoring

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

    7/31/2026, 8:37:09 PM

  • identified

    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.

    7/31/2026, 8:34:00 PM

  • investigating

    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.

    7/31/2026, 8:21:58 PM

  • investigating

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

    7/31/2026, 7:50:13 PM

More Cursor incidents

Is Cursor down right now?All outage history →