Cursor Status
Real-time updates of Cursor issues and outages
Cursor status is Operational
Cursor Automations
Cursor CLI
Cursor Cloud Agents
Cursor IDE
Cursor Grok Bot
You're checking on Cursor - but is your own site converting?
Outages aren't the only thing that costs you visitors.
Get a visual audit that shows exactly where your site loses conversions.
Free, takes 2 minutes.
Active Incidents
No active incidents
Recently Resolved Incidents
We are investigating a service degradation affecting Grok Bot.
We are investigating a service degradation affecting Grok Bot. Grok Bot computers may temporarily not be able to be created, reached, or reset.
We are investigating degraded performance for requests that use Grok 4.7.
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.
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.
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.
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.
Cursor Outage Survival Guide
Cursor Components
Cursor Automations
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.
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.
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.
We are investigating degraded performance for requests that use Grok 4.7.
Cursor Review Agents
Cursor CLI
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.
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.
We are investigating degraded performance for requests that use Grok 4.7.
Cursor Cloud Agents
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.
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.
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.
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.
We are investigating degraded performance for requests that use Grok 4.7.
Cursor cursor.com
Cursor IDE
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.
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.
We are investigating degraded performance for requests that use Grok 4.7.
Cursor Origin
Cursor Grok Bot
We are investigating a service degradation affecting Grok Bot. Grok Bot computers may temporarily not be able to be created, reached, or reset.
We are investigating a service degradation affecting Grok Bot.