Is Cursor down?
No, Cursor is not down.
Cursor’s status page reports no incidents, api2.cursor.sh responded from 6 regions, and nobody reported problems in the last hour.
- Official statusNo incidentsstatus.cursor.com
- Reachable6 of 6 regionsCursor API · api2.cursor.sh
- Reports in the last hour0Normal
Cursor’s status page
From status.cursor.com. Read at
- IDEOperational
- Cursor IDE (iOS)Operational
- CLIOperational
- cursor.comOperational
- Cloud AgentsOperational
- AutomationsOperational
- BugbotOperational
- Grok BotOperational
Show all 11 components
- Third-party modelsOperational
- OriginOperational
- Enterprise DashboardOperational
Not working for me
Pick what’s broken. Your report shows up on the chart below within a few minutes.
Last 24 hours
No problems in the last 24 hours, median response 377 ms, and 0 reports.
- Operational
- Degraded
- Partial outage
- Major outage
- No data
- Reachability check (api2.cursor.sh)
By region
| Region | Cursor API api2.cursor.sh |
|---|---|
| N. Virginia | Up · 53 ms |
| Oregon | Up · 181 ms |
| Frankfurt | Up · 427 ms |
| Singapore | Up · 651 ms |
| Tokyo | Up · 448 ms |
| São Paulo | Up · 367 ms |
Each row shows the latest result from that region. How we check
Last 90 days
We have checked Cursor ourselves since Oct 28, 2026. Earlier days come from its status page.
30 days with problems in the last 90 days.
Recent incidents
Incidents: 35 in the last 30 days and 50 in the last 90, lasting a median of 1 h 2 min.
- 3 "Slow clones from GH due to Github degradation"Degraded1 h 12 min
- Issues with source control integrationsDegraded1 h 16 min
- Service Degradation - Billing and Usage DashboardDegraded5 h 15 min
- Multiple services degradedDegraded44 min
- Auto Review DegradationDegraded1 h 35 min
- Cloud Agent DegradationDegraded7 h 41 min
- Investigating Service Degradation with VS Code ExtensionsDegraded9 h 35 min
- Degraded performance — Origin and Cloud AgentsDegraded16 min
- Multiple services degradedPartial outage1 h 59 min
- Delayed responses in Grok BotPartial outage9 min
If Cursor isn’t working for you
Cursor is an AI code editor built on VS Code, with agent, chat and tab completion features powered by Cursor's own and third-party models.
Common Cursor errors
| Error | What it means | Usually | What to do |
|---|---|---|---|
Connection failed. If the problem persists, please check your internet connection or VPN | Cursor could not reach its servers; corporate proxies that block HTTP/2 are a common cause, but it also appears during Cursor incidents. | Your side | Turn on "Disable HTTP/2" in settings, start a new chat, and try another network. Source |
We're having trouble connecting to the model provider. This might be temporary - please try again in a moment. | A generic error between Cursor and the model provider; Cursor staff say it is most often a network issue, but a custom API key or a failing MCP server can also cause it. | Your side | Run Cursor's Network Diagnostics, disable HTTP/2, turn off custom API keys and MCP servers, and try another model. Source |
We're experiencing high demand for Composer 2 right now. Please switch to Auto, another model, or try again in a few moments | The selected model is at capacity; it is not your subscription limit. | Heavy load | Switch to Auto or another model, or retry in a couple of minutes. Source |
Is it just you?
- Run Network Diagnostics in Cursor's settings; corporate proxies and VPNs often break its HTTP/2 connection.
- Switch models: a high-demand error on one model while others answer is capacity, not an outage.
- Turn off custom OpenAI keys, base URL overrides and MCP servers to rule them out.
- Start a new chat; long agent sessions can fail on their own.
- Check Cursor's components on status.x.ai and the reports on this page.
Alternatives to Cursor
Questions
Cursor's forum staff most often trace it to proxies or VPNs that block HTTP/2, and turning on Disable HTTP/2 fixes many cases. If it starts for many users at once, check Cursor's components on status.x.ai.
Cursor depends on several model providers, so one provider's incident can break some models while others work. Try a different model before assuming Cursor itself is down.
Sources: forum.cursor.com, forum.cursor.com, status.x.ai
Get alerted when Cursor breaks your app.
If your product depends on Cursor, your users feel its outages too. Point a Site Qwality monitor at the Cursor endpoint you use and at your own site, and we alert you on Slack, email, SMS or a webhook as soon as either one stops answering.