Incorrect POP selection for NextDNS users in Lobito, Angola

Hello NextDNS Support,

I am located in Lobito, Benguela, Angola, and I have configured NextDNS on my router so that all devices on my network use NextDNS.

I am experiencing what appears to be an incorrect POP selection. The NextDNS test is selecting netbarista-par at ~212 ms, even though there is a much lower-latency NextDNS location available in Johannesburg, South Africa (vultr-jnb) at ~64 ms.

My current test results are:

vultr-jnb       64 ms
zepto-jnb       65 ms
edgeuno-for    117 ms
zepto-sao      119 ms
netbarista-par 212 ms <-- selected POP
zepto-los       220 ms
edis-skp        229 ms
zepto-ath       232 ms
netshop-nic     258 ms
lightnode-cai   271 ms
lightnode-run   271 ms
anexia-ath      error

Copy

The important point is that Johannesburg is responding at approximately 64–65 ms, while the currently selected São Paulo POP is approximately 119 ms, resulting in almost an additional 55 ms of latency for DNS queries.

Could you please investigate why the NextDNS anycast/routing system is selecting the São Paulo POP rather than the Johannesburg POP for my connection in Angola?

I understand that NextDNS POP selection is based on network routing/anycast rather than simply geographical distance, so I would particularly like to know whether the BGP/anycast routing from my ISP in Angola is causing the incorrect POP to be selected.

Location: Lobito, Benguela, Angola
ISP: ZAP Fibra
Connection: FTTH
Configuration: NextDNS configured directly on the router
Expected/observed: Johannesburg ~64 ms vs São Paulo ~119 ms

I can provide additional information such as my public IP, traceroutes, nextdns test output, or other diagnostics if required.

Could you please check the routing/POP selection for my network?

Thank you.