Member OP
Hi everyone! Sorry, total noob here I found this old guide about reading traceroutes and trying to learn. Could someone explain how you tell which carrier owns which hop from just the hostname? Like when it says something like "core-router.city.carrier.net" — how do you know who's peered with who? Sorry if this is dumb!!
I stare at traceroutes more than I'd like 😂 few tricks: look at domain in hostname, check reverse DNS consistency, compare latency jumps. €0.02: contabo.com to ovhcloud.com usually hits Vultr backbone in between. Timing spikes = likely handoff. List I use:
Member
This is insane value knowledge! Back in the day you could map the whole internet from traceroutes! Ampere boxes at my edge run circles around old x86 for this kind of lookup workload — 128 cores, parallel whois, whole table in seconds! Modern cloud obfuscation kills the art though. AWS Global Accelerator? Invisible. Azure Front Door? Ghost hops. You see 3ms then 45ms with nothing between. Where's the carrier? Gone! The hostname game is dying and it makes me sad!
Grabs popcorn 🍿
ASN path is the only way I trust anymore. Names lie.
