Is Cursor AI Down? Live status & outage reports

Service info and troubleshooting

Editor fails to launch or crashes

If the application won't start or closes unexpectedly, check your system resources first. The editor requires at least 4GB of available RAM to run smoothly. Close other heavy applications and try again. On Windows, running as administrator sometimes resolves permission-related crashes. Mac users should verify the app has necessary accessibility permissions in System Preferences. If crashes persist, delete the .cursor folder in your user directory and reinstall.

Code suggestions stop appearing

When autocomplete stops working, the AI connection likely dropped. Check your internet connection stability. The service needs consistent bandwidth to stream suggestions. Try toggling the AI features off and back on through settings. Sometimes the model context gets overloaded with large files—close unnecessary tabs and restart the editor. Verify your API key hasn't expired in account settings.

High latency during code generation

• Reduce the size of files you're working with. Large codebases slow down response times
• Check your network ping to verify connection quality
• Clear the editor cache through settings to remove accumulated data
• Limit the number of open project folders
• Disable unused extensions that might interfere with performance

Authentication errors when logging in

If you can't sign in, clear your browser cookies and try authenticating again. The OAuth flow sometimes breaks with cached credentials. Check if your firewall blocks connections to cursor.sh domains. Corporate networks often restrict authentication endpoints. Try switching networks temporarily to isolate the issue. Password reset emails might land in spam folders—check there before requesting another reset.

File indexing gets stuck

The indexing process can hang on large projects or when encountering corrupted files. Restart the editor and let it re-index from scratch. Add problematic directories to .cursorignore to exclude them from scanning. Node_modules and vendor folders should always be excluded—they contain thousands of files that aren't needed for suggestions. Check available disk space, as indexing requires temporary storage.