Routing issue to zetta-bne

Hi,

For some reason, connecting to zetta-bne is being routed down to Sydney then back to Brisbane. This never used to be the case - I'm not sure exactly when it started but it's within the last few months.

traceroute to 119.252.95.133 (119.252.95.133), 64 hops max, 52 byte packets
 1  mtik-primary-gw (10.0.0.254)  5.318 ms  3.355 ms  3.246 ms
 2  <irrelevant next hop>  5.149 ms  4.634 ms  5.866 ms
3 vl101.pe02.bri01.launtel.net.au (203.12.2.249) 5.940 ms 6.061 ms 5.184 ms
4 as58511.qld.ix.asn.au (218.100.76.10) 5.731 ms 4.413 ms 4.814 ms
5 et-0-0-6.cor101.ndcb1.au.as58511.net (103.30.218.118) 30.881 ms 22.128 ms 22.052 ms
6 et-0-0-7.cor102.ndcb1.au.as58511.net (103.30.218.137) 22.790 ms 21.487 ms 21.766 ms
7 et-0-0-15.cor102.eqsy3.au.as58511.net (103.30.217.134) 1187.044 ms 877.279 ms 645.361 ms
8 ae1-200g.bdr101.eqsy3.au.as58511.net (103.30.217.169) 23.444 ms 22.056 ms 21.495 ms
9 ce.7004955-1.as58511.net (103.17.223.110) 38.482 ms 22.077 ms 23.004 ms
10 et-0-672-rt1-sydbo.zettagrid.com (203.7.224.181) 20.234 ms 25.128 ms 18.911 ms
11 xe0-2-954-rt1-briwh.zettagrid.com (203.7.224.173) 31.118 ms 30.909 ms 30.861 ms
12  *^C

Have spoken with my ISP and they advised the following:

OK so looking at that trace from the BNG, you can see as58511.qld.ix.asn.au

That's the IX-AU peering - at that point we have little control over it.

I would say they have either decided to not peer their IP in QLD or that they have had a failure and are serving it out of NSW

-------

I've hard coded a static dns entry to go anexia-bne, as my first anycast IP has a latency of:

18     45.90.28.0  259ms 258ms 258ms. 

anexia-bne works fine (2ms) and I have gsl-syd as a secondary A record but it would be nice if there was a quick remediation of whatever peering issue is causing the bad routing for zetta through IX. 

I posted the diag result with my email address included, url ending in 953bf7c9b2b9 (don't want to post URL publicly as my ipv6 range isn't redacted).

Thanks :)