How to locate a server geographically from URL

ke flag
P i

In order to minimize latency for HTTP GET/POST requests, I want to setup a linux box near the server.

Suppose for example the server is

I've tried with traceroute and whois. i.e. running traceroute in theory returns the ip of each hop, and I should be able to whois on the latter hops.

But in practice traceroute returns line after line of hidden IPs before quitting:

> traceroute
traceroute to (, 64 hops max, 52 byte packets
 1 (  1.128 ms  0.574 ms  0.889 ms
 8 (  182.163 ms (  202.120 ms (  181.422 ms
 9  * * *
10  * * *
63  * * *
64  * * *

And as I understand whois is hit and miss as:

The Internet Assigned Numbers Authority (IANA) handles splitting all the IPV4 and IPV6 addresses to 5 different Regional Internet Registries (RIR).


Is a request to always going to land at the same physical server? And if not, how is this decided?

Would it help to make an actual HTTP GET and somehow inspect the packet routing?

Is there some science to this? Or is it an impossible task?

vn flag
Whois won't work for this; Google IPs may geolocate to California even when they're physically located in Australia. Fire up VMs at several different locations (AWS is good for this) and benchmark latency.
P i avatar
ke flag
P i
Great! I found online tools like that give a rough indication (i.e. I can see is somewhere in the USA)

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.