Cursor "Connection failed": causes and fixes
Is there an outage right now?
Cursor official status is operational. If this error persists, it is likely an implementation or environment issue on your side.
View Cursor status →What this error means
Cursor cannot reach its servers/models. Causes include network, corporate proxy/firewall, VPN, expired auth, or a Cursor-side outage.
Common causes
- •Unstable network or offline
- •Corporate proxy/firewall blocking traffic
- •Blocked via VPN / zero-trust
- •Expired login/auth
- •Temporary Cursor-side outage
How to fix
- 1.Check your network connection
- 2.Set the HTTP proxy correctly in Cursor settings
- 3.Allow cursor.com and model APIs in firewall/VPN
- 4.Re-login
- 5.Restart Cursor
- 6.Check status at the top of this page
When waiting helps (and when it won't)
If Cursor-side, it recovers over time. Most cases are your own network/proxy config—waiting will not help, so check the above.
Alternatives when Cursor is down
Related errors
FAQ
What is Connection failed?
Cursor cannot reach its servers/models. Causes include network, corporate proxy/firewall, VPN, expired auth, or a Cursor-side outage.
How do I fix Connection failed?
Check your network connection / Set the HTTP proxy correctly in Cursor settings / Allow cursor.com and model APIs in firewall/VPN / Re-login / Restart Cursor / Check status at the top of this page