I operate several machines at a facility approximately 80 kilometers from my residence. A traceroute to my own colocated machine traverses thirty hops. The physical distance is irrelevant; the path originates at my rural ISP, backhauls to a major exchange city, transits three separate networks, and finally returns. The latency is 34 milliseconds. I am paying for this inefficiency. I understand the economic logic of rural aggregation but the topological absurdity still offends me. -- Marcus
My traceroute has 30 hops to a destination 50 miles away
My rack at same facility, 42U, 15A circuit
The wife says I care more about hop count than her
Measured power: 2.3 kW steady, 2.8 kW peak when those cheap Leaseweb switches warm up
Your 34 ms is not bad, I get 28 ms to same city and I am closer, figure that one out
Works on my end
Your traceroute is wrong, you have misconfiguration, check your local routing table
RTFM
I have make traceroute since 2 days also, from my village to Lyon, 45 hops lol
It is possible to do that? Yes because my ISP send everything to Paris first, then peer in Paris, then back to Lyon
The geography is not the network, I learn this since long time
Mdr
Wat man 30 hops for 50 miles is normal
My traceroute to Hostinger in sao paulo is 15 hops and I am in sao paulo more fast wen you live in rio because the backhaul go direct not like this kkkkkk
Double negative: I dont got no problem with 30 hops
¿why not¿ 30 hops is very normal brother.
My ISP in madrid send traffic to london then Frankfurt then back to barcelona jaja
Is very the infrastructure economics brother. They dont build fiber for every pueblo.
The latency is what matter not the hops!
What rural ISP and what backhaul city