Requests are just getting bounced/failed connections it looks like.
4 Likes
yes it is
If you refreshed the page and clicked the status page, you would see it.
It’s crazy with all these outages lately
Just as i was about to do some work. Let’s have a break then.
Seems that Claude is also affected
1 Like
In the Cursor Settings > Network, if I change to HTTP/1.1 or HTTP/1.0, the Agent and Chat diagnostics pass again and I can use the chat. If it’s HTTP/2, then Agent and Chat fail and I cannot use them.
7 Likes
ty dude
While it is down:
All should be fixed now - sorry for any inconvenience!
Feel free to switch back to HTTP/2 as the slightly quicker and lower overhead service.
1 Like
Yes it’s down!
this worked, thanks!
everything was down. cursor itself must default to http/1.1 when it loses connection.
I mean forum was also down.
What was the problem?
aws down, cursor relies on aws
Cursor 1.7.54 is fckng slow right now. Cheetah needing 30s until first token(?).
我的天，没中文？