Resolved
Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
A bug message should not advise me to “upgrade to Pro” if I am already on Pro.
Steps to Reproduce
This only manifests when Cursor’s infrastructure is under load.
At which point, I get the error:
“We’re experiencing high demand right now. Please upgrade to Pro or try again in a few moments.”
I’m already on a Pro account. The error message shouldn’t advise me to upgrade to Pro under such circumstances.
Expected Behavior
An error message that just apologises ![]()
Screenshots / Screen Recordings
Operating System
MacOS
Version Information
Version: 3.12.30
VS Code Extension API: 1.128.0
Commit: 63a2996a10d9e476b6c28e951dd7691d9c0cf480
Date: 2026-07-21T22:50:03.568Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Darwin arm64 24.6.0
For AI issues: which model did you use?
Auto
Additional Information
Please note that this is NOT about the underlying issue that caused the service overload. This report is only about the inappropriate wording on the error message.
Does this stop you from using Cursor
No - Cursor works, but with this issue
same btw. this happened at a very inopportune moment..
Hey @zoltan_bango @hiram_abi @Laura_Avila, what you’re describing (your account switching to Free, missing payment history, and a refund for unused time) is different from the original issue in this thread and is related to subscription and billing for a specific account. We don’t handle those cases on the forum.
Please email us with details at [email protected].
Hey everyone, quick update on this thread.
We fixed the wording of the High Load message on our side. Paid plans Pro, Pro+, Ultra, Teams, and Enterprise will no longer see “upgrade to Pro” when a request gets rejected during high load. This change is already live, so you don’t need to update anything.
That said, the High Load message can still show up briefly during demand spikes. As mentioned above, this is expected. It usually helps to retry after a few seconds, or pick a specific model instead of Auto, for example Composer 2.5.
If you’re on a paid plan and you still see “upgrade to Pro”, please share a recent Request ID here and we’ll take a look.


