Report network latency issue
If you are experiencing some latency issue or non-ideal routing, please use our diagnostic tool to report it. The tool can run on your computer or router. It gathers and submit network measurements that will help us improve our network. You can then use the generated diagnostic link to report your issue on the Help Forum.
Please follow the instruction for your platform below:
MacOS, Linux, *BSD, Linux based routers
Open a terminal, run the following command and follow the instructions:
sh -c 'sh -c "$(curl -s https://nextdns.io/diag)"'Windows
- Download and run this program.
- If you get a virus alert, you can disregard it, see note below.
- Follow the instructions
If you find bugs in the tool itself, please log an issues on the Github repository.
124 replies
-
Yesterday, 2021/1/1 some of my amazon echoes (2/5) didn't connect due to excessive latency nextdns reply...spent many time to factory reset the echos before I figuring out the problem was your dns :(
today, some hops are missing
https://nextdns.io/diag/4fec72f0-4d3a-11eb-b1e7-537a0e39f0e9
-
on 1/26/2021 THE NEXT DFNS IS SLOW HERE WHAT GETTING
Tracing route to dns1.nextdns.io [45.90.28.27]
over a maximum of 30 hops:1
2 21 ms 7 ms 9 ms d47-69-1-72.try.wideopenwest.com [69.47.72.1]
3 17 ms 9 ms 10 ms dynamic-76-73-171-37.knology.net [76.73.171.37]
4 11 ms 10 ms 10 ms 76-73-170-110.knology.net [76.73.170.110]
5 10 ms 10 ms 19 ms 76-73-164-154.knology.net [76.73.164.154]
6 10 ms 11 ms 12 ms static-75-76-101-196.knology.net [75.76.101.196]
7 11 ms 11 ms 13 ms static-76-73-191-232.knology.net [76.73.191.232]
8 11 ms 11 ms 11 ms chi-b2-link.telia.net [62.115.63.86]
9 13 ms 11 ms 13 ms chi-b2-link.telia.net [62.115.122.195]
10 13 ms 11 ms 13 ms vultr-ic-318445-chi-b2.c.telia.net [62.115.148.197]
11 * * * Request timed out.
12
PS C:\Users\ray> tracert 45.90.30.27Tracing route to dns2.nextdns.io [45.90.30.27]
over a maximum of 30 hops:1
2 11 ms 8 ms 10 ms d47-69-1-72.try.wideopenwest.com [69.47.72.1]
3 10 ms 8 ms 9 ms dynamic-76-73-171-37.knology.net [76.73.171.37]
4 11 ms 8 ms 9 ms 76-73-170-110.knology.net [76.73.170.110]
5 10 ms 11 ms 30 ms 76-73-164-154.knology.net [76.73.164.154]
6 12 ms 11 ms 10 ms static-75-76-101-196.knology.net [75.76.101.196]
7 18 ms 12 ms 10 ms static-76-73-191-232.knology.net [76.73.191.232]
8 12 ms 12 ms 13 ms chi-b2-link.telia.net [62.115.63.86]
9 25 ms 24 ms 24 ms atl-b24-link.ip.twelve99.net [62.115.113.18]
10 26 ms 24 ms 24 ms dcr02.anx57.atl.us.anexia-it.net [62.115.165.226]
11 36 ms 33 ms 35 ms ae0.dcr01.anx57.atl.us.anexia-it.net [188.172.247.32]
12 33 ms 33 ms 32 ms dns2.nextdns.io [45.90.30.27] FIRST ONE END WITH ALL START ONLY SHOWING SOME AND TOOK OUT FIRST HOP DEW TO MY DEVICE AND DONT WANT IT PINGED -
Script worked fine on my MacBook Air running macOS Big Sur (not M1). Ran the script on 30/01/2021.
It reported a higher latency of 99ms on the IPv6 link to gsl-per (Perth, Australia) which I think is normal from Sydney, Australia. Latency to local gsl-syd and vltr-syd was 6-7 ms on both IPv4 and IPv6 which is very good.
I have uploaded the test results via the script.
-
serverwala-buh 8 ms (ultralow2)
zepto-sof 16 ms
estnoc-buh 19 ms (ultralow1)
■ zepto-fra 33 ms (anycast1)
anexia-fra 36 ms (anycast2)
anexia-vie 48 ms
exoscale-vie 48 ms
anexia-waw 51 ms
zepto-waw 66 ms
anexia-sof 66 ms
edgeuno-ist 75 ms
premiumrdp-ist 76 ms
FRUSTRATING !!!
-
Am in Australia... getting 5-10s page load times. DNS is sooooo slow with NextDNS enabled it's like being on dialup. Tool run and diag sent.
-
Test result today: https://nextdns.io/diag/702a41e0-71bc-11eb-9a9a-a3e20303d7a2
-
https://nextdns.io/diag/08cc6110-7372-11eb-a511-27729ee6adcd
I'm using DoH on my phone which is routed to router-pit (220 ms) and teraswitch-pit (226 ms). Please fix this. Thanks
-
Khairul Are you using a DNS server (either on your phone or at the router level) that's in the US?
-
Romain Cointepas I'm using both DoT (Private DNS for Android 9+) and Android below than Android 9, I'm using DoH in Chrome. Ya that's from US server. My ISP is AS4788 (Malaysia). I'll put result from test.nextdns.io for your reference.
-
Romain Cointepas and this result from ping.nextdns.io
-
Khairul The reason you're being sent to US servers with NextDNS is that the DNS server in your network (what's used to first resolve dns.nextdns.io) is something hosted on Amazon AWS in the US (3.18.127.41). My guess is down the line on your network, a custom US DNS server is set?
-
Romain Cointepas oh i see, you right!.. I don't know thats my dns on my router affect nextdns ultralow route, because I just want to use nextdns on my portable devices but not on my home router. Thank for your support
-
Romain Cointepas for your information when I change back to cloudflare dns and enable IPv6, ultralow changed.. not US anymore...
-
Khairul Can I ask what DNS server you use on your router, and why is it in the US when you are in Malaysia?
-
Romain Cointepas https://alternate-dns.com/ they just upgraded their infrastructure, hosted by Amazon AWS (I guess) which is fast in my country (routed to Amazon Singapore). Idk thats affect my NextDNS DoT and DoH on my phone. So I changed back to Cloudflare.
-
Khairul is NextDNS routing better when using Cloudflare on the router?
-
Romain Cointepas https://nextdns.io/diag/ab23db60-7394-11eb-8d0e-4bbc5409628a
Yeah all route to Singapore (IPv4 & IPv6), except anycast2 route to London (IPv4 & IPv6). I think it would be nice if you can fix anycast2 route maybe? But I don't think it will be used in my case because I'm using DoT and DoH which is NextDNS using ultralow I guess. Maybe some other user from my ISP use unencrypted DNS from NextDNS. It would be good if anycast2 (both IPv4 & IPv6) are faster too.
-
-
https://nextdns.io/diag/c605daf0-752e-11eb-a7ae-9f6e888a83a3
dns2.nextdns.io routes to
Johannesburg ZA
AS 37179
Africa Independent Network Exchange (Pty) LTD (AfricaINX)Tracing route to ipv4-anycast.dns2.nextdns.io [45.90.30.0] with TTL of 32:
1 2ms 2ms 5ms SynologyRouter.local [192.168.1.1]
2 23ms 20ms 10ms 142.254.213.149
3 27ms 36ms 39ms agg63.drfdnyad02h.northeast.rr.com [24.58.240.165]
4 22ms 16ms 14ms agg93.esyrnyaw02r.northeast.rr.com [24.58.52.116]
5 16ms 15ms 16ms agg27.rcr01rochnyei.netops.charter.com [24.58.32.76]
6 31ms 31ms 30ms bu-ether13.tustca4200w-bcr00.tbone.rr.com [66.109.6.2]
7 33ms 31ms 31ms 66.109.5.137
8 37ms 29ms 34ms ae-13.edge2.Chicago10.Level3.net [4.68.37.137]
9 * * * Request timed out.
10 118ms 127ms 121ms EOH-MTHOMBO.ear2.Amsterdam1.Level3.net [213.19.192.134]
11 * * * Request timed out.
12 301ms 304ms 298ms xe-0-1-6-0.dcr01.anx67.jnb.za.anexia-it.net [41.66.181.79]
13 301ms 297ms 299ms ipv4-anycast.dns2.nextdns.io [45.90.30.0]Traceroute complete.
-
-
John DeCarlo
Consistent with mine:
i am also on TWC-11351-NORTHEAST
Secondary: anexia-jnb (297 ms)
Secondary IPv6: anexia-jnb (270 ms)
-
TheGreat1G it’s fixed now, thank you! No more pings to Africa Johannesburg
-
