Api2.cursor.sh down: Cannot login to Cursor

Bug Reports
1

https://status.cursor.com/ shows no downtime but ping api2.cursor.sh return the following:

PING api2.cursor.sh (35.172.8.11): 56 data bytes

Request timeout for icmp_seq 0

Request timeout for icmp_seq 1

Request timeout for icmp_seq 2

Tried to login but after clicking on the sign in button, it triggers a lot of pending requests to /auth/poll

Screenshot 2025-02-22 at 21.33.13
Screenshot 2025-02-22 at 21.33.131115×1180 230 KB

2

Can log in now, but indexing stuck at 0% with a lot of errors:

Screenshot 2025-02-22 at 21.44.40
Screenshot 2025-02-22 at 21.44.401920×1225 242 KB

3

it’s not a bug, it’s a feature:

4

Hey, just to clarify, api2.cursor.sh does not return pings, so that would not work.

Are you still seeing issues here?

5

Thanks, it’s working now after some time. A couple of suggestions:

  1. Please be more careful with updates. My issue started right after upgrading to Version 0.45.14. Not sure if it was the cause, but it feels like Cursor could use more thorough testing before shipping new versions.

  2. The Status page should be more transparent. It always looks green, but in reality, there are a lot of glitches, if not actual downtime.

Just some thoughts from a user who’s still on the fence. Transparency and reliability go a long way.

1 Like
6

I had the same issues, that the connection to cursors servers were blocked due to certificates not being accepted.

i found that dns lookups shoed different ips for the domain ap2.cursor.sh than if i used googles name server.

➜  ~ nslookup api2.cursor.sh        
Server:		192.168.2.1
Address:	192.168.2.1#53

Non-authoritative answer:
Name:	api2.cursor.sh
Address: 18.210.181.23
Name:	api2.cursor.sh
Address: 34.231.115.189
Name:	api2.cursor.sh
Address: 34.225.57.63
Name:	api2.cursor.sh
Address: 34.202.168.86
Name:	api2.cursor.sh
Address: 34.196.7.7
Name:	api2.cursor.sh
Address: 52.7.76.48
Name:	api2.cursor.sh
Address: 3.221.237.231
Name:	api2.cursor.sh
Address: 54.236.139.253

➜  ~ nslookup api2.cursor.sh 8.8.8.8
Server:		8.8.8.8
Address:	8.8.8.8#53

Non-authoritative answer:
Name:	api2.cursor.sh
Address: 54.85.239.103
Name:	api2.cursor.sh
Address: 35.153.137.144
Name:	api2.cursor.sh
Address: 54.163.171.118
Name:	api2.cursor.sh
Address: 34.233.16.224
Name:	api2.cursor.sh
Address: 44.211.1.198
Name:	api2.cursor.sh
Address: 35.172.245.167
Name:	api2.cursor.sh
Address: 54.210.173.142
Name:	api2.cursor.sh
Address: 3.214.133.223

➜  ~ nslookup api2.cursor.sh 1.1.1.1
Server:		1.1.1.1
Address:	1.1.1.1#53

Non-authoritative answer:
Name:	api2.cursor.sh
Address: 35.172.245.167
Name:	api2.cursor.sh
Address: 54.86.152.169
Name:	api2.cursor.sh
Address: 35.153.137.144
Name:	api2.cursor.sh
Address: 44.218.155.151
Name:	api2.cursor.sh
Address: 34.233.16.224
Name:	api2.cursor.sh
Address: 44.211.1.198
Name:	api2.cursor.sh
Address: 54.163.241.212
Name:	api2.cursor.sh
Address: 54.163.171.118```

when i added googles 8.8.8.8 dns server to my mac settings, (as well as cloudflares 1.1.1.1) everything started working again.

and the lookup also return the same ip addresses.

➜ ~ nslookup api2.cursor.sh
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
Name: api2.cursor.sh
Address: 54.86.152.169
Name: api2.cursor.sh
Address: 35.172.245.167
Name: api2.cursor.sh
Address: 3.227.202.252
Name: api2.cursor.sh
Address: 34.195.126.113
Name: api2.cursor.sh
Address: 54.209.76.134
Name: api2.cursor.sh
Address: 18.211.45.51
Name: api2.cursor.sh
Address: 34.233.16.224
Name: api2.cursor.sh
Address: 50.17.119.86

➜ ~ nslookup api2.cursor.sh 8.8.8.8
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
Name: api2.cursor.sh
Address: 54.210.173.142
Name: api2.cursor.sh
Address: 52.7.165.190
Name: api2.cursor.sh
Address: 54.85.239.103
Name: api2.cursor.sh
Address: 34.233.16.224
Name: api2.cursor.sh
Address: 44.195.214.117
Name: api2.cursor.sh
Address: 3.227.202.252
Name: api2.cursor.sh
Address: 50.17.119.86
Name: api2.cursor.sh
Address: 18.211.45.51

➜ ~ nslookup api2.cursor.sh 1.1.1.1
Server: 1.1.1.1
Address: 1.1.1.1#53

Non-authoritative answer:
Name: api2.cursor.sh
Address: 54.86.152.169
Name: api2.cursor.sh
Address: 44.218.155.151
Name: api2.cursor.sh
Address: 35.172.245.167
Name: api2.cursor.sh
Address: 52.7.165.190
Name: api2.cursor.sh
Address: 54.163.241.212
Name: api2.cursor.sh
Address: 54.210.173.142
Name: api2.cursor.sh
Address: 35.153.137.144
Name: api2.cursor.sh
Address: 44.211.1.198

 

Now the main question is, are those ip addresses just "old" ip addresses that the dns server that isps had was not being updated fast enough and thus the certificate matching did not pass.

or is something complromised somehwere, amalware somewhere that was spoofing the domain.
i can imaging cursor users being delicious targets for hackers esp when there is the possibility if you could hijack instructions coming from an agent that has access to your filesystem and can run commands on your machine.