When attempting to use model 3.7 sonnet or 3.5 sonnet, the following message appears: “Your request has been blocked as our system has detected suspicious activity from your account.”
(Request ID: f62d2aef-3d18-45a9-aaa6-79ed757d284c)
When attempting to use model 3.7 sonnet or 3.5 sonnet, the following message appears: “Your request has been blocked as our system has detected suspicious activity from your account.”
(Request ID: f62d2aef-3d18-45a9-aaa6-79ed757d284c)
I think we’re all experiencing the same thing — I believe it’s a cursor error. I’m not using a VPN. I have two cursor windows open, one for front and one for back. In the back, Claude 3.7 works perfectly, but in the front it doesn’t. However, if I switch to 3.5 or to automatic, it works fine. It makes no sense.
same here, as a student I just applied for a one year free trial of cursor pro. I got this message while I was doing my course project.I don’t know why cursor did this.My application was totally valid and such block really badly affected my course project
For the same problem, I didn’t perform any abnormal operations.
Your request has been blocked as our system has detected suspicious activity from your account.
Facing the same issue from past 5-6 hours
Description - When we use claude-3.5-sonnet, claude-3.7-sonnet it directly gives - “Your request has been blocked as our system has detected suspicious activity from your account.”. If we use gemini-2.5-pro, gpt-4.1 the coversation continues a little bit but when there is function calling for editing the files it gives this error - “We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.”
To reproduce - Install CursorUserSetup-x64-0.50.5 and try to use the above discussed models.
Versions - cursor: x64-0.50.5, operating system: Windows-11 24H2 for x64-based Systems (KB5058411)
The issue is increasingly affecting my ability to use Cursor effectively. The unresponsive cursor and recurring bugs interrupt my daily workflow. I’ve had to switch to alternative tools on several occasions because certain features became unusable or too unstable to rely on.
It’s becoming difficult to depend on Cursor as my main development environment, and this is disappointing given how promising and productive the platform used to be.
Yea also getting this. I’m gonna send an email.
Also having the same issue. Thought it as because I had a free account.
I have just give one prompt to grmini 2.5 and then came back to claude not it work fine.
Facing the same issue for past few hours with my 1 year subscription student account while I was working on a project. It’s frustrating. I have sent email, but no reply from them yet.
tooooooo
same problem
Also having the same issue.
Same issue here. Sent them a email.
Sent an email, and they reply :“try to create a new account and sign Cursor Pro”, although I’m using Pro Subscription with a student discount ![]()
I got same error. And wow you have student account pro subcription ?
Ya, I’m a Senior student. I tried with free account but It has same issuse.
same issuse
Dear Support Team,
I am a university student using the free tier of your services. Recently, whenever I attempt to use either the Claude 3 Sonnet model or the Claude 3.5 Sonnet model, I consistently receive the following error message: “Your request has been blocked as our system has detected suspicious activity from your account.”
This is quite perplexing as I believe my usage has been normal, and I can confirm that I still have available tokens in my account. Despite having tokens, I am unable to access these models due to this block.
Tip & trick to solve temporary : You can first request with deepseek and enter prompt later with claude or other models
Hey all, we’ve been attempting to crack down on fraudulent use of Cursor over the past 24-48 hours, as for a short while, this detection was overly sensitive, causing some false positives.
We have now tuned this down, so you should no longer be seeing any issues here!
If you are, try tweaking your prompt to ensure you aren’t sending the same request over and over.
Apologies for the inconvenience here!