Elevated errors for OpenAI model requests
Cursor reported elevated errors for requests to OpenAI models. The incident affected Automations, Cloud Agents, CLI, IDE, and Third-party models. Cursor reported recovery and then resolved the incident after 34 minutes.
State
Resolved
Started
Lasted
34 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
32 min 94%
Monitoring
2 min 6%
Updates
Times in UTCAs posted by Cursor
This incident has been resolved.
We're seeing recovery and are continuing to monitor. We'll share another update soon.
We're investigating elevated errors affecting requests to OpenAI models. Some users may see failed or incomplete responses. Other models are unaffected and can be used in the meantime. We'll share another update as soon as we have more information.
Affected components
5Cursor in the last 90 days
Full historyIncidents in 90 days
55
Days with an incident
35
Median duration
1 h 7 min
This incident
49% shorter than the median
Other Cursor incidents
All incidentsCursor·Grok Bot is currently degraded
Grok Bot was degraded. Cursor reports that the issue is resolved. The outage lasted 77 minutes.
Cursor·Computer use in Grok Bot fails for users in a few regions.
Computer use in Grok Bot fails for users in a few regions. Cursor reports that the issue is resolved. The outage lasted 14 minutes.
Cursor·composer-2.5 degraded
Cursor reports that composer-2.5 requests were degraded. This affected Automations, Bugbot, Cloud Agents, CLI, IDE, and Cursor IDE (iOS). Cursor resolved the incident after 50 minutes.
Cursor·Degraded Performance - Grok Bot
The Grok Bot component had degraded performance. Cursor reports that the issue is resolved. The incident lasted 75 minutes.
Cursor·3 "Slow clones from GH due to Github degradation"
Cursor Cloud Agents and Bugbot had slow startups and slow runs. The cause was a GitHub incident that affected Git operations. Cursor reports that the incident is resolved. It lasted about 72 minutes.
Follow Cursor
Your coding agent knows when Cursor is down, and tells you when a failure is theirs, not yours. You can also get Cursor incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "cursor" and tell me if Cursor has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=cursor/feed subscribe https://outages.live/feed.xml?providers=cursorFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane