Cursor reported "Degraded Performance - Grok Bot" on its status page at 2026-11-05 00:34 UTC. Grok Bot shows degraded performance for Cursor. Cursor reports that it is investigating errors with Grok Bot.

Cursor lists these components: Grok Bot.

When did the incident start and end?

It started at 2026-11-05 00:34 UTC. This page shows the end time when Cursor marks it resolved.

How do I get alerts for Cursor?

Subscribe to the Cursor live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Cursor. outages.live reads it every few minutes and keeps every update. A language model writes the summary from those updates.

CursorIncident ·

Degraded Performance - Grok Bot

DegradedOfficial update

Grok Bot shows degraded performance for Cursor. Cursor reports that it is investigating errors with Grok Bot.

State

Investigating

Started

Ongoing for

1 h 1 min

Worst impact

Degraded

Timeline

1 update

00:3400:4901:0501:2001:35

DegradedUpdate postedTimes in UTC

Investigating

1 h 1 min 100%

Updates

Times in UTC

As posted by Cursor

Investigating

We are currently investigating errors with Grok Bot.

Affected components

Grok Bot

Cursor in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 10 min

This incident

About 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 10 min

90 days agoToday

Other Cursor incidents

All incidents

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.

Resolved

Cursor·Issues with source control integrations

Source control integrations do not work in the Cursor IDE and Grok Bot. Cursor reports that the issue is resolved. The outage lasted 1 hour and 15 minutes.

Resolved

Cursor·Service Degradation - Billing and Usage Dashboard

Cursor reports a service degradation on the billing and usage dashboard. The cursor.com and Enterprise Dashboard components are affected. Cursor states that the incident is resolved. The outage lasted about 5 hours and 15 minutes.

Resolved

Cursor·Multiple services degraded

This incident has been resolved.

Resolved

Cursor·Auto Review Degradation

This has been resolved

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