Oh my god please, Gemini 2.5 pro and Claude 3..7 sonnet response too slow, very slow with slow request:(
2 Likes
Yes, it’s really ridiculous. It takes up to 2 minutes to get an answer. Perfect when you add the other bugs where the edit fails or the output simply stops… and you spend minutes trying to get a correctly executed response.
2 Likes
No bro. It is 5 min. Real 5 min bro. Omg.
2 Likes
more than 5 minutes, i will cancel my pro plan.
1 Like
Yes, I have the same problem. Today, Cursor began to think for 4-5 minutes, sometimes more, before giving an answer.
I had the same problem 2-3 days ago.
Hey guys, unfortunately, if you are on slow requests, they will get slower the more you use them.
Slow requests were initially added to work as a backup, in case you run out of fast requests, but we always have to protect our capacity to ensure fast requests are always fast.
Significant slowdowns only occur when you are well into the 100s and 1000s of slow requests, in which case you are easily getting fantastic value for a $20/m plan.
The only way around this right now is to either use the free models more frequently, or to enable usage-based pricing.
3 Likes
It wasn’t like that before… your WdSf competitors have free requests for agents. it is quite possible to work with them for primitive tasks. What conclusion can be drawn?
2 Likes
Hit generate on a slow request almost 10 minutes ago and it’s still “Generating…”
This is what we’d refer to as an extortion tactic.
I’m on a PRO plan, so this move is trying to get me to pay even more money.
2 Likes
I’m a Pro user. Today after upgrading to version 0.50.5, claude-3.7 and gemini-2.5-pro stopped working properly. Sometimes they’re unresponsive, sometimes extremely slow, and now they’re constantly loading without any response at all. This is really disappointing.
2 Likes
I’ve been a PRO user on Cursor for months and honestly, never had a single complaint until now.
The last month has been rough. The platform is basically unusable. Feels like they care way more about making money than actually helping users. As soon as you run out of fast requests, you’re stuck waiting like 5-10 minutes for even the simplest reply, and half the time the answer is wrong or just missing context.
It really seems like they’re doing this on purpose to push people into buying more fast requests or upgrading to MAX, which costs even more. What’s even worse is that your fast requests get burned up automatically as soon as your subscription renews, so you don’t even get to pick when you want a quick answer. It’s like they want to annoy us with these long waits so we’ll pay extra just to get anything done.
Let’s be real, 20 bucks a month isn’t enough for the amount of requests most people need. If that’s the problem, just offer new plans or something, but don’t treat loyal users like clowns making us wait 10 minutes for a half-baked answer just to push us into paying per request is a joke.
It’s honestly wild that in an hour, I can only get like 6-10 responses. At this point, I’d be faster just coding everything myself.
To whoever’s running Cursor: the market is moving fast, and your competitors are gonna steal your loyal users the second they offer something even a tiny bit better than what you’re doing now.
4 Likes
This feels like intentional extortion. Everything worked fine until today, and now the developer has confirmed this throttling is by design—and it will only get worse the more requests you make. According to him, users are “getting a fantastic value of fast requests for $20,” which basically admits this is a pay-to-escape system, intentionally making the wait unbearable to push people into usage-based billing, all under the guise of “protecting capacity” and “ensuring optimal speeds for fast requests.” (As if that’s actually been a major issue—spoiler: it hasn’t.)
This is a defining moment in their business lifecycle. A competitor is perfectly positioned to absorb Cursor’s user base, and many, myself included, are already researching alternatives. Cursor’s competitive advantage just died with version 0.50. What is their business strategy here? They certainly aren’t a cost leader with this broken and unfair usage-based billing model. What once set them apart from the competition is gone.
They’re at an inflection point: Cursor is about to become either just another forgotten app, or a first-to-market leader that continues to grow. The choice is in their hands—but right now, they’re pushing users away.
2 Likes
Some transparency around this would be great, like letting us know what tier of queue we’re in? And how long until we’re back in the normal slow queue.
I get what you mean @danperks, I also understand that businesses need to work to generate revenue effectively. But I want you and your business to know that I want a monthly subscription with lots and lots of slow requests in the 20-30 second range for a response. I accept it for more than $20. I don’t need 500 fast requests because they are useless and meaningless. I also want to confirm to you that I haven’t even reached 1000 slow requests and I’m already waiting 10 minutes for each request. Please!..