Battle Can we get some pings and traceroutes for common DNS providers?

Compare list
1.1.1.1
dns.adguard-dns.com
dns.controld.com
dns.nextdns.io
dns.google
dns.quad9.net
Platform(s)
  1. Any platform

windscribe

From Windscribe
Thread author
Verified
Developer
Well-known
Dec 28, 2016
121
Hi folks,

This is not a traditional "battle" and I'm looking to get some anecdotal performance results from real people when it comes to latency to common DNS resolvers. Let's leave person feelings aside and concentrate on raw numbers.

Whoever is down to participate, please provide ping summary (at least 5 polls) and ideally a traceroute (feel free to redact first few hops) to the following endpoints:

  1. 1.1.1.1
  2. dns.adguard-dns.com
  3. dns.controld.com
  4. dns.nextdns.io
  5. dns.google
  6. dns.quad9.net


I'll start.

--- 1.1.1.1 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4005ms rtt min/avg/max/mdev = 0.978/1.078/1.193/0.070 ms HOST: Office-Box Loss% Snt Last Avg Best Wrst StDev 1. AS??? REDACTED 2. AS??? REDACTED 3. AS??? REDACTED 4. AS21949 be320.dr01.151FrontStW01.YYZ.beanfield.com 0.0% 5 1.0 1.3 1.0 1.5 0.2 5. AS??? ??? 100.0 5 0.0 0.0 0.0 0.0 0.0 6. AS??? beanfield.ip4.torontointernetxchange.net 0.0% 5 0.9 3.5 0.9 11.7 4.6 7. AS??? cloudflare.ip4.torontointernetxchange.net 0.0% 5 1.8 2.7 1.6 5.4 1.6 8. AS13335 108.162.239.2 0.0% 5 1.3 2.1 1.3 3.5 0.8 9. AS13335 one.one.one.one 0.0% 5 1.0 1.1 1.0 1.1 0.0

--- dns.adguard-dns.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4007ms rtt min/avg/max/mdev = 15.393/15.575/16.099/0.263 ms HOST: Office-Box Loss% Snt Last Avg Best Wrst StDev 1. AS??? REDACTED 2. AS??? REDACTED 3. AS??? REDACTED 4. AS21949 be320.dr01.151FrontStW01.YYZ.beanfield.com 0.0% 5 1.3 1.2 1.1 1.3 0.1 5. AS??? ??? 100.0 5 0.0 0.0 0.0 0.0 0.0 6. AS1299 beanfield-ic-357184.ip.twelve99-cust.net 0.0% 5 0.7 2.8 0.6 11.2 4.7 7. AS1299 toro-b5-link.ip.twelve99.net 0.0% 5 1.1 2.9 0.8 10.5 4.3 8. AS1299 chi-b23-link.ip.twelve99.net 0.0% 5 19.4 14.2 12.8 19.4 2.9 9. AS1299 chi-bb1-link.ip.twelve99.net 80.0% 5 10.8 10.8 10.8 10.8 0.0 10. AS1299 chi-b24-link.ip.twelve99.net 0.0% 5 11.0 11.2 10.9 12.1 0.5 11. AS1299 datacamp-ic-337371.ip.twelve99-cust.net 0.0% 5 11.1 11.4 11.1 12.3 0.5 12. AS60068 vl204.chi-cs1-dist-2.cdn77.com 0.0% 5 11.1 11.2 11.1 11.4 0.1 13. AS212772 dns.adguard.com 0.0% 5 13.2 14.3 13.2 18.7 2.4


--- dns.controld.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4006ms rtt min/avg/max/mdev = 1.133/1.330/1.555/0.166 ms HOST: Office-Box Loss% Snt Last Avg Best Wrst StDev 1. AS??? REDACTED 2. AS21949 REDACTED 3. AS??? REDACTED 4. AS21949 be320.dr01.151FrontStW01.YYZ.beanfield.com 0.0% 5 1.1 1.3 1.1 1.4 0.1 5. AS??? ??? 100.0 5 0.0 0.0 0.0 0.0 0.0 6. AS??? beanfield.ip4.torontointernetxchange.net 0.0% 5 0.9 0.9 0.6 1.0 0.1 7. AS??? ??? 100.0 5 0.0 0.0 0.0 0.0 0.0 8. AS??? ??? 100.0 5 0.0 0.0 0.0 0.0 0.0 9. AS36236 controld-edge1-tor.anycast.net 0.0% 5 1.2 1.0 0.9 1.2 0.1 10. AS398962 dns.controld.com 0.0% 5 1.2 1.2 1.1 1.3 0.0

