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 - 71ms HTTP response. Last checked . 90-day uptime: 99.9%.
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
99.9%
20 incidents (90d)
Response now
71ms
HTTP p50 (7d)
138ms
median ping response
HTTP p95 (7d)
790ms
tail ping response
Response time (7 days)
p50 138ms·p95 790msⓘ 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 Grok 4.6.
We are investigating a service degradation affecting Automations.
An upstream Anthropic issue is causing elevated errors for Claude Opus 5 and Fable 5 requests. Some users may experience errors or failed Agent turns. We're monitoring recovery and will provide update…
We are investigating a service degradation affecting some non-fast Grok-4.6 sessions. Users may experience failures in sessions with attached images.
We are investigating elevated errors affecting Fable 5. Other models remain available. Please switch to another model or select Auto while we investigate.
We are investigating a service degradation affecting Composer 2.5 (non-fast). Users may experience errors when making requests using this model.
We’re investigating elevated errors affecting GitHub-connected workflows in Cloud Agents. Some users may encounter failures or rate-limit errors. We’re working to restore normal operation.
We’re investigating an issue causing Grok Bot connectors to hang. We’ll share updates as we learn more.
We are investigating an issue preventing users from removing members from teams.
We are investigating a service degradation affecting Grok 4.6.
Customers may encounter errors when using Grok 4.6. We’re investigating and will share updates as we learn more.
We are investigating a service degradation affecting Automations, Cloud Agents, Review Agents and Codebase related to a GitHub degradation reported in GitHub's status page: https://www.githubstatus.co…
We are investigating a service degradation for requests that use Grok 4.6 (non-fast). Users may experience slowness and high error rates. Other models are unaffected.
All systems and components are operating as expected, but due to a service outage for one of our model providers, agent surfaces using Anthropic Models Claude Mythos 5, Claude Fable 5, and Claude Sonn…
We are investigating a service degradation affecting Cloud Agents and Bugbot due to an ongoing GitHub outage. Users may see failures or delays when starting or running Cloud Agents and when Bugbot att…
We are investigating degraded performance for requests that use Claude Fable. Users may see failed or retried requests in Automations, Cloud Agents, the CLI, and the IDE when Claude Fable is used. Oth…
We are investigating degraded performance for requests that use Composer 2.5. Users may see failed or retried requests in Automations, Cloud Agents, and the IDE when Composer 2.5 is used. Other models…
We are investigating a service degradation affecting Automations, Cloud Agents, and IDE. Affected agent surfaces: Composer, Claude Fable 5
We are investigating a service degradation for requests using Composer 2.5
We are investigating an issue where users are unable to authenticate with MCP servers in Automations and Cloud Agents. Affected runs may fail to connect to their MCP tools.
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.