very Slow dns with 280+ ping and latency (image included)
I am getting 280+ ping although there are other server with lower ping. Can i manually use other servers?
8 replies
-
Welcome to NextDNS network diagnostic tool.This tool will capture latency and routing information regarding
the connectivity of your network with NextDNS.The source code of this tool is available at https://github.com/nextdns/diag
Do you want to continue? (press enter to accept)
Testing IPv6 connectivity
available: true
Fetching https://test.nextdns.io
status: ok
client: 2404:7c00:42:e9ba:1535:2972:21f8:255e
protocol: UDP
dest IP:
server: anexia-dxb-1
Fetching PoP name for ultra low latency primary IPv4 (ipv4.dns1.nextdns.io)
anexia-del: 111.77ms
Fetching PoP name for ultra low latency secondary IPv4 (ipv4.dns2.nextdns.io)
microhost-del: 66.965ms
Fetching PoP name for anycast primary IPv4 (45.90.28.0)
anexia-dxb: 317.406ms
Fetching PoP name for anycast secondary IPv4 (45.90.30.0)
anexia-dxb: 287.735ms
Fetching PoP name for ultra low latency primary IPv6 (ipv6.dns1.nextdns.io)
Fetch error: Get "https://dns.nextdns.io/info": dial tcp: lookup ipv6.dns1.nextdns.io: no such host
Fetching PoP name for ultra low latency secondary IPv6 (ipv6.dns2.nextdns.io)
Fetch error: Get "https://dns.nextdns.io/info": dial tcp: lookup ipv6.dns2.nextdns.io: no such host
Fetching PoP name for anycast primary IPv6 (2a07:a8c0::)
anexia-dxb: 278.768ms
Fetching PoP name for anycast secondary IPv6 (2a07:a8c1::)
anexia-dxb: 293.857ms
Pinging PoPs
vultr-bom (IPv6): 38.235ms
ls-bom: 45ms
vultr-bom: 44.159ms
ls-bom: 47.32ms
anexia-maa (IPv6): 48.024ms
do-blr (IPv6): 57.763ms
anexia-maa: 60.758ms
ls-bom (IPv6): 64ms
anexia-del: 64.043ms
do-blr: 73.635ms
ls-bom (IPv6): 79.967ms
microhost-del: 93ms
anexia-del (IPv6): 92.879ms
greencloud-han: 150.415ms
premiumrdp-bkk: 223ms
anexia-han: 249.325ms
greencloud-han (IPv6): 252.981ms
Traceroute for ultra low latency primary IPv4 (217.146.10.59)
1 192.168.1.254 1ms 1ms 1ms
2 110.44.112.227 7ms 8ms 6ms
3 103.41.174.142 6ms 6ms 5ms
4 103.10.28.67 8ms 5ms 6ms
5 110.44.112.66 6ms 5ms 6ms
6 125.19.67.33 11ms 11ms 18ms
7 116.119.50.142 73ms 74ms 73ms
8 125.19.53.94 92ms 76ms 76ms
9 180.179.197.10 69ms 69ms 69ms
10 180.179.193.182 91ms 76ms 76ms
11 217.146.10.59 89ms 89ms 89ms
Traceroute for ultra low latency secondary IPv4 (103.127.29.198)
1 192.168.1.254 2ms 1ms 1ms
2 110.44.112.227 8ms 7ms 5ms
3 103.41.174.142 26ms 5ms 5ms
4 103.10.28.67 8ms 8ms 9ms
5 110.44.112.66 8ms 9ms 8ms
6 125.19.67.33 28ms 9ms 12ms
7 116.119.44.160 92ms 76ms 76ms
8 182.71.117.74 103ms 72ms 73ms
9 103.127.29.198 87ms 69ms 73ms
Traceroute for anycast primary IPv4 (45.90.28.0)
1 192.168.1.254 2ms 2ms 1ms
2 110.44.112.227 64ms 7ms 9ms
3 103.41.174.142 27ms 8ms 9ms
4 103.10.28.67 7ms 9ms 8ms
5 110.44.112.66 7ms 6ms 8ms
6 125.19.67.33 13ms 10ms 9ms
7 182.79.222.213 97ms 78ms 76ms
8 185.1.8.11 329ms 325ms 391ms
9 45.90.28.0 329ms 327ms 408ms
Traceroute for anycast secondary IPv4 (45.90.30.0)
1 192.168.1.254 2ms 1ms 1ms
2 110.44.112.227 9ms 13ms 7ms
3 103.41.174.142 25ms 5ms 13ms
4 103.10.28.67 8ms 9ms 8ms
5 110.44.112.66 6ms 9ms 8ms
6 125.19.67.33 11ms 12ms 11ms
7 182.79.222.213 73ms 72ms 73ms
8 185.1.8.11 407ms 404ms 406ms
9 45.90.30.0 438ms 413ms 307ms
Traceroute error: lookup ipv6.dns1.nextdns.io: no such host
Traceroute error: lookup ipv6.dns2.nextdns.io: no such host
Traceroute for anycast primary IPv6 (2a07:a8c0::)
1 2404:7c00:42:e9ba::1 1ms 1ms 1ms
2 2404:7c00::f 28ms 8ms 6ms
3 2404:7c00:0:7::2 27ms 9ms 8ms
4 2404:7c00:0:6::2 27ms 8ms 5ms
5 2404:a800:1a00:807::89 58ms 57ms 57ms
6 2404:a800::30 72ms 72ms 73ms
7 2001:7f8:73::a5e9:0:1 308ms 290ms 290ms
8 2a07:a8c0:: 399ms 299ms 300ms
Traceroute for anycast secondary IPv6 (2a07:a8c1::)
1 2404:7c00:42:e9ba::1 21ms 3ms 2ms
2 2404:7c00::f 10ms 36ms 43ms
3 2404:7c00:0:7::2 65ms 64ms 9ms
4 2404:7c00:0:6::2 28ms 8ms 6ms
5 2404:a800:1a00:807::89 76ms 250ms 57ms
6 2404:a800::30 85ms 66ms 66ms
7 2001:7f8:73::a5e9:0:1 284ms 300ms 287ms
8 2a07:a8c1:: 425ms 309ms 285ms
Do you want to send this report? [Y/n]:
-
while using nextdns own client for window and tls or doh for mobile devices and browser it is having high ping
-
this is the ping in mobile device
Content aside
- 2 yrs agoLast active
- 8Replies
- 529Views
-
4
Following