--- steering.nextdns.io ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4005ms rtt min/avg/max/mdev = 0.541/0.634/0.683/0.049 ms HOST: Office-Box Loss% Snt Last Avg Best Wrst StDev 1. AS??? REDACTED 2. AS??? REDACTED 3. AS??? REDACTED 4. AS21949 be320.dr01.151FrontStW01.YYZ.beanfield.com 0.0% 5 1.3 1.2 1.1 1.4 0.1 5. AS??? ??? 100.0 5 0.0 0.0 0.0 0.0 0.0 6. AS??? beanfield.ip4.torontointernetxchange.net 0.0% 5 0.8 0.8 0.7 1.0 0.1 7. AS??? choopa.ip4.torontointernetxchange.net 0.0% 5 1.2 4.0 1.2 14.8 6.1 8. AS??? ??? 100.0 5 0.0 0.0 0.0 0.0 0.0 9. AS??? ??? 100.0 5 0.0 0.0 0.0 0.0 0.0 10. AS??? ??? 100.0 5 0.0 0.0 0.0 0.0 0.0 11. AS20473 dns.nextdns.io 0.0% 5 0.7 0.8 0.5 1.2 0.2

--- dns.google ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4006ms rtt min/avg/max/mdev = 0.978/1.041/1.077/0.037 ms HOST: Office-Box Loss% Snt Last Avg Best Wrst StDev 1. AS??? REDACTED 2. AS??? REDACTED 3. AS??? REDACTED 4. AS21949 be320.dr01.151FrontStW01.YYZ.beanfield.com 0.0% 5 1.2 1.2 1.0 1.5 0.2 5. AS??? ??? 100.0 5 0.0 0.0 0.0 0.0 0.0 6. AS15169 142.250.173.69 0.0% 5 0.6 3.5 0.6 14.3 6.1 7. AS15169 142.250.173.68 0.0% 5 4.6 3.1 0.7 8.8 3.6 8. AS15169 192.178.98.53 0.0% 5 2.5 2.6 2.5 2.9 0.1 9. AS15169 216.239.35.233 0.0% 5 1.2 1.5 1.2 1.7 0.2 10. AS15169 dns.google 0.0% 5 0.8 0.8 0.8 0.8 0.0

--- dns.quad9.net ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4006ms rtt min/avg/max/mdev = 0.581/0.984/2.109/0.578 ms HOST: Office-Box Loss% Snt Last Avg Best Wrst StDev 1. AS??? REDACTED 2. AS??? REDACTED 3. AS??? REDACTED 4. AS21949 be320.dr01.151FrontStW01.YYZ.beanfield.com 0.0% 5 1.2 1.3 1.0 2.2 0.5 5. AS??? ??? 100.0 5 0.0 0.0 0.0 0.0 0.0 6. AS??? beanfield.ip4.torontointernetxchange.net 0.0% 5 0.6 1.0 0.6 2.5 0.9 7. AS??? woodynet.torontointernetxchange.net 0.0% 5 1.2 2.9 1.1 7.0 2.6 8. AS19281 dns.quad9.net 0.0% 5 0.6 2.4 0.6 9.3 3.9
 

brambedkar59

Level 30
Verified
Top Poster
Well-known
Apr 16, 2017
1,966
Pinging 1.1.1.1 with 32 bytes of data:
Ping statistics for 1.1.1.1:
Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 3ms, Average = 2ms

Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms REDACTED
2 3 ms 3 ms 2 ms REDACTED
3 1 ms 1 ms 1 ms REDACTED
4 3 ms 3 ms 3 ms 172.68.39.2
5 5 ms 4 ms 4 ms 172.69.202.2
6 5 ms * 4 ms one.one.one.one [1.1.1.1]
Pinging dns.adguard-dns.com [94.140.14.14] with 32 bytes of data:
Ping statistics for 94.140.14.14:
Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 76ms, Maximum = 77ms, Average = 76ms

