Live  /  Cursor  /  Incident

Cursor: Elevated errors affecting Opus 5.5

Cursor · cursor.comMinor incidentResolved2026-10-08 20:51 UTC
Public — what happened

Summary

Cursor reported a minor incident in which people using the Opus 5.5 model could run into occasional errors or requests that did not go through. The company began looking into the problem at 19:52 UTC on October 8, 2026. Cursor did not share a cause, and it marked the issue as resolved at 20:51 UTC the same day, roughly an hour later.

Affected

Third-party models

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 42, 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.