FAQ
| Question 1 |
This thing sucks, what a load of crap! How come it locates my computer in { the wrong city, the wrong state, the ocean, in the wrong country } ? |
| Question 2 |
Where do the maps come from? |
| Question 3 |
How do you figure out the latitude/longitude given the IP address? |
| Question 4 |
What part of the traceroute output do I cut and paste? |
| Answer 1 |
Well, yeah. This thing does kind of suck. It's for amusement purposes only, as I don't have access to (or the money to buy) an official up-to-date database of IP address and latitude/longitude mappings. So get over it. |
| Answer 2 |
I get the maps from Google, using the Google Maps API. |
| Answer 3 |
For IP addresses in the US and UK the heavy lifting is done by hostip.info. For other countries that do not have a good match in the hostip.info database I default to using the latitude/longitude of that country's capital city. Perfect? No, but you get an idea for where the packets are going. |
| Answer 4 |
Paste the part that enumerates the hops with an increasing integer in the left most column. For example:
1 isp (64.81.72.1) 18.392 ms 23.884 ms 22.773 ms
2 220.ge-0-1-0.cr2.sfo1.speakeasy.net (69.17.83.177) 21.694 ms
3 ge-4-0-440.ipcolo1.SanJose1.Level3.net (209.247.156.221) 18.995 ms
4 ae-1-51.bbr1.SanJose1.Level3.net (4.68.123.1) 25.495 ms
5 so-3-0-0.mp2.Stockholm1.Level3.net (4.68.128.70) 206.762 ms
6 4.68.96.226 (4.68.96.226) 205.678 ms
7 213.242.110.138 (213.242.110.138) 204.055 ms
8 SE-gw.RUN.net (193.10.252.150) 200.717 ms
9 msk-gw.RUN.Net (193.232.80.209) 224.436 ms
10 MSUnet.msk.RUN.Net (193.232.80.90) 220.896 ms
11 campus-core-G12-0-4.350.lion.msu.net (193.232.127.14) 225.506 ms
Alternatively just put each IP address you are interested in on a seperate line by itself. |
|
