I am waiting almost same time with response time my waiting time doubles, slow is ok but this is too slow
5 Likes
yeah, too bad
2 Likes
Similarly, I found that cursor now fixes the slow request setting for claude 3.7 models to take 90 seconds to start responding. This is really too bad.
5 Likes
I totally get it! Typically, I get faster responses around 3-4 AM my time in Europe, but during work hours, it can sometimes take up to 5 minutes to get a reply, which can be a bit frustrating. Honestly, I’d even be willing to pay an extra $50 if it meant I didn’t have to deal with such slow response times like I’ve been experiencing recently. I know I could switch to usage-based requests, but that would cost even more, and I don’t think there are many usage-based customers causing the delays. It seems like the trial account users might be the ones causing the bottleneck!
1 Like
Hey, the slow request time should be the same as it has been for a while, but it is true that the more you use, the slower they get!
Unfortunately, we have to prioritise and protect the needed capacity to serve the fast premium requests, and to do this, we have to queue the slow requests to ensure we can serve everyone as best as we can.
While we are always monitoring this in a hope that we can shorten the slow queue time when we are confident fast requests are never affected, the only solution for now would be to either:
- use the usage-based pricing feature to purchase and use additional fast requests
- try to use other, non-premium models more often, to spread out your fast requests to last longer / only be used when necessary
1 Like
From what you’re saying, it seems that while “slow requests” are mentioned as option after fast requests are gone, it’s not clearly stated that they get progressively slower with increased usage (at least I didn’t come across that information). It would be great if this was clarified, especially how the system tracks the total number of requests and how slowness increases over time.
2 Likes
Guys you need to find a path for premium unlimited for an ok price. I’d be willing to go 40-50 bucks on premium unlimited, but if slow pool is like exceedingly slow then effectively cursor becomes useless after a day or two for a pro that’s using it as a work tool. Paying for usage based 300-400 bucks a month is insane. This is the kind of stuff which will alienate users. I am seriously looking at augment code now which for the time being is unlimited. The one who can offer Sonnet like quality in agent mode on an unlimited basis for a feasible price will win this coding war. Cursor has become unuseable beyond the 500 limit and 500 usage based is just too expensive.
2 Likes
Could you have a look at the documentation?
Wait times in the slow pool are calculated proportionally to how many slow requests you’ve used, so they generally remain manageable unless you’re well over your fast request limit.
They were clear about this and explained it many times here in the forum as well.
2 Likes
I truly hope issues like this can be addressed promptly. Cursor stands out as a pioneer in AI-driven coding—offering one of the most comprehensive experiences at a relatively affordable cost.
However, it’s important that the quality of the features matches the promise. While we deeply appreciate the vision and innovation, it’s crucial that advertised features function as expected. Otherwise, even with good intentions, users may begin to feel misled or disappointed when core features fail to deliver reliably.
We look forward to improvements and continued excellence in the development of Cursor.
It’s too slow! It’s really slow! I really don’t know what the point of this pro is other than waiting for 4-5 minutes for each answer after using the full version for 1-2 days.