Skip to main content

Cursor · 14m ago

Multiple services degraded

Resolved

Yes — Cursor had a problem on October 28, 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: 10/28/2026, 9:15:10 PM

Last update: 10/28/2026, 11:13:34 PM

Resolved: 10/28/2026, 11:13:34 PM

Affected: k0trcq273dr6, bugbot, mwv1g9sc7kdh, sm5wkcnqkvr9, xwjpvdf81qh9

Cursor's official report →

Updates

  • resolved

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

    10/28/2026, 11:13:34 PM

  • investigating

    Services have recovered and we're monitoring to make sure everything stays stable. If you're still seeing errors, please try again. We'll post another update once we've confirmed the issue is fully resolved.

    10/28/2026, 10:42:05 PM

  • resolved

    Services have recovered and we're monitoring to make sure everything stays stable. If you're still seeing errors, please try again. We'll post another update once we've confirmed the issue is fully resolved.

    10/28/2026, 10:40:52 PM

  • investigating

    A fix has been implemented and services are starting to recover. We will share another update shortly.

    10/28/2026, 10:06:55 PM

  • investigating

    We are investigating service degradation for multiple services. Users may see failures across Automations, Bugbot, Cloud Agents, Grok Bot, and Origin. We are working on a fix and will update shortly.

    10/28/2026, 9:39:37 PM

  • investigating

    We are investigating service degradation for multiple services. Users may see failures across Cloud Agents, Grok Bot, and Origin. Apologies for the trouble.

    10/28/2026, 9:15:10 PM

More Cursor incidents

Is Cursor down right now?All outage history →