Is Cursor down right now?
HTTP endpoint monitoring - checked every 5 minutes · How we classify outages
Weekly AI pricing & uptime digest
Price drops, new model releases, and incident summaries - every Monday. Free.
Cursor is currently operational - 33ms HTTP response. Last checked . 90-day uptime: 100%.
Stay informed
Follow @tickerr_ai
We post when tier 1 LLM APIs go down - before the official status page updates.
Follow on X →Or get the weekly reliability digest:
Add a status badge
Show live Cursor status on your site, README, or docs.
90-day uptime
100%
20 incidents (90d)
Response now
33ms
HTTP p50 (7d)
132ms
median ping response
HTTP p95 (7d)
880ms
tail ping response
Response time (7 days)
p50 132ms·p95 880msⓘ HTTP response times from Tickerr's monitoring server to Cursor's status or homepage endpoint - not API inference latency or time-to-first-token (TTFT). For API benchmark data, see third-party sources like Artificial Analysis.
90-day uptime comparison
Independent monitoring catches issues faster - official pages sometimes lag by hours before acknowledging problems.
Service components
via status.cursor.com ↗Incident history
We are investigating a service degradation affecting Cloud Agents and Grok Bot. Some new Cloud Agents and Grok Bot sessions may fail to start.
We are investigating a service degradation affecting Cloud Agents.
We are investigating a service degradation affecting Opus 5.5. Users may see intermittent errors or failed requests when using Opus 5.5.
We are investigating a service degradation with Opus 5.5 being used across all product components.
We are investigating a service degradation affecting Grok Bot's computers in certain regions.
We are investigating a service degradation affecting Cloud Agents.
We are investigating a service degradation affecting some Cloud Agents and Grok Bot features.
We are investigating a service degradation affecting Security Reviewer agents.
We are investigating a service degradation affecting Opus 5.5. More information: https://status.claude.com/incidents/ch27pb90bn85
We are investigating a service degradation affecting Grok Bot and Review Agents.
We are investigating a service degradation affecting xAI models. Some Agent requests may fail.
We are investigating a service degradation affecting Cloud Agents and Grok Bot.
We are investigating a service degradation affecting Grok Bot.
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. Othe…
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 model…
Related pages
About Cursor status
Cursor is an AI-powered code editor built on VSCode. Cursor downtime affects developers who rely on AI code completion and chat. If Cursor AI is not working, it may be a server-side issue affecting all users.