Tracing route to dns.adguard-dns.com [94.140.14.14]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms REDACTED
2 1 ms 1 ms 1 ms REDACTED
3 18 ms 11 ms 3 ms REDACTED
4 19 ms 18 ms 19 ms 14.141.116.229.static-Delhi.vsnl.net.in [14.141.116.229]
5 * 55 ms 53 ms 172.31.180.57
6 52 ms 51 ms 54 ms ix-ae-4-2.tcore1.cxr-chennai.as6453.net [180.87.36.9]
7 * 75 ms 75 ms if-be-34-2.ecore2.esin4-singapore.as6453.net [180.87.36.41]
8 74 ms 75 ms 74 ms 180.87.105.18
9 72 ms 73 ms 73 ms vl223.sgp-eq3-dist-2.cdn77.com [185.156.45.99]
10 76 ms 77 ms 76 ms dns.adguard.com [94.140.14.14]
Pinging dns.controld.com [76.76.2.22] with 32 bytes of data:
Ping statistics for 76.76.2.22:
Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 37ms, Maximum = 56ms, Average = 46ms

Tracing route to dns.controld.com [76.76.2.22]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms REDACTED
2 3 ms 2 ms 3 ms REDACTED
3 6 ms 5 ms 3 ms REDACTED
4 20 ms 20 ms 23 ms 14.141.116.229.static-Delhi.vsnl.net.in [14.141.116.229]
5 54 ms 58 ms 54 ms 172.28.176.206
6 33 ms 35 ms 35 ms 203.200.155.194
7 * * * Request timed out.
8 46 ms 44 ms 46 ms dns.controld.com [76.76.2.22]
Pinging steering.nextdns.io [139.84.167.156] with 32 bytes of data:
Ping statistics for 139.84.167.156:
Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 5ms, Average = 4ms

Tracing route to steering.nextdns.io [139.84.167.156]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms REDACTED
2 3 ms 3 ms 3 ms REDACTED
3 12 ms 6 ms 11 ms REDACTED
4 12 ms 13 ms 13 ms 14.141.116.229.static-Delhi.vsnl.net.in [14.141.116.229]
5 4 ms 4 ms 4 ms 115.117.120.186
6 6 ms 6 ms 8 ms 10.102.0.10
7 5 ms 4 ms 4 ms 10.102.0.114
8 * * * Request timed out.
9 6 ms 6 ms 5 ms dns.nextdns.io [139.84.167.156]
Pinging dns.google [8.8.4.4] with 32 bytes of data:
Ping statistics for 8.8.4.4:
Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 4ms, Average = 3ms

Tracing route to dns.google [8.8.4.4]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms REDACTED
2 3 ms 2 ms 2 ms REDACTED
3 2 ms 1 ms 1 ms REDACTED
4 7 ms 3 ms 2 ms 142.250.160.212
5 2 ms 2 ms 2 ms 142.251.77.185
6 4 ms 3 ms 3 ms 142.251.52.207
7 2 ms 2 ms 2 ms dns.google [8.8.4.4]
Pinging dns.quad9.net [9.9.9.9] with 32 bytes of data:
Ping statistics for 9.9.9.9:
Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 6ms, Average = 5ms

Tracing route to dns.quad9.net [9.9.9.9]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms REDACTED
2 4 ms 2 ms 3 ms REDACTED
3 3 ms 3 ms 3 ms 205.254.170.49
4 5 ms 5 ms 5 ms 45.120.248.248
5 5 ms 5 ms 5 ms dns9.quad9.net [9.9.9.9]
Edit: removed spacing
 
Last edited:

SeriousHoax

Level 48
Verified
Top Poster
Well-known
Mar 16, 2019
3,715
cld-p.jpg
cld-t.jpg
adg-p.jpg
adg-t.jpg
ctd-p.jpg
ctd-t.jpg
nxt-p.jpg
nxt-t.jpg
google-p.jpg
google-t.jpg
quad-p.jpg
quad-t.jpg
 

SeriousHoax

Level 48
Verified
Top Poster
Well-known
Mar 16, 2019
3,715
Wow, those pings for Google and NextDNS. Absurd routing FTW
Yeah, the NextDNS one especially is very odd. If I simply ping 45.90.28.0 then I get similar to ControlD but using dns.nextdns.io made it use 45.90.30.0 which has always been ridiculous like this on my location.
Ping 41-67ms for other providers has been the average always. But since last year Quad9 and Cloudflare have been using servers located in my country which has improved their performance. Others usually route to Singapore/India. I'm not very knowledgeable regarding DNS routing, so I'm not sure if my understanding is correct.
 

