Unable to reach Anthropic March 2025

Bug Reports
1
• Issue: macOS Cursor repeatedly shows “Anthropic down” error.
• Status Check: status.anthropic.com and status.cursor.com reports all systems operational.
• Action Taken: Clicking “Try Again” continuously fails.
• Internet Check: Confirmed not an internet issue—tested on 3 stable networks.
• Current Plan: Exceeded max usage; now on usage-based billing.

using sonnet-3.7

update: it seems related to: Rolling Back to 0.45 - #7 by Benjamin so you would have to do a rollback. which i don’t want to do because too much effort.

temporary fix is to use 3.5!

8 Likes
2

Same here, pro user, fast requests.

image
image488×110 7.74 KB

3

+1.

image
image523×159 12.3 KB

4

ive been trying for 2 hours, burning like almost 50 fast requests

1 Like
5

I stopped after 2 requests failed when I noticed it still counted, it should not count, they supposedly fixed that.

2 Likes
6

Same issue here. Tired of it now.
Fails to connect to Anthropic.
I gave up after clicking resume too many times.
Went back to Sonnet 5.

7

I am having this issue. I have probably wasted 50 fast requests. What is going on and why is the cursor team at least responding to our cry for help?

8

+1

image
image668×686 2.5 KB

Also doesn’t work on sonnet 3.5, and gpt 4o and 4.5 are reaalyy slow

9

I’m also facing same issue from past two hours. I have pro account as well.

image
image949×270 82.6 KB

10

Getting the same error often.
All of you should check if you get charged for these.
I found out I get charged for every failed request. Not cool.

1 Like
11

Thanks for the tip! How do we know which request is billed and which isn’t ?

12

Sadly I don’t think we can see that. I just found out today when i had like 5 requests in row fail and I saw the billing amount in my dashboard go up with every click.

13

Same here. The only way i made it work is cmd+shift+p > Reload Window, and as soon as window reloads clicking send button and sending prompt. But it only works once. You have to do reload window and rush out to send prompt every time. That’s not even a workaround. So waiting for a fix.

14

Update: I was getting this error every time. I was not getting any response at all.

I managed to get rid of this error by disabling MCPs. I had 4 MCPs enabled. Disabled 2 of them. And it did the job.

15

I had the same experience, I got 9~10 MCPs, after disabling them all, Clause 3.7 wakes up again. There are too many bugs to get a clue, when I quote codebase in an Ask, Claude fails again.

16

I have 0 MCPs and still get this failure on a daily basis.

17

Same. It’s almost totally unusable.