Not using the closest server
I've run already the diag quite a few times from my router but it is no resolved
is used which is quite slow from a network distance perspective regardless if it is close from a geographical perspective
results from ping
serverwala-buh (IPv4) 32 ms
■ anexia-ams (IPv6) 47 ms (secondary)
exoscale-vie (IPv6) 48 ms
■ anexia-lon (IPv4) 53 ms (secondary)
■ zepto-lon (IPv4) 54 ms (primary)
■ zepto-fra (IPv6) 55 ms (primary)
anexia-vie (IPv4) 62 ms
estnoc-buh (IPv4) 62 ms
exoscale-vie (IPv4) 64 ms
serverwala-buh (IPv6) 67 ms
serverwala-mil (IPv4) 68 ms
anexia-vie (IPv6) 70 ms
edgeuno-ist (IPv6) 83 ms
edgeuno-ist (IPv4) 85 ms
zepto-sof (IPv4) 89 ms
premiumrdp-ist (IPv4) 95 ms
anexia-sof (IPv6) 98 ms
anexia-sof (IPv4) 98 ms
citynet-cai (IPv4) 102 ms
diag report here: https://nextdns.io/diag/3dfa7a90-50cf-11eb-9bcc-51da18bb30ac
27 replies
-
Any updates ?
-
ultralow definition is really funny here
serverwala-buh 42 ms
exoscale-vie (IPv6) 57 ms
zepto-fra (IPv6) 58 ms (anycast1)
anexia-lon 62 ms (anycast2)
serverwala-buh (IPv6) 65 ms
anexia-ams (IPv6) 68 ms (anycast2)
zepto-lon 71 ms (anycast1)
estnoc-buh 71 ms
edgeuno-ist (IPv6) 82 ms
zepto-mil (IPv6) 84 ms
anexia-vie (IPv6) 98 ms
zepto-mil 104 ms
anexia-vie 107 ms
edgeuno-ist 110 ms
anexia-sof (IPv6) 122 ms (ultralow1)
■ anexia-sof 125 ms (ultralow1)
citynet-cai 128 ms
zepto-sof 142 ms (ultralow2)
premiumrdp-ist 246 ms
exoscale-vie 255 ms
dns2.nextdns.io (IPv6) error (ultralow2)
Olivier Poitrey any actions coming?
Content aside
-
1
Likes
- 3 yrs agoLast active
- 27Replies
- 719Views
-
5
Following