Use the perfSONAR list of traceroute/ping servers. It is at: http://132.160.6.186/toolkit/gui/perfAdmin/directory.cgi#PING. This provide a list of IP names/address that host traceroute/ping servers. Then add to the perfSONAR toolkit host name (e.g. 192.41.236.35 or 2001:e10:3c00:3:5054:ff:fe12:ee41) the following
<perfsonar-toolkit-host>/toolkit/gui/reverse_traceroute.cgi?target=<target>&function=ping |
to create a URL: http://192.41.236.35/toolkit/gui/reverse_traceroute.cgi?target=www.upenn.edu&function=ping. The output should appear as below:
One can also simply go to the web site (e.g. http://209.129.246.135/, it will direct to http://209.129.246.135/toolkit/) and view the information for the node. Unfortunately some nodes do not respond, for others although Latitude, Longitude is in the table the value is not entered. Some work, see below for an example:
One could search for the string <td>Latitude,Longitude</td><td>-41.28131,174.77575</td> and extract the lat/long.
Most PingER monitoring sites have a traceroute/ping server. This is the same server CGI script (with a different URL) as the perfSONAR server CGI script so the output is the same. The URL for the PingER ping server is
<pinger-host>/cgi-bin/traceroute.pl?target=<target>.edu&function=ping |
This creates a URL of the form http://pinger.arn.dz/cgi-bin/traceroute.pl?target=www.slac.stanford.edu&function=ping
We use the Planetlab scriptroute service via the TULIP reflector.