Unexpected route to anycast network

desec.io shows a location of ns1.desec.io in Sydney. When I check the route from Melbourne to 45.54.76.1 (v4 of ns1.desec.io) with the online traceroute at https://www.telstra.net/cgi-bin/trace, I would expect a routing to the Sydney location with low latency. Instead, I see it first routes to Sydney in about 13ms (good), but then, the route seems to continue in the US taking about 190ms. Is this online tool somehow misleading? Or is the routing to your anycast network configured in a non-optimal way?

Complete traceroute result:

 1  gigabitethernet3-3.exi1.melbourne.telstra.net (203.50.77.49)  0.807 ms  0.721 ms  0.744 ms
 2  TenGigE0-0-0-21.lon-dlr20.melbourne.telstra.net (203.50.233.22)  0.744 ms  0.612 ms  0.620 ms
 3  bundle-ether30.exi-core30.melbourne.telstra.net (203.50.11.246)  3.617 ms  1.487 ms  1.995 ms
 4  bundle-ether2.cla-core30.melbourne.telstra.net (203.50.13.124)  2.244 ms  2.736 ms  0.996 ms
 5  bundle-ether3.hay-core30.sydney.telstra.net (203.50.13.132)  12.365 ms  13.606 ms  13.238 ms
 6  bundle-ether19.ken-core10.sydney.telstra.net (203.50.13.146)  13.486 ms  13.106 ms  14.114 ms
 7  bundle-ether1.pad-gw11.sydney.telstra.net (203.50.6.61)  14.237 ms  13.355 ms  13.362 ms
 8  203.50.13.90 (203.50.13.90)  13.863 ms  12.857 ms  12.864 ms
 9  203.50.13.90 (203.50.13.90)  147.536 ms  148.779 ms  149.034 ms
10  i-20802.eqnx-core02.telstraglobal.net (202.84.141.25)  147.660 ms  149.402 ms  149.408 ms
11  i-92.eqnx03.telstraglobal.net (202.84.247.17)  147.286 ms  147.278 ms  147.160 ms
12  sjo-b21-link.ip.twelve99.net (213.248.75.146)  147.159 ms  147.028 ms  147.161 ms
13  ntt-ic323771-sjo-b21.ip.twelve99-cust.net (62.115.12.53)  147.534 ms  147.296 ms  147.385 ms
14  ae-10.r25.snjsca04.us.bb.gin.ntt.net (129.250.3.174)  147.907 ms  168.759 ms  147.411 ms
15  ae-8.r21.dllstx14.us.bb.gin.ntt.net (129.250.4.155)  189.384 ms  195.500 ms  189.637 ms
16  ae-1.a01.dllstx14.us.bb.gin.ntt.net (129.250.4.30)  189.135 ms  190.753 ms  189.261 ms

Hi Lukas,

Thanks for your message, and welcome to deSEC! :slight_smile:

We consulted with our datacenter, and here’s their response:

I was able to confirm and resolve a specific issue with Telstra in Sydney and the reported issue is now clear. A retest with the tool listed now reaches our edge in Sydney. It looks like this was just a Telstra issue and peering with other ISPs in the region was unaffected.

:tada:

Stay secure,
Peter