toto_10

Level 5
Verified
Well-known
Feb 12, 2017
245
Pinging 1.1.1.1 with 32 bytes of data:
Reply from 1.1.1.1: bytes=32 time=24ms TTL=55
Reply from 1.1.1.1: bytes=32 time=39ms TTL=55
Reply from 1.1.1.1: bytes=32 time=56ms TTL=55
Reply from 1.1.1.1: bytes=32 time=25ms TTL=55

Ping statistics for 1.1.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 56ms, Average = 36ms
Pinging dns.adguard-dns.com [94.140.15.15] with 32 bytes of data:
Reply from 94.140.15.15: bytes=32 time=33ms TTL=53
Reply from 94.140.15.15: bytes=32 time=43ms TTL=53
Reply from 94.140.15.15: bytes=32 time=33ms TTL=53
Reply from 94.140.15.15: bytes=32 time=66ms TTL=53

Ping statistics for 94.140.15.15:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 66ms, Average = 43ms
Pinging dns.controld.com [76.76.2.22] with 32 bytes of data:
Reply from 76.76.2.22: bytes=32 time=49ms TTL=56
Reply from 76.76.2.22: bytes=32 time=35ms TTL=56
Reply from 76.76.2.22: bytes=32 time=61ms TTL=56
Reply from 76.76.2.22: bytes=32 time=29ms TTL=56

Ping statistics for 76.76.2.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 61ms, Average = 43ms
Pinging steering.nextdns.io [188.172.192.71] with 32 bytes of data:
Reply from 188.172.192.71: bytes=32 time=28ms TTL=56
Reply from 188.172.192.71: bytes=32 time=28ms TTL=56
Reply from 188.172.192.71: bytes=32 time=31ms TTL=56
Reply from 188.172.192.71: bytes=32 time=24ms TTL=56

Ping statistics for 188.172.192.71:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 31ms, Average = 27ms
Pinging dns.google [8.8.8.8] with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=34ms TTL=57
Reply from 8.8.8.8: bytes=32 time=26ms TTL=57
Reply from 8.8.8.8: bytes=32 time=34ms TTL=57
Reply from 8.8.8.8: bytes=32 time=36ms TTL=57

Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 36ms, Average = 32ms
Pinging dns.quad9.net [9.9.9.9] with 32 bytes of data:
Reply from 9.9.9.9: bytes=32 time=38ms TTL=56
Reply from 9.9.9.9: bytes=32 time=34ms TTL=56
Reply from 9.9.9.9: bytes=32 time=33ms TTL=56
Reply from 9.9.9.9: bytes=32 time=31ms TTL=56

Ping statistics for 9.9.9.9:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 38ms, Average = 34ms
 

brambedkar59

Level 30
Verified
Top Poster
Well-known
Apr 16, 2017
1,966
Yeah, the NextDNS one especially is very odd. If I simply ping 45.90.28.0 then I get similar to ControlD but using dns.nextdns.io made it use 45.90.30.0 which has always been ridiculous like this on my location.
Ping 41-67ms for other providers has been the average always. But since last year Quad9 and Cloudflare have been using servers located in my country which has improved their performance. Others usually route to Singapore/India. I'm not very knowledgeable regarding DNS routing, so I'm not sure if my understanding is correct.
In the past I had some issues with routing, which were eventually fixed by my ISP. Took some patience to talk to their CC and in few weeks, they fixed it. Worth talking to ur ISP I would say.
 

monkeylove

Level 12
Verified
Top Poster
Well-known
Mar 9, 2014
564
Also, check out this one, but not all providers are featured.

 

About us

  • MalwareTips is a community-driven platform providing the latest information and resources on malware and cyber threats. Our team of experienced professionals and passionate volunteers work to keep the internet safe and secure. We provide accurate, up-to-date information and strive to build a strong and supportive community dedicated to cybersecurity.

User Menu

Follow us

Follow us on Facebook or Twitter to know first about the latest cybersecurity incidents and malware threats.

Top