Outage in Cursor
Opus 5.5 is Experiencing 429s
Resolved MinorIncident Report
Summary AI Generated
**Cursor – Opus 5.5 429 Errors (1.7 hours)** Cursor experienced a service degradation where Opus 5.5 returned 429 (rate limit/too many requests) errors across all product components. A fix was implemented approximately 14 minutes into the incident and monitored before being confirmed resolved roughly 1.5 hours later.
We are investigating a service degradation with Opus 5.5 being used across all product components.
Trusted by 1,000+ teams
The Status Page Aggregator with Early Outage Detection
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
Latest Updates ( sorted recent to last )
RESOLVED
1 day ago - at 10/08/2026 03:31PM
This incident has been resolved.
MONITORING
1 day ago - at 10/08/2026 02:08PM
A fix has been implemented and we are monitoring for service restoration.
INVESTIGATING
1 day ago - at 10/08/2026 01:54PM
We are investigating a service degradation with Opus 5.5 being used across all product components.
Latest Cursor outages
Elevated errors affecting Opus 5.5 - about 21 hours ago
Investigating service degradation — Grok Bot - 2 days ago
Investigating service degradation — Cloud Agents - 3 days ago
The Status Page Aggregator with Early Outage Detection
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with
