it’s really slow in my case and I waited so long just to get one simply thing done.
20fac714-3057-4788-850a-a9f64c5431ca
Yes, I hit it too at 03-31 22:00~24:00
and no fixed
I’ve been using Opus 4.6 exclusively in normal mode for all my work.
Here are the Request IDs from the slow sessions:
b2d48fdc-f435-404a-8eca-c97e5efbe371, f9a38c96-1b1a-4ea6-b975-7b5d47dcce34
Here are the Request IDs from the slow sessions:b2d48fdc-f435-404a-8eca-c97e5efbe371, f9a38c96-1b1a-4ea6-b975-7b5d47dcce34
When will this issue be fixed? Opus is unusable.
1 Like
We will continue monitoring for latency, but we believe the issue causing the slowness reported in this thread has been resolved. In addition to our ongoing monitoring, we haven’t received any new reports on this thread since last week.
I would prefer to close this thread now, as any future performance issues would be better tracked in a new, dedicated thread. Before doing so – @enragedcamel, @ahhxyz, @John_Bush @Abdelrahman_Mohamed @jjukl , @jjukl, @midaz, @KGF, @Bryan_Jenson, @swagoo, @Prince, @heavy_user – how’s performance looking? Any lingering issues on Opus? If yes, please provide a new Request ID!
Hello, the issue is still completely persisting on my end: 824b9662-db66-4516-bf60-c834a98d8b85
All the requests I’ve made to Claude over the past few days have been extremely slow: 20+ minutes to make fixes it would normally have handled in under a minute.
The output quality has also been affected. I’ve seen it go into endless reasoning loops instead of simply applying what I asked.
I use Auto mode most of the time, and it works very well, but Claude can use the browser. Still, none of the requests I’ve made to it over the past week have produced good results.
Performance is still slow for me, Colin.
It would be nice to know whether it is on the Cursor side, or on the Anthropic side. What has your troubleshooting shown you?
Hello, everything ‘s got back to normal now. Opus 4.6 max is back to best performance since yesterday. Thank you 
1 Like
Closing this topic since the original issue reported is resolved. For future performance issues, please raise a fresh thread!