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)"'
- 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.
Hello support team,
I am facing network performance issues (especially in Multiplayer Online Games and with Audio / Video Streaming (e.g. Amazon Prime / Apple Music or Video). I am using a Peplink Balance Router with 2 WAN internet providers (Telekom DSL and Vodafone LTE) to gain enough speed at our countryside region in south-west of Germany close to the French border (slow bandwith region far away from bigger cities). I am unsing 2 different nextdns-Profiles for every of the lines (having a separate dyndns address each).
Can the problem maybe have todo with my location, as Nextdns seems to connect to DNS Servers at France insteand of German servers?
I would appreciate, if you could please review the following logs.
Diagnose results using Telekom: https://nextdns.io/diag/ba295220-93a1-11eb-ac31-f10bbd007106
Diagnose results using Vodafone: https://nextdns.io/diag/ea674920-93a0-11eb-ac31-f10bbd007106
Something I can do?
I’m having issues getting the closest server. Keeps on going to zepto-sin and is fixed if I restart the service or router (CLI on ASUS router).
connecting far away servers high ping by around 50 to 60 ms on average. My nearest one serverwala-del 4ms and microhost-del 4 ms connecting to ■ do-blr 52 ms (ultralow1) any good reason.
Diagnostic Tool Report 21- April-2021 https://nextdns.io/diag/75355ba0-a2ba-11eb-ba97-31f721ac5087
CLI client keeps being routed to `anexia-lis` POP despite being US based. I am on a UDM Pro. The diag script on the router itself is stalling because one of the traceroutes does not complete. The linked output here is from my laptop and I've pasted some of the output from diag on the UDMP below as well.
Laptop output: https://nextdns.io/diag/f580fc00-a9c3-11eb-85e8-a1be87597512
Router partial output:
Testing IPv6 connectivity available: false Fetching https://test.nextdns.io status: unconfigured client: redacted (same as linked output above) resolver: 188.8.131.52 Fetching PoP name for ultra low latency primary IPv4 (ipv4.dns1.nextdns.io) anexia-lis: 110.803ms Fetching PoP name for ultra low latency secondary IPv4 (ipv4.dns2.nextdns.io) vultr-chi: 2.386ms Fetching PoP name for anycast primary IPv4 (184.108.40.206) anexia-lis: 111.535ms Fetching PoP name for anycast secondary IPv4 (220.127.116.11) virtua-par: 93.43ms Pinging PoPs vultr-chi: 2.4ms heficed-chi: 3ms teraswitch-pit: 13.059ms zepto-mci: 13.366ms router-pit: 13.333ms smarthost-mci: 18.493ms zepto-iad: 18.838ms zepto-xrs: 19.316ms anexia-mnz: 22.031ms hydron-clt: 23.359ms Traceroute for ultra low latency primary IPv4 (18.104.22.168) 1 10.16.160.1 0ms 0ms 0ms 2 22.214.171.124 0ms 0ms 0ms 3 126.96.36.199 0ms 0ms 0ms 4 188.8.131.52 0ms 0ms 0ms 5 184.108.40.206 0ms 0ms 0ms 6 220.127.116.11 2ms 1ms 1ms 7 18.104.22.168 1ms 1ms 1ms 8 22.214.171.124 1ms 1ms 1ms 9 126.96.36.199 8ms 8ms 9ms 10 188.8.131.52 20ms 20ms 20ms 11 184.108.40.206 92ms 92ms 93ms 12 220.127.116.11 105ms 105ms 105ms 13 18.104.22.168 111ms 112ms 113ms 14 22.214.171.124 109ms 109ms 109ms 15 126.96.36.199 110ms 110ms 110ms 16 188.8.131.52 110ms 109ms 110ms Traceroute for ultra low latency secondary IPv4 (184.108.40.206) 1 10.16.160.1 0ms 0ms 0ms 2 220.127.116.11 0ms 0ms 0ms 3 18.104.22.168 0ms 0ms 0ms 4 22.214.171.124 0ms 0ms 0ms 5 126.96.36.199 0ms 0ms 0ms 6 188.8.131.52 5ms 1ms 1ms 7 184.108.40.206 1ms 1ms 1ms 8 220.127.116.11 1ms 1ms 1ms 9 18.104.22.168 1ms 5ms 1ms 10 22.214.171.124 1ms 1ms 1ms 11 126.96.36.199 1ms 6ms 1ms 12 188.8.131.52 2ms 4ms 3ms
I think my network can be saved, please help adjust the network to China. The link seems to be reset.发
Some people tell me my iPhone look like I'm in USA needs fixing
Hey guys, would appreciate it if you could give me some feedback on this.
I don't think I am connecting to the ultra low latency servers at all, my average response time is in the region of 200-300ms. So I suspect that I am connecting to edgeuno-sao or anexia-lon
Please advise on how I can optimally connect to the closest server.
I'm being routed to the wrong server, I'm in Sydney but instead all my traffic is being sent via Melbourne. Can this be fixed so that it goes via Sydney instead?
My connection is since yesterday and today very slow.
there is generally best one premiumrdp-ist but when checing ping its going to server edgeuno-ist
here is the diag : https://nextdns.io/diag/a311a6e0-b30a-11eb-b651-bd1b4832df5d
pls can you fix it to premiumrdp-ist
Since as a private user I do not have the possibility to send an email, I leave my good-bye comment here: I tried the service and even signed up for a paid yearly plan but after some weeks of usage I repeatedly got outages where I could not open a legit website. Happened both on mobile and desktop devices across the family. It seems the DNS server was down. After a couple of minutes it worked again but this was not acceptable. Switched back to Cloudflare for families again. Would have loved to use the service because I think the idea is great.
https://nextdns.io/diag/26e54060-b3d0-11eb-b104-fb4765e971c6 in case anyone wants to investigate further. Diagnostics was created after I switched back to Cloudflare.
Here's mine. Can anything be improved? I'm using it in YogaDNS. Set it to 45.90.30.*** because this one seems to have lower a ping than 45.90.28.*** and ultra latency option in YogaDNS.
I am using NextDNS CLI on a UDM Pro. Everything on my LAN is using the UDM Pro for DNS and works great except for POP selection.
I ran the diag, which shows the usual experience - there are IPv6 POPs with much lower latency not being used via my network:
Geographically speaking certainly not far off - I don't know if my ISP has their subnet spanning multiple sites. Any tweaking NextDNS could do would be great!