We’re experiencing high demand for Composer 2.5 right now. Please switch to Auto, another model, or try again in a few moments.
Encountered the same issue
Auto is working for me, but seems much slower than usual.
Hey, thanks for the report. This message isn’t a bug, it’s a temporary high load. When demand for Composer 2.5 is higher than available capacity, some requests slow down, and you see this screen.
What you can do:
- Switch to Auto or another model. Auto usually works, even if it can be a bit slower during peak times, like one user mentioned above.
- Or try again in a few minutes. These spikes are usually short.
This is expected during peak load and we’re monitoring it. If you keep hitting this for a long time, not just a one-off spike, let me know which models you used and what time it happened, and we’ll take a closer look.
is there any status checking website so that we can see the live data of usage of composer 2.5?
same here
same but i cant use auto even.
peak hours after midnight?
I am using cursor CLI on WSL and have the same problem now
Hey, I’ll answer a couple questions from the thread.
@jackylo.hc: You can see the live system status at https://status.cursor.com. It shows overall service health and incidents. There isn’t a separate page showing live load specifically for Composer 2.5, but big capacity events will show up there.
@amp @qoomir: If even Auto hits high demand, it means the traffic spike is bigger than usual and affects multiple models at once. These spikes are usually short. Retrying in a few minutes helps, or switching to another model like Sonnet or GPT for now. The CLI on WSL uses the same fallback system, so it’s the same approach.
This is expected during peak load and we’re monitoring it. If anyone is seeing this consistently for a long time and it’s not just a one-off spike, let us know which models you used and the rough time with your timezone, and we’ll take a closer look.