Anycast secondary IPv6 routing to anexia-ath instead of zepto-lon
Evening,
Once again, IPv6 routing has gone awry from AANET, and this time it's routing the secondary anycast to anexia-ath instead of zepto-lon, which means it's 60 ms latency instead of 10 ms.
Why does this consistently keep happening to IPv6 which ends up with degraded latency as a result? I've never seen it happen with IPv4.
Is any fix in the pipeline for this odd behaviour? Presuming it's some kind of fallback, why does it end up routing to somewhere a long way away with high latency instead of somewhere nearer with better latency?
Diag: https://nextdns.io/diag/ba88acc0-715a-11f0-8da8-dd060582d10a
Cheers,
-Will
8 replies
-
Still the same today...need a fix please!
-
If you aren't running the nextdns-cli already it might be worth a try if you can.
It resolved my issue (I'm in Canberra using AussieBB).
-
Could be worse.. lol.. I have the same issue.. Except anexia-ath is 149ms for me...
https://nextdns.io/diag/fc426b40-7265-11f0-b423-eb7c0ef70556
-
I just noticed on my monitoring that this is now resolved as of a few minutes ago and secondary anycast IPv6 is routing to anexia-lon as it should be.
-
Still broken.
Content aside
- 10 hrs agoLast active
- 8Replies
- 65Views
-
3
Following