Hello, been using cursor for a few months now and have been loving it, but since yesterday it takes Claude like 3-5 minutes per response. Is this going to be how a slow request moves going forward? Or is this an issue that is being experienced?
Ah, guess it’s not just me.
Looking for a staff response on this please. There seems to be several of us having this issue.
same issue here. Even in usage-based pricing for premium models. Sonnet is very slow, and gemini not working anymore (might me related).
And the most frustrating to me : https://status.cursor.com/ everything’s fine 
I’m also wondering if the cursor will be like this in the future, and I’m going to consider whether to take out a subscription for the next quarter.
Me as well. This is so frustrating. It is just unfair that the non pro the free trial have fast request
Yes, recently, it might be due to that annual membership promotion activity, which has led to the response time of the 3.7 model becoming extremely long after the 500-time quota is used up. This is the case for both of my pro accounts after the quota is exhausted. Although I find Cursor very useful, if you implement it this way, you should either remove the slow-speed restriction for pro users or clearly inform me that I need to pay extra fees, rather than forcing users to pay by making the 3.7 model extremely slow. Even though Cursor might be operating at a loss currently, this practice is really unfriendly to paying subscribers. You could choose to disallow usage or explicitly state that additional payment is required, but you shouldn’t use this method to compel me to wait or pay. Although Cursor is currently irreplaceable to me, this approach makes me wonder if at some point you will exploit me. I am willing to pay for the official pricing and features, but I don’t want to be harvested like a leek.
Thanks for reporting this. You’re right that slow requests should not take super long if you are just over your 500 request limit - they should only take a few extra seconds at the start, not minutes or hours.
If you’re seeing response times longer than 1 minute, there might be something else going on. Could you help us investigate by:
You can find your request ID following these steps: Cursor – Getting a Request ID
This will help us figure out what’s causing these unusually long delays
For context on how slow requests normally work, check out: Cursor – Plans & Usage
hi
c6dac193-ed1a-49a5-baf2-29ef119605c7
Could you please check if this is correct? This is what I just requested.
I will not subscribe again after this month expires, but I will consider free editor. Currently, cursor’s Claude 3.7 is completely unusable at such a slow speed that I may wait for 4+ minutes before getting an error.
If you look two replies before yours the staff member said this is not normal. Don’t abandon cursor yet guys, let’s give them a chance to fix this.
When I get home from work today I will submit request id’s and share anything I can to help out with this.
Actually - here’s a request ID I was working in last night and having the issues @danperks
f1044c93-3d5c-42fb-a12a-b8b99a4b8cef
6fb3006c-0429-436e-9268-b6037874e344 this is my requestId
Here’s my request ID: 0abd5e02-554b-4aba-afff-eaf5de3cb96f
Thank you for trying to help us out. I really appreciate that.
Different computer, different version, same cursor account, same issue, new request ID.
82f81b33-2d12-4207-9cb6-5e5107e022f2
update: here’s another one from my first computer
304d94b4-4fee-44c8-83ba-0e9a341e1b07 - most recent (today 4/18)
Looking forward to this fix so I can go back to my cave 
Hi I hope this will help you:
Yeah it doesn’t seem to matter what version we are on either, just throwing that out there.
In the past few days, the experience with Claude 3.7 has been terrible — it takes between 2 to 5 minutes to get a response from the model.
it is very slow ,it so terrible for pro user.
Hopefully we’ll get an update from @danperks soon. Seems more and more people are registering on the forums for this. Doing my best to link them all back to here.
any status on this please…