outages.live
Live
CursorIncident ·

Elevated errors for some requests

Partial outageOfficial update
0

Cursor reports elevated errors for some requests on cursor.com and Grok Bot. Some requests fail, including purchases and other billing actions. Cursor identified the cause, implemented a fix, and now monitors for service restoration.

State

Monitoring

Started

Ongoing for

46 min

Worst impact

Partial outage

Timeline

3 updates
20:0820:1920:3120:4220:54
Partial outageDegradedUpdate postedTimes in UTC

Investigating

37 min 81%

Monitoring

9 min 19%

Updates

Times in UTC

As posted by Cursor

Monitoring

A fix has been implemented and we are monitoring for service restoration.

Investigating

We've identified the cause and are rolling out a fix. We'll share another update soon.

Investigating

We're investigating an issue that may cause some requests to fail, including purchases and other billing actions. We'll share another update as soon as we have more information.

Affected components

2
cursor.comGrok Bot

Cursor in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

56

Days with an incident

36

Median duration

1 h 7 min

This incident

31% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

9 h 34 min
median 1 h 7 min
90 days agoToday

Other Cursor incidents

All incidents

Cursor·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.

Resolved

Cursor·Grok Bot is currently degraded

Grok Bot was degraded. Cursor reports that the issue is resolved. The outage lasted 77 minutes.

Resolved

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.

Resolved

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.

Resolved

Cursor·Degraded Performance - Grok Bot

The Grok Bot component had degraded performance. Cursor reports that the issue is resolved. The incident lasted 75 minutes.

Resolved

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.

Prompt
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.

RSS
https://outages.live/feed.xml?providers=cursor
Slack
/feed subscribe https://outages.live/feed.xml?providers=cursor

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane