Anycast from Chicago is resolving to Melbourne, causing high latency on initial DNS lookups

Diag report: https://nextdns.io/diag/e664e1e0-70a2-11f1-a02c-e9a853b77f77

Client IP: 65.79.146.38

I'm using your anycast servers (45.90.28.210 / 45.90.30.210). Your own diag tool shows they're connecting me to your Melbourne server at 212 ms, and the backup to Taipei at 182 ms.

But I'm in the US near Chicago. When the tool tests your Chicago servers directly, they respond in 9–17 ms — about 20x faster. So a fast path clearly exists through my ISP; the anycast routing just isn't using it.

The traceroutes in the report show exactly where it goes wrong: the connection is fine and fast in the US (~70 ms) up to a hop on your network (IP 206.148.24.2), then suddenly jumps to ~220 ms and heads to Australia.

Can you please fix the anycast routing for my location so it points to Chicago instead of Melbourne/Taipei? Happy to run the diag tool again if it helps.

Thanks!