Before you start

Editor sign-in, model requests and extension downloads follow different paths.

Step by step

  1. Check the official status or announcement page at https://status.cursor.com/. A help page is not necessarily a live status monitor.
  2. Reproduce the Cursor issue on one exit and record its time, code, stage and duration.
  3. Reproduce a small completion and record the model, time and redacted diagnostic error code.
  4. Compare wired, Wi-Fi or another network while changing only one condition.
  5. If the app is slow but the browser works, compare app and system proxy settings for duplication.
  6. Editor sign-in, model requests and extension downloads follow different paths.

Official references

Use these provider resources for current rules. Some announcement links are help pages, not live availability tests.

Common questions

Can switching networks fix every Cursor error?

No. Account privileges, subscriptions, file permissions and service outages require separate checks.

What should I send to support?

Share the time, client version, redacted error code and minimal reproduction. Never share a password, token, cookie or one-time code.