0
Connected to a much higher latent server instead of lowest ones
What is wrong with NextDNS? It's connected to the farthest server instead of the nearest one. 32 ms vs 236 ms and chose to connect to 236 ms.
Also, update nextdns app in Android for God's sake.
Client
ASN: AS4775 Globe Telecoms
Country: PH
Has IPv6: true
Created: 2026-05-08T03:27:19.000Z
Status
- Client: redacted
- Server: zepto-sin-1
- Status: unconfigured
- Resolver: 162.158.161.44
Top
| lightnode-mnl | 34 ms | (ultralow2) | |
| anexia-hkg | 46 ms | ||
| zepto-sin | 56 ms | ||
| anexia-sin | 61 ms | ||
| zepto-hkg | 78 ms | ||
| zepto-hkg (IPv6) | 79 ms | ||
| zepto-tpe | 86 ms | ||
| lightnode-sgn | 97 ms | ||
| lightnode-tpe | 99 ms | ||
| anexia-sin (IPv6) | 182 ms | ||
| zepto-tpe (IPv6) | 204 ms | ||
| premiumrdp-mnl | 200 ms | (ultralow1) | |
| anexia-hkg (IPv6) | 218 ms | ||
| ▶︎ | zepto-sin (IPv6) | 236 ms | |
| viettel-sgn | 244 ms | ||
| viettel-sgn (IPv6) | 252 ms |
1 reply
-
Using custom DNS bypasses your ISP’s DNS resolver, but it does not bypass your ISP’s actual network routing. Your ISP still decides how traffic reaches the destination service. So if the service is hosted farther away and doesn’t have nearby CDN/cache nodes, you may still end up connecting to a higher latency location regardless of which DNS provider you use. DNS helps resolve where to go — it doesn’t control the physical network path afterward.
Content aside
- 3 hrs agoLast active
- 1Replies
- 71Views
-
2
Following