Closed wroldjiucai closed 1 year ago
A traceroute from NYC server confirms they are not in NYC:
2 vl202.nyc-tlx3-core-2.cdn77.com (185.229.188.174) 0.316 ms vl201.nyc-tlx3-core-1.cdn77.com (185.229.188.170) 0.320 ms 0.408 ms
3 * * *
4 be3362.ccr41.jfk02.atlas.cogentco.com (154.54.3.9) 1.244 ms 0.965 ms be3363.ccr42.jfk02.atlas.cogentco.com (154.54.3.125) 0.766 ms
5 be2889.ccr21.cle04.atlas.cogentco.com (154.54.47.49) 13.027 ms 12.832 ms *
6 be3157.rcr71.buf02.atlas.cogentco.com (154.54.47.126) 17.248 ms be3156.rcr71.buf02.atlas.cogentco.com (154.54.29.202) 17.016 ms be3157.rcr71.buf02.atlas.cogentco.com (154.54.47.126) 16.975 ms
7 te0-0-0-8.nr01.b015478-3.buf02.atlas.cogentco.com (154.24.4.46) 17.693 ms te0-0-0-22.nr01.b015478-3.buf02.atlas.cogentco.com (154.24.4.50) 17.934 ms te0-0-0-8.nr01.b015478-3.buf02.atlas.cogentco.com (154.24.4.46) 17.883 ms
8 * * *
9 64.44.41.41 (64.44.41.41) 21.536 ms 21.339 ms *```
Hi Sir, It looks like some of the geolocation sites have not pulled the update yet.If you check services such as ipgeolocation, ip2location, and maxmind directly, you can see they have the updated information already. Some services do not pull updates very often,I asked my hosting company and they said it might take some time for a full update, thanks a lot, thanks a lot
The geolocation information from various databases are not the source of truth. The physical location and the latency is what matters. And the IPs are in Buffalo, NY. Not in NYC.
IP:64.44.41.41, 64.44.41.42, 64.44.41.43, 64.44.41.44, 64.44.41.45, 64.44.41.46,64.44.41.47,64.44.41.48,64.44.41.49,64.44.41.50 Coordinates:40.71455(lat) / -74.00714 (long) City:New York Region:New York (NY) CountryUnited States (US) Country Code:10002 Hello, please check again, the hosting company has helped me transfer the server to New York, and the ip shows that it has been relocated