0
Issue with wrong routing of Anycast 2 destination - going to zepto-tpe, why?
Hi,
as mentioned in the other post, there is some weird stuff going on within routing of Anycast 2 destination.
It is going to zepto-tpe instead of FRA as destination.
Here the diag:
https://nextdns.io/diag/38d6c9f0-48ac-11ef-ba18-63ff1694e125
Here another output showing the issue:
zepto-tpe (IPv6) 271 ms (anycast2, ultralow2)
zepto-tpe 271 ms (ultralow2)
1 reply
-
We have updated the routing policy, and the changes should take effect within the next 10 minutes. Please try your connection again after this time. If you continue to experience issues, do not hesitate to contact us for further assistance.
Content aside
- 1 mth agoLast active
- 1Replies
- 33Views
-
2
Following