Cursor reported "Grok Bot is currently degraded" on its status page at 2026-11-06 13:57 UTC. Grok Bot was degraded. Cursor reports that the issue is resolved. The outage lasted 77 minutes.

Cursor lists these components: Grok Bot.

When did the incident start and end?

It started at 2026-11-06 13:57 UTC and ended at 2026-11-06 15:15 UTC. It lasted 1 h 17 min.

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 ·

Grok Bot is currently degraded

ResolvedOfficial update

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

State

Resolved

Started

Lasted

1 h 17 min

Worst impact

Degraded

Timeline

2 updates

13:5714:1714:3614:5515:15

DegradedUpdate postedTimes in UTC

Investigating

1 h 17 min 100%

Updates

Times in UTC

As posted by Cursor

Resolved

This issue has been resolved.

Investigating

Grok Bot is currently degraded, and our team is investigating.

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

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

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