Cursor Status · History · Incident #6092

RESOLVED

Investigating service degradation

Critical · Started Jul 31, 2026 · 7:50 PM

  • Duration

    1h 19m

  • Severity

    Critical

  • Detection lead

  • User reports

Summary

Investigating service degradation

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


  • Started

    Jul 31, 2026 · 7:50 PM

  • Resolved

    Jul 31, 2026 · 9:10 PM

  • Duration

    1h 19m

  • Severity

    Critical

Event timeline

How this incident unfolded

  • Investigating

    Jul 31 · 7:50 PM Cursor

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

  • Investigating

    Jul 31 · 8:21 PM Cursor

    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.

  • Identified

    Jul 31 · 8:34 PM Cursor

    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.

  • Monitoring

    Jul 31 · 8:37 PM Cursor

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

  • Monitoring

    Jul 31 · 8:56 PM Cursor

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

  • Resolved

    Jul 31 · 9:10 PM Cursor

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

Get alerted before the next Cursor outage.

Pulsetic catches degradations minutes before vendors acknowledge them.

Start monitoring free