Started working at 7:00 CET, and Sonnet 4.5 is running fast for the first time in days.
Had 4 updates over the past 2 days.
I also discovered that a bug that was in an early version of Cursor has reappeared. The “Unable to reach model provider” error seems to happen very often in longer chats (although the context is not at all full). If I change to a new chat, it works. I remember this happened over a certain time in a past version (maybe a year ago?).
It definitely seems to be better, especially after upgrading to 2.1.19 on Linux, which arrived overnight. I remain surprised that Cursor didn’t treat this as a degraded service issue; their official status page for the last few days is squeaky clean.
@deanrie :
@deanrie : Hey deanrie, the error keeps persisting, but after testing it for a few days i think i have narrowed down the follwing:
Sonnet 4.5 = the error appears almost all the time
Gemini3 Pro = the Error appears after the agent runs sometime
MCP = If MCP is activated, the error appears way more often AND especially since i use the MCP Toolkit from Docker Desktop, with 50+ Tools in one MCP Connection the speed of the models is degregaded.