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.
Very interesting. So the VPN that comes with Google one is useless lol. The first time I connected it routed me through Google (like it's supposed to), then through an ad network (!), then on my way. Switching it on and off half a dozen times for additional tests, it just didn't bother routing through Google at all, just straight through my wireless carrier and showing the same user IP each time. So neat.