Whether it’s a hotel lobby, a corporate guest Wi-Fi, or retail free Wi-Fi, I have a ritual that happens before I do anything else.
Before I toggle on my VPN or connect back to my home network via Tailscale, I’m pulling up a terminal to run a traceroute.
This isn’t just a geeky habit—it’s how I get a head start on knowing exactly how my VPN is going to perform. I need to see the “hops” and the raw path latency between my current location and my home servers before I introduce the overhead of a tunnel.
Why the pre-VPN traceroute? • Performance Forecasting: If I see high jitter or packet loss on the third hop, I already know why my remote desktop session might lag later.
• The “Northeast Loop”: Living in the Boston area, I see this constantly. I’ll be trying to reach my home lab just a few miles away, but the traceroute reveals my traffic is taking a 400+ mile round trip down to a New York City and back just to cross town.
• Peering Insights: I want to see how this specific ISP hands off traffic. Is the local network routing me through a weird gateway in another state?
Once I’ve mapped the route and satisfied my curiosity, then I flip the switch, the VPN goes up, and I disappear into my private network. It’s about seeing the invisible infrastructure before I tunnel through it.
🔍 Real talk: Am I the only one who does this the moment they get a DHCP lease, or are there other network geeks out there who can’t help but learn the “shape” of the internet in their corner of the world? Let me know your go-to “new network” ritual in the comments! 👇