A cool-as-shit dynamic traceroute powered by custom software, married with an informative article about how the BGP routing protocol works and guides the shape of the Internet.
My claim that this website’s traceroute was the path your packets took to reach my server was a bit of a white lie. To calculate that, I would’ve had to be able to run a traceroute to my server from your computer. Instead, I ran the traceroute from my server to your computer and just reversed it. That’s also why the traceroute at the top seemingly loads in reverse order.
If I run traceroute to this server I get totally different results, ips are similar, but always different.
It’s just a reverse traceroute:
If I run traceroute to this server I get totally different results, ips are similar, but always different.
To run traceroute on *nix:
traceroute how-did-i-get-here.net
You may have to install the
traceroute
packageOn windows:
tracert how-did-i-get-here.net