Live  /  Cursor  /  Incident

Cursor: composer-2.5 degraded

Cursor · cursor.comMinor incidentResolved2026-11-05 15:56 UTC
Public — what happened

Summary

Cursor reported a minor incident affecting requests to its Composer 2.5 feature, which it described as degraded. The company said it began investigating at 15:06 UTC on 2026-11-05. Cursor posted that the problem was resolved at 15:56 UTC, and it did not state a cause or say who was affected.

Affected

Automations, Review Agents, Cloud Agents, CLI, IDE, Cursor IDE (iOS)

As listed on Cursor’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Cursor against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Cursor: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Cursor report →

More from Cursor

Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.

The full archive is on the Cursor status & history page.

Related: Cursor status & history. SquidGrid is not affiliated with Cursor.