My SF2 droplet IP has trouble being identified as west coast by Geo DNS services
In US I have one droplet on SF02 and one in NYC1.
SF02: IP Address IP Address (float IP)
NYC1: IP Address IP Address (float IP)
I tried setting GEO dns by both amazon route53 (latency based) and also Cloudns (geo based), they both have problems identifying this IP as being on us west coast.
I ping my host (www.domain.com) from multiple locations and when a client is pinging from Los Angeles (under 10ms from SF02 IP), it gets sent to the NY ip as being the closest one, NY being on the other coast, 60ms away.
This also causes the server to get less traffic, for example Google Bot never visited that SF02 server even if it is online for over a month. The other IPs get around 4-5 times more traffic.
What could be wrong ? Is the SF02 using a less reliable ISP ? Is there an ISP or route associated with the SF02 IP that is more related to Asia region than the US west coast ? Because I also see some Asia region users hitting the SF02 IP, maybe even more than US users.
Not sure if getting a droplet in SF01 (currently unavailable) would behave different than SF02. Anyone knows any network/IP differences between SF01 and SF02 ? Maybe different ISP or latency/bandwidth ?