Live / Cursor / Incident
Cursor: Opus 5.5 is Experiencing 429s
Cursor · cursor.comMinor incidentResolved2026-10-08 15:31 UTC
Public — what happened
Summary
Cursor said it was looking into a degradation affecting the Opus 5.5 model, which it said was impacting every part of its product, and it labeled the incident minor. The report began at 13:54 UTC on 2026-10-08, and the title referred to the model returning 429 errors. Cursor said it put a fix in place by 14:08 UTC and was watching to confirm service recovered, then marked the incident resolved at 15:31 UTC. No cause was given in the text it published.
Affected
Third-party models
Timeline
- Started — 2026-10-08 13:54 UTC
- Investigating — 2026-10-08 13:54 UTC (2 updates)
- Resolved — 2026-10-08 15:31 UTC · 1h 37m after it started
With SquidGrid — where it starts on the route
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 seeCustomers 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.