Traceroute Mapper – Show Your Traceroute on a Map
11–20 of 36 posts
Re: Traceroute Mapper – Show Your Traceroute on a Map
#12Neat. Just curious, why do I need to turn off ublock for this to work?
Re: Traceroute Mapper – Show Your Traceroute on a Map
#13Is it possible to make this a local app so you don't have to use the web?
Re: Traceroute Mapper – Show Your Traceroute on a Map
#14Love this! "ipinfo.io ratelimit exhausted. Please try again tomorrow, or run the script from your own server." Needs a port to Linux (from .bat).
function traceroute-mapper { xdg-open "http://stefansundin.github.io/traceroute-mapper/?trace=$(tra... -q1 $* | sed ':a;N;$!ba;s/\n/%0A/g')" }
Re: Traceroute Mapper – Show Your Traceroute on a Map
#15I remember a Windows tool that used to do this, like 15 years ago. I remember using it and getting quite fascinated.
Re: Traceroute Mapper – Show Your Traceroute on a Map
#16Neat. Just curious, why do I need to turn off ublock for this to work?
Re: Traceroute Mapper – Show Your Traceroute on a Map
#17Re: Traceroute Mapper – Show Your Traceroute on a Map
#18I remember a Windows tool that used to do this, like 15 years ago. I remember using it and getting quite fascinated.
Re: Traceroute Mapper – Show Your Traceroute on a Map
#19Neat. Just curious, why do I need to turn off ublock for this to work?
Hi Dave. Because of overzealous filters, unfortunately. The "EasyPrivacy" seems to block the whole ipinfo.io domain if it's included as a third-party request.
Not sure what's going on.
Re: Traceroute Mapper – Show Your Traceroute on a Map
#20The following shows up at Fremont but it should be NYC, right? 7 100ge10-1.core1.nyc6.he.net (184.105.64.178) 10.344 ms 9.712 ms 20.411 ms
Yes this is the disadvantage of traditional IP geolocation databases. They work mostly by sourcing information from RIRs and ISPs. Unfortunately for a lot of larger organizations which typically exist in internet backbone that is very inaccurate. This skews the traceroute mapping significantly. I don't want to shamelessly plug-in stuff here but we have geolocation API which uses latency triangulation and does not suf…
Who is "we"? I'd like to test drive a service like that.