Skip to main content

Cursor · 3h ago

Investigating service degradation

Resolved

Yes — Cursor had a problem on September 15, 2026, and Cursor has since marked it resolved. Cursor's latest word: “This incident has been resolved at 6pm Eastern.”

See Cursor's live status →

Timeline

Started: Sep 15, 2026, 9:26 PM UTC

Last update: Sep 15, 2026, 10:00 PM UTC

Resolved: Sep 15, 2026, 10:00 PM UTC

Affected: k0trcq273dr6, 2x2chyqwmkzl, vsny1qv7v86c, mwv1g9sc7kdh, rflc60xp5jp2, xwjpvdf81qh9, sm5wkcnqkvr9

Cursor's official report →

Updates

  • resolved

    This incident has been resolved at 6pm Eastern.

    Sep 15, 2026, 10:00 PM UTC

  • monitoring

    A fix has been implemented and we are monitoring for service restoration. Only Grok 4.6 (non-fast) is affected in Cursor.

    Sep 15, 2026, 9:41 PM UTC

  • monitoring

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

    Sep 15, 2026, 9:38 PM UTC

  • investigating

    We are investigating a service degradation. Affected agent surfaces: Composer and xAI.

    Sep 15, 2026, 9:26 PM UTC

More Cursor incidents

Is Cursor down right now?All outage history →