DownForAI

Cursor status: API, auth, latency & outage reports

Cursor is operational right now. DownForAI checks Cursor every ~75 minutes across 2 monitored surfaces, with 0 community reports in the last 24 hours.

Operational
Last probe 17 min ago·2 surfaces
Likely your sideMEDIUM confidence
📡 Official status page →📚 Docs →💳 Pricing →
100.0%
24h Uptime
161ms
p50 Latency
508ms
p95 Latency
0
Incidents (30d)

Current Status

✅
Operational
Everything works normally
✓Checked by our probes · 96ms
Verified 17m ago
✓No major incident reported
ⓘNo reports in the last 24h

Having issues?

Help other users by reporting if Cursor is not working for you.

0reports in the last 24 hours

Surface Health

Cursor AI FeaturesOperational
HTTP 200p50 149ms17m ago
Cursor AppOperational
HTTP 200p50 173ms17m ago

Uptime — last 24h

100.0%

Latency — last 20 probes

Loading…

Is Cursor down for everyone?

Likely local or client-side issue
Our probes see normal responses. The issue is likely on your end or in your network path.
Moderate confidence
Probe summary (2 surfaces)
All surfaces operational as of last probe.
Signals detected
  • All monitored surfaces operational
  • No recent user reports
  • Check your network, credentials, or rate limits

Incident history (30d)

✓No incidents recorded in the past 30 days.

Reported symptoms

No user reports for Cursor in the last 24 hours.

Known error signatures

Common failure patterns and how to diagnose them

Provider details

AI-native code editor/IDE with tab completion, chat, agents, and model routing. Based on a VS Code fork; routes workloads to Anthropic, OpenAI, and Google models.

What we monitor
Cursor IDE — Core IDE features
Cursor CLI — CLI interface
Cloud Agents — Background agent tasks
Marketplace — Extension marketplace
Bugbot — Bug detection bot
Automations — Automation features
cursor.com — Website and authentication
Status page segments
IDECLICloud AgentsMarketplaceBugbotAutomationscursor.com
Model families
Anthropic (Claude Sonnet / Opus)OpenAI (GPT / o-series)Google (Gemini)Cursor proprietary/specialized internal model(s)User can bring their own API keys
Common limits & quotas
  • Hobby: limited agent requests + limited tab completions
  • Pro: $20/mo — expanded usage
  • Pro+: $60/mo — higher usage
  • Ultra: $200/mo — top-tier individual
  • Teams: $40/user/mo — centralized billing, org controls
  • Enterprise: custom — SSO, policy controls, SLAs
Ecosystem dependencies
Built on: VS Code (fork) — VS Code Marketplace issues can affect extension installsRoutes to: Anthropic API, OpenAI API, Google Gemini API — upstream outages cascadeAuth: Cursor's own auth system, independent of GitHub
Operator notes
  • Cursor's status page decomposes surfaces well: IDE, CLI, Cloud Agents, Marketplace, Bugbot, Automations, cursor.com can fail independently
  • Upstream cascades are common: when Claude API has incidents, Cursor's Claude-routed Chat degrades. Model picker swap is the first workaround.
  • The Cursor forum (forum.cursor.com) often surfaces issues minutes before the status page updates
  • Cursor auth is independent of GitHub — a GitHub outage doesn't break Cursor sign-in
Diagnostic signals
$ Check status.cursor.com per-component (IDE, CLI, Cloud Agents, Marketplace, Bugbot, Automations, cursor.com)$ In IDE: Cmd+Shift+P → Developer: Reload Window to clear extension state$ Test model switching: Chat panel → model picker dropdown$ For Cloud Agents: cancel current task, verify new task creation in status page

Fallback alternatives

What to use if this service is down

One upstream model is degraded (Claude/GPT/Gemini)
Switch model inside Cursor before leaving the IDE
Easy switch
Cursor IDE globally unavailable
Windsurf or VS Code + Copilot can reduce downtime for active sessions
Easy switch
Tab completions unavailable but Chat works
Use Chat for inline suggestions manually
Easy switch
Cloud Agents unavailable
Claude Code CLI or Devin can reduce downtime for autonomous tasks
Moderate effort
Offline continuity
VS Code + Continue.dev + local Ollama
Zero dependency after setup
Major migration

How we monitor

downforai.com probes each AI service every 2–5 minutes from multiple independent locations. We measure HTTP response codes, latency (p50 & p95), and endpoint availability across the surfaces listed above. Status is classified as Operational, Degraded, or Outage based on a weighted combination of probe results. Uptime is calculated over 30-minute buckets and the last 24 hours. User reports are factored into our diagnosis as a secondary signal. We are independent of all providers listed and receive no compensation to report any particular status.

Embed status badge

Add to your README, docs, or dashboard
PreviewCursor status
Markdown
[![Cursor status](https://downforai.com/api/badge/cursor.svg)](https://downforai.com/cursor)
HTML
<a href="https://downforai.com/cursor"><img src="https://downforai.com/api/badge/cursor.svg" alt="Cursor status" /></a>

Community Discussion

0/1000
No comments yet. Be the first to share your experience!

Still having issues with Cursor?

Let the community know and help others experiencing the same problem.