Skip to main content

Cursor · 36d ago

Investigating service degradation

Resolved

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

See Cursor's live status →

Timeline

Started: 9/2/2026, 12:48:00 AM

Last update: 9/2/2026, 4:07:31 AM

Resolved: 9/2/2026, 3:07:00 AM

Affected: k0trcq273dr6, vsny1qv7v86c, mwv1g9sc7kdh, rflc60xp5jp2

Cursor's official report →

Updates

  • resolved

    This incident has been resolved.

    9/2/2026, 4:07:12 AM

  • monitoring

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

    9/2/2026, 1:04:37 AM

  • investigating

    We're currently investigating degraded performance affecting requests made with Composer 2.5 and Grok 4.6 Fast. While these models are in use, you may encounter failed or retried requests across Automations, Cloud Agents, the CLI, and the IDE. Other models are unaffected.

    9/2/2026, 12:48:13 AM

More Cursor incidents

Is Cursor down right now?All outage history →

Is Cursor down? Cursor is up now — Sep 2, 2026 outage | AI Status