Cursor Status
Cursor service notices; distinguish provider-side problems from a particular local project or extension error.
Live Domain Check
Is Cursor Down? Check cursor.com Status and Outages
Run a live reachability check for cursor.com. Compare the regional responses with the problem you see in Cursor.
Find Cursor help and reporting links, specific checks, and step-by-step guidance below the live result.
Ready
Running automatic check…
Checking reachability from multiple regions.
Checked
-
Verdict
-
Response Time
-
Final URL
-
Regional checks
Is Cursor working for you?
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
Past 24 hours15-minute totals · current interval in progress
Most reported problems
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
Understanding Cursor connection and service problems
Cursor editor operation, account access, model requests and a remote development environment can fail independently.
The checker above requests cursor.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Cursor action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Looking for another service? Browse AI service checks.
Cursor status information and official help
Cursor help and reporting
The official support forum is public; remove private source code and secrets before posting.
Open cursor.com
Open the website in your browser and compare it with the result above.
Where to report problems with Cursor
Open Cursor help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.
Details to include in your report
Cursor version, OS, model/mode, request/error identifier and whether the workspace is local or remote.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to Cursor.
What to check when Cursor is not working
These are troubleshooting comparisons, not claims that Cursor is currently experiencing a particular incident.
Start with the action that failed
Check whether editing local files works while AI requests fail, then compare a small non-sensitive request.
Narrow down the affected service
Inspect Cursor's status and official support forum for the matching symptom; record extension/remote-environment errors separately.
Read the actual checker response
A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
How to check if Cursor is down
- Save the error. Note what you were doing and when it failed. Save unfinished work before refreshing.
- Run the cursor.com check. Look at the regional results and when they were checked. Checking again may return a cached result.
- Check for a service notice. Open Cursor status and check whether the named service and incident time fit your error.
- Try another browser or network. Use the specific checks above to narrow down the problem. If it continues, send the error and time through the official help link.
If Cursor Is Not Working Only For You, Start Here
Use these local troubleshooting steps after the down-check workflow when Cursor seems broken only for you. This section focuses on app, browser, account, and network fixes.
1. Compare browser sessions
Open cursor.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
2. Preserve a working account session
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader Cursor issue.
3. Try another network
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
4. Capture support-ready evidence
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Cursor support.
Frequently asked questions about Cursor problems
Is Cursor down, or is the problem limited to one feature?
Run the cursor.com check and compare its original timestamps and responses with your actual error. Cursor editor operation, account access, model requests and a remote development environment can fail independently.
Where can I report a problem with Cursor?
Use the community buttons on this page to share whether the service works for you. For help from Cursor, use the official help/reporting resource linked above. The official support forum is public; remove private source code and secrets before posting.
What should I check first when Cursor is not working?
Check whether editing local files works while AI requests fail, then compare a small non-sensitive request. Inspect Cursor's status and official support forum for the matching symptom; record extension/remote-environment errors separately.
What information helps Cursor support investigate?
Cursor version, OS, model/mode, request/error identifier and whether the workspace is local or remote.