Well, it's the persistent problem reported numerous times in all versions of this thread where traffic to Australia is routed via the Hong Kong and US, instead of directly to Australia, via Singapore. It started back when the cable broke and traffic, understandably, was routed via the US.
Since then, it has constantly occurred where when the IP address is 61.6.x.*, when x is above 150, it's fine and traffic is routed directly to Australia - latencies are slightly over 100.
However, when x is 125 and below, it's routed via the US - latencies are constantly above 200.
Have not reliably gotten IPs where x is between 125 and 150, so can't comment on those.
So, having said that, maybe you can provide feedback to the tech personnel at TIME, and get them to look into it, and rectify the problem.
And here's a current tracert, where the routing to
equinix.com (8) in the US clearly is the problem
CODE
Tracing route to 103.4.115.248 over a maximum of 30 hops
 1   3 ms   3 ms   10 ms  ag-01-glsfb.ni.time.net.my [223.28.0.216]
 2   3 ms   3 ms   3 ms  ae2-er-01-glsfb.ni.time.net.my [223.28.26.41]
 3   17 ms   26 ms   12 ms  223.28.2.1
 4   10 ms   9 ms   20 ms  Bundle-Ether1-br-01-mciwg.ni.time.net.my [223.28.26.82]
 5   10 ms   20 ms   10 ms  ae-2.edge-gw-1-sin-pip.sg.globaltransit.net [124.158.226.149]
 6   10 ms   9 ms   10 ms  xe-0-1-0-1.cr-gw-1-sin-pip.sg.globaltransit.net [124.158.224.237]
 7   10 ms   11 ms   13 ms  xe-0-0-2-0.pp-gw-1-sin-pip.sg.globaltransit.net [124.158.224.66]
 8  219 ms  219 ms  219 ms  4826.sgw.equinix.com [27.111.228.74]
 9  218 ms  219 ms  219 ms  ten-0-6-0-4.cor01.per02.wa.vocus.net.au [114.31.206.98]
10  222 ms  222 ms  222 ms  BE-102.cor01.syd11.nsw.VOCUS.net.au [114.31.206.128]
11  223 ms  233 ms  222 ms  bundle-100.bdr01.syd03.nsw.vocus.net.au [114.31.192.85]
12  222 ms  222 ms  231 ms  static-73.7.255.49.in-addr.VOCUS.net.au [49.255.7.73]
13  223 ms  231 ms  223 ms  xe-1-0-0.gw101.sy1.ap.equinix.com [27.111.240.140]
14  222 ms  222 ms  221 ms  27.111.240.17
15  222 ms  233 ms  223 ms  27.111.251.106
16  222 ms  222 ms  222 ms  103.4.115.248
Trace complete.
versus what the routing should be (taken from this very same topic (v3) back in Nov 2016)
CODE
 1   <1 ms   <1 ms   <1 ms  192.168.1.1
 2   2 ms   2 ms   2 ms  ag-01-glsfb.ni.time.net.my [223.28.0.216]
 3   2 ms   1 ms   1 ms  ae2-er-01-glsfb.ni.time.net.my [223.28.26.41]
 4   14 ms   15 ms   15 ms  223.28.2.1
 5   8 ms   8 ms   8 ms  Bundle-Ether1-br-01-mciwg.ni.time.net.my [223.28.26.82]
 6   8 ms   8 ms   8 ms  124.158.226.149
 7   8 ms   8 ms   8 ms  xe-0-1-0-1.cr-gw-1-sin-pip.sg.globaltransit.net [124.158.224.237]
 8   8 ms   8 ms   8 ms  xe-0-0-2-0.pp-gw-1-sin-pip.sg.globaltransit.net [124.158.224.66]
 9   8 ms   8 ms   9 ms  4826.sgw.equinix.com [27.111.228.74]
10  103 ms  103 ms  103 ms  ge-0-1-0-15.cor02.per02.wa.VOCUS.net.au [114.31.206.98]
11  103 ms  103 ms  103 ms  bundle-102.cor03.syd03.nsw.vocus.net.au [114.31.206.128]
12  102 ms  102 ms  102 ms  ten-1-0-0.bdr03.syd04.nsw.VOCUS.net.au [175.45.72.73]
13   99 ms  139 ms   99 ms  as17819.cust.bdr03.syd04.nsw.VOCUS.net.au [175.45.73.194]
14   99 ms   99 ms   99 ms  27.111.251.106
15  103 ms  102 ms  102 ms  103.4.115.248
I'll provide another ~100ms tracert again, as soon as I can power-cycle myself back onto a 'good' IP address.
Very good findings indeed... I will forward to the network team to check.
Thanks.