Getting 5 hops tracerouting 1.1.1.1


#1

Hello,

I saw on https://blog.cloudflare.com/fixing-reachability-to-1-1-1-1-globally/ that the ideal low latency setup is one hop, when i do a traceroute i get 5 hops, first is the local router, then 2 adresses that belong to my isp, and then cloudflare.telecity2.nl-ix (dot) net [193.239.117.114] before it goes to 1dot1dot1dot1.cloudflare-dns.com [1.1.1.1] is there a way to reduce the number of hops?

My isp is KPN, i am using Pi-hole if that matters

Thanks in advance,

Nick


#2

One hop in that scenario is actually a bad thing. It means that the connection is being intercepted by the router and isn’t making it to Cloudflare. 4 hops doesn’t sound too bad actually…

Here are my traceroutes to 1.0.0.1 (Cloudflare) at 9 hops and 8.8.8.8 (Google) 10 hops for comparison:

traceroute to 1.0.0.1 (1.0.0.1), 64 hops max, 52 byte packets
1 192.168.1.254 (192.168.1.254) 1.644 ms 0.805 ms 0.615 ms
2 45-18-124-1.lightspeed.austtx.sbcglobal.net (45.18.124.1) 3.464 ms 16.442 ms 10.533 ms
3 71.149.77.208 (71.149.77.208) 4.139 ms 3.310 ms 2.438 ms
4 75.8.128.136 (75.8.128.136) 4.395 ms 2.795 ms 2.170 ms
5 12.83.68.145 (12.83.68.145) 2.339 ms
12.83.68.137 (12.83.68.137) 5.455 ms
12.83.68.145 (12.83.68.145) 3.775 ms
6 12.123.18.233 (12.123.18.233) 12.312 ms 13.846 ms 7.920 ms
7 192.205.36.206 (192.205.36.206) 8.228 ms 8.155 ms 7.733 ms
8 66.110.56.158 (66.110.56.158) 8.538 ms 9.875 ms 7.829 ms
9 1dot1dot1dot1.cloudflare-dns.com (1.0.0.1) 7.213 ms 7.378 ms 9.707 ms

traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 52 byte packets
1 192.168.1.254 (192.168.1.254) 1.270 ms 0.655 ms 0.821 ms
2 45-18-124-1.lightspeed.austtx.sbcglobal.net (45.18.124.1) 146.576 ms 5.585 ms 4.316 ms
3 71.149.77.208 (71.149.77.208) 2.584 ms 2.644 ms 3.161 ms
4 75.8.128.136 (75.8.128.136) 2.783 ms 5.544 ms 2.154 ms
5 12.83.68.137 (12.83.68.137) 2.604 ms
12.83.68.145 (12.83.68.145) 2.440 ms
12.83.68.137 (12.83.68.137) 5.468 ms
6 12.122.85.197 (12.122.85.197) 7.577 ms 7.900 ms 7.750 ms
7 * * *
8 * * *
9 108.170.238.220 (108.170.238.220) 14.570 ms
72.14.234.103 (72.14.234.103) 8.032 ms
72.14.235.111 (72.14.235.111) 7.786 ms
10 google-public-dns-a.google.com (8.8.8.8) 8.275 ms 7.620 ms 7.809 ms


#3

The real test is speed of lookup, which you can test like this on your Pi:

dig cnn.com @1.1.1.1
dig cnn.com @8.8.8.8

For me both answer in 8ms which is pretty fast…

;;Query time: 8 msec


#4

ok, i misunderstood the blogpost then,

Thanks for the explanation!


#5

This topic was automatically closed after 14 days. New replies are no longer allowed.