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.
-
On Mac, I see this notice:
```➜ ~ sh -c 'sh -c "$(curl -s https://nextdns.io/diag)"'
zsh: no such file or directory: sh -c sh -c "$(curl -s https://nextdns.io/diag)
```
Is there something specific that I must do to run this snippet?
-
Hi
When running the command sh -c 'sh -c "$(curl -s https://nextdns.io/diag)"' on an Edgeouter I see this message " environment: line 85: detect_endiannes: command not found "
Looks like not complete...Fetching https://test.nextdns.io
status: unconfiguredSee attached file...
Steen
-
Hi Olivier Poitrey , this is an issue I have been facing for a long time now. I am connecting continuously to very far away servers thereby increasing ping by around 240 ms on average.
I have posted my diag results here: https://nextdns.io/diag/990f9f00-49b8-11eb-aaee-adbaa1733145
Request you to please look into the same.
-
Can you help me? I have been getting very high latency for a few days and therefore cannot access sites.
https://nextdns.io/diag/a4409560-491c-11eb-b38e-c1ae9e6f6c08
-
I am unable to post:
Do you want to send this report? [Y/n]: y
Optional email in case we need additional info: xxxxx
Post unsuccessful: status 400
{"error":"0: instance.Test requires property \"Client\"\n"}%
yeri-macbookpro1 ~ $ uname -a
Darwin yeri-macbookpro1.roam.corp.xxxx 20.2.0 Darwin Kernel Version 20.2.0: Wed Dec 2 20:39:59 PST 2020; root:xnu-7195.60.75~1/RELEASE_X86_64 x86_64 -
Experiencing high latency in India, seems to pick up far away servers due to bad routing? Logs of different ISPs are pasted below.
Airtel 4G:
https://nextdns.io/diag/9b05fb40-4cee-11eb-b1e7-537a0e39f0e9
BSNL 3G:
https://nextdns.io/diag/86309e40-4cef-11eb-b1e7-537a0e39f0e9
Jio 4G
https://nextdns.io/diag/679370b0-4cf0-11eb-b1e7-537a0e39f0e9
-
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.
-
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
-
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.
-
Usene tons on Android cell phone with Android private dns turned like dite tells how love nextdns but here my ping
heficed-chi (IPv6) 32 ms (ultralow1)
heficed-chi 33 ms (ultralow1)
vultr-chi 39 ms (anycast1, ultralow2)
vultr-chi (IPv6) 39 ms (anycast1, ultralow2)
teraswitch-pit 50 ms
zepto-iad 52 ms
zepto-mci (IPv6) 54 ms
teraswitch-pit (IPv6) 57 ms
zepto-iad (IPv6) 68 ms
zepto-xrs (IPv6) 73 ms
router-pit 74 ms
anexia-mnz 77 ms
zepto-xrs 78 ms
hydron-clt 78 ms
hydron-clt (IPv6) 79 ms
anexia-mnz (IPv6) 80 ms
smarthost-mci (IPv6) 81 ms
smarthost-mci 97 ms
zepto-mci 98 ms
anexia-ams (IPv6) 114 ms (anycast2)
anexia-ams 132 ms
I'm in desplaines il USA use on my home router also but ping on android cell phone for now showing here
-
figured I'd share my results too! I'm "guessing" it looks good? ;)
https://nextdns.io/diag/742bc560-82b1-11eb-abe8-11b40072f372
-
Ultra low for IPv6 is not working. And routing anycast 1 was too slow. Please check it! Thank you!
Anycast 1 connet to zepto-mad https://nextdns.io/diag/25f81500-8de3-11eb-8a6e-3fd26ddfe68f
Anycast 1 connect to zepto-hkg https://nextdns.io/diag/fde2bd80-8de3-11eb-8a6e-3fd26ddfe68f