Cursor Outage History
Past incidents and downtime events
Complete history of Cursor outages, incidents, and service disruptions. Showing 50 most recent incidents.
November 2026(1 incident)
Service Degradation - Billing and Usage Dashboard
3 updates
This incident has been resolved.
We are continuing to work towards a resolution and will share more information as it becomes available.
We are investigating a service degradation affecting our billing and usage dashboard. We will share updates as more information becomes available.
October 2026(33 incidents)
Multiple services degraded
2 updates
This incident has been resolved.
We are investigating a service degradation at the moment. We'll share more updates as soon as more information is available.
Auto Review Degradation
2 updates
This has been resolved
We are investigating a degradation in Auto Review functionality
Cloud Agent Degradation
2 updates
This incident has been resolved. Cloud Agent services have returned to normal operation.
We are investigation a degradation to Cloud Agents
Investigating Service Degradation with VS Code Extensions
2 updates
This incident has been resolved. All services have returned to normal operation.
We are investigating a service degradation with VS Code extensions
Degraded performance — Origin and Cloud Agents
2 updates
This incident has been resolved. Cloud Agents and Origin have returned to normal performance.
We are investigating degraded performance affecting Cloud Agents and Origin. Users may see slow responses, timeouts, or retried requests. Our team is actively working to restore normal performance.
Multiple services degraded
6 updates
This incident has been resolved. All services have returned to normal operation.
Services have recovered and we're monitoring to make sure everything stays stable. If you're still seeing errors, please try again. We'll post another update once we've confirmed the issue is fully resolved.
Services have recovered and we're monitoring to make sure everything stays stable. If you're still seeing errors, please try again. We'll post another update once we've confirmed the issue is fully resolved.
A fix has been implemented and services are starting to recover. We will share another update shortly.
We are investigating service degradation for multiple services. Users may see failures across Automations, Bugbot, Cloud Agents, Grok Bot, and Origin. We are working on a fix and will update shortly.
We are investigating service degradation for multiple services. Users may see failures across Cloud Agents, Grok Bot, and Origin. Apologies for the trouble.
Delayed responses in Grok Bot
2 updates
This issue has been resolved. For a short period, some Grok Bot responses were delayed. Responses are back to normal and we're sorry for the disruption.
We're investigating an issue causing delayed responses in Grok Bot. We'll share an update as soon as we have more information.
Elevated errors affecting repository integrations
2 updates
This incident has been resolved. Affected services returned to normal operation at approximately 08:02 UTC.
We are investigating elevated errors affecting some repository integrations. Features that rely on repository access, including review agents and cloud agents, may fail or be delayed. We are working to restore normal service.
Payment System Sync Issues
2 updates
This has been resolved.
Users may encounter unexpected blocks with payments. Our team are actively investigating this.
Degraded agent personalization and codebase sync
3 updates
This has been resolved.
We've identified the cause and are rolling out a fix.
We're investigating an issue affecting codebase indexing and saved rules and memories. Codebase indexes may not update, and agents may respond without your saved rules or memories. Chat, agents, and Tab are otherwise available. We're working with our infrastructure provider and will share updates as we learn more.
Elevated errors for Claude Sonnet 5.5
3 updates
This incident has been resolved.
We are seeing improvement for Claude Sonnet 5.5 requests. We are continuing to monitor the situation. Some users may still see occasional errors when using this model.
We are investigating elevated errors affecting requests to Sonnet 5.5. Some users may see failed or rate-limited responses when using this model.
Degraded Model Performance
2 updates
We have identified and resolved the issue.
We are currently investigating some degraded model performance.
Investigating service outage - Grok models unavailable
3 updates
This incident has been resolved.
A fix has been implemented and Grok models are recovering. We're monitoring to confirm full service restoration.
We are investigating a service outage affecting Grok models.
Elevated errors for Bitbucket Cloud integrations
2 updates
Atlassian has reported the issue as resolved and they are continuing to monitor for service restoration.
We are investigating an issue affecting Cursor's Bitbucket Cloud integration. More information: https://bitbucket.status.atlassian.com/incidents/ldlx0fdgls28.
Investigating service degradation
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring for service restoration.
We are investigating a service degradation affecting billing dashboards. You may notice errors in regards to billing, usage, and plan changes.
Investigating service degradation
1 update
We experienced service degradation affecting Anthropic models between 5:56 ET and 6:21 ET, which has since been resolved.
Investigating service degradation — Grok Bot
2 updates
This incident has been resolved.
We are investigating a service degradation affecting Grok Bot and grok.com. You may notice errors related to billing, plans, and usage.
Investigating service degradation — Grok Bot
4 updates
This incident has been resolved.
A fix has been implemented and we are monitoring for service restoration.
We are continuing to investigate this issue. We will provide updates as more information becomes available.
We are investigating a service degradation affecting Grok Bot where routines may be delayed.
Investigating service degradation
3 updates
This incident has been resolved. Thank you for your patience!
A fix has been implemented and we are monitoring for service restoration.
We are investigating elevated errors for Anthropic Opus 5.5.
Elevated errors affecting Grok models
3 updates
This incident has been resolved. Grok models in Cursor are working normally again.
A fix has been implemented and we are monitoring for service restoration.
We are investigating elevated errors affecting Grok models in Cursor. Some requests may fail with a capacity error. Retrying the request or switching to another model may help.
Investigating service degradation — Grok Bot
3 updates
This incident has been resolved.
We've identified the issue impacting Grok Bot for some users and are working on a fix.
We are investigating a service degradation affecting Grok Bot and preventing some users from reaching their computers
Grok Bot routines not triggering
1 update
Between 10:52 AM and 1:29 PM PT on October 13, many Grok Bot routines started by webhooks, Slack, git, email and Linear events didn't run. Webhook callers may have seen an HTTP 400 "Automation run rate limit exceeded" error, and other triggers failed without an error. Your own usage didn't cause this. Routines are running normally again. Events sent during this window weren't processed and won't be retried automatically, so please resend anything important.
Degraded performance and errors across Cursor services
6 updates
This incident has been resolved.
All Cursor services have recovered and are operating normally, except Cloud Agents. Some Cloud Agents may still be slow to start or fail to run, and we're actively working to restore full service. We'll share another update as soon as we have more information.
Grok Bot has recovered and is operating normally. We are continuing to monitor recovery across the IDE, Cloud Agents, and other affected services, and some users may still see intermittent errors.
We are continuing to monitor recovery. Some users may still see intermittent errors.
A fix has been implemented and services are recovering. Some users may still see intermittent errors while we monitor for full restoration.
We are investigating a widespread issue affecting Cursor. Users may see errors or failed requests across the IDE, Cloud Agents, Automations, Grok Bot, and Origin. Our team is actively working to restore service.
Investigating service degradation — Cloud Agents and Grok Bot
2 updates
This incident has been resolved. New Cloud Agents and Grok Bot sessions are starting normally again.
We are investigating a service degradation affecting Cloud Agents and Grok Bot. Some new Cloud Agents and Grok Bot sessions may fail to start.
Investigating service degradation — Cloud Agents
2 updates
This incident has been resolved.
We are investigating a service degradation affecting Cloud Agents.
Elevated errors affecting Opus 5.5
2 updates
This incident has been resolved.
We are investigating a service degradation affecting Opus 5.5. Users may see intermittent errors or failed requests when using Opus 5.5.
Opus 5.5 is Experiencing 429s
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring for service restoration.
We are investigating a service degradation with Opus 5.5 being used across all product components.
Investigating service degradation — Grok Bot
2 updates
This incident has been resolved.
We are investigating a service degradation affecting Grok Bot's computers in certain regions.
Investigating service degradation — Cloud Agents
5 updates
This incident has been resolved.
We are currently investigating this issue. We will provide updates as more information becomes available.
We are currently investigating this issue. We will provide updates as more information becomes available.
We are currently investigating this issue. We will provide updates as more information becomes available.
We are investigating a service degradation affecting Cloud Agents.
Investigating service degradation — Cloud Agents and Grok Bot
4 updates
This incident has been resolved.
Grok Bot has been restored. We are continuing to investigate a service degradation affecting some Cloud Agents.
We are currently investigating this issue. We will provide updates as more information becomes available.
We are investigating a service degradation affecting some Cloud Agents and Grok Bot features.
Investigating service degradation — Security Reviewer Agents
2 updates
This incident has been resolved.
We are investigating a service degradation affecting Security Reviewer agents.
Elevated errors affecting Anthropic models
2 updates
This incident has been resolved.
We are investigating a service degradation affecting Opus 5.5. More information: https://status.claude.com/incidents/ch27pb90bn85
Investigating service degradation — Grok Bot and Review Agents
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring for service restoration.
We are investigating a service degradation affecting Grok Bot and Review Agents.
September 2026(16 incidents)
Investigating service degradation - xAI models
3 updates
This incident has been resolved.
We have identified the cause of degraded performance affecting xAI models and are working to restore full capacity. Users may see errors, slow responses, or rate limiting on these models, and some Cloud Agent tasks may fail. We will post another update shortly.
We are investigating a service degradation affecting xAI models. Some Agent requests may fail.
Investigating service degradation — Cloud Agents and Grok Bot
4 updates
This incident has been resolved.
Fixes are being implemented and we are monitoring for service restoration.
The root cause has been identified and a fix is being implemented.
We are investigating a service degradation affecting Cloud Agents and Grok Bot.
Investigating service degradation — Grok Bot
2 updates
This incident has been resolved.
We are investigating a service degradation affecting Grok Bot.
Investigating service degradation — Grok Bot
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring for service restoration.
We are investigating a service degradation affecting Grok Bot.
Investigating service degradation — Grok Bot
3 updates
The service degradation affecting Grok Bot has been resolved.
We have identified the cause and are deploying a fix. We are monitoring recovery as the fix rolls out. Some Grok Bot computers may remain temporarily unavailable or unable to be created or reset during this time.
We are investigating a service degradation affecting Grok Bot. Grok Bot computers may temporarily not be able to be created, reached, or reset.
Investigating service degradation - Grok 4.7
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring for service restoration.
We are investigating degraded performance for requests that use Grok 4.7.
Investigating — Cloud Agent Dockerfile Builds
4 updates
This incident has been resolved.
A fix has been implemented and we are monitoring for service restoration.
The root cause has been identified and a fix is being implemented.
Customers using Cloud Agents with Dockerfile-based builds may be unable to create new builds. Existing Cloud Agents continue to run on their current image; only new Dockerfile builds are affected.
Investigating service degradation — Automations and Cloud Agents w/ Grok 4.7
3 updates
This incident has been resolved.
The root cause has been identified and a fix is being implemented.
We are aware of an issue where Grok 4.7 fails to be selected as a model for Cloud Agents. We are investigating the issue.
Investigating service degradation
2 updates
This incident has been resolved.
We are investigating degraded performance for requests that use Grok models. Users may see failed or retried requests in Automations, Cloud Agents, the CLI, and the IDE when Grok models are used. Other models are unaffected.
Investigating service degradation
2 updates
This incident has been resolved.
We are investigating degraded performance for requests that use Grok 4.6. Users may see failed or retried requests in Automations, Cloud Agents, the CLI, and the IDE when Grok 4.6 is used. Other models are unaffected.
Sign-in and dashboard errors for some users
3 updates
This incident has been resolved.
Sign-in is recovering. The issue came from our authentication provider, who has identified the cause and is seeing recovery on their side. We are monitoring to confirm everything is back to normal.
We are investigating an issue affecting sign-in. Signing in, signing out, and loading the dashboard may hang or fail. If you are already signed in, your session should continue to work normally. We will provide another update shortly.
Investigating service degradation — Grok Bot
4 updates
This incident has been resolved.
A fix has been implemented and we are monitoring for service restoration. Grok Bot should be responding normally again.
The root cause has been identified and a fix is being rolled out. Some users may see Grok Bot respond slowly or not respond at all. We will provide another update shortly.
We are investigating a service degradation affecting Grok Bot.
Investigating service degradation — Grok Bot
2 updates
This incident has been resolved.
We are investigating a service degradation affecting Grok Bot. Users may experience degraded performance or bots that don't respond.
Investigating service degradation — Cloud Agents and Automations
7 updates
This incident has been resolved.
A fix has been implemented and we are monitoring for service restoration.
Affected services are back to normal operation. Our team continues to monitor everything closely.
We are continuing to investigate this issue. Cloud Agents, Automations, and Review Agents (resulting from Cloud Agents) are affected. Bugbot is not affected.
We are continuing to investigate this issue.
We are currently investigating this issue. We will provide updates as more information becomes available.
We are investigating a service degradation affecting Cloud Agents and Automations
Investigating service degradation — Grok Bot
2 updates
This incident has been resolved.
We are investigating a service degradation affecting Grok Bot. Users may experience degraded performance or bots that don't respond.
Investigating service degradation — Grok Bot
3 updates
This incident has been resolved.
The root cause has been identified and a fix is being implemented.
We are investigating a service degradation affecting Grok Bot. Users may experience degraded performance or bots that don't respond.
📡 Tired of checking Cursor status manually?
Better Stack monitors uptime every 30 seconds and alerts you instantly when Cursor goes down.