It's only some connections (typically to game servers it seems) that seem to route via sydney.
For people ( @KiwiTT ? ) wanting to reduce gaming ping with a VPN I've switched to mudfish which is cheaper (pay by bandwidth), more flexible (more exit points to choose from), and no packet loss compared to my previous (wtfast). It's a little more technical to set up but I prefer the flexibility.
Regarding all connections routing via syd...
When I traceroute to overwatch servers (e.g. 24.105.30.129) I can see the syd hops...
1 <1 ms <1 ms <1 ms 10.0.0.1
2 4 ms 3 ms 3 ms 125-239-10-1-adsl.sparkbb.co.nz [125.239.10.1]
3 * 12 ms 11 ms mdr-ip24-int.msc.global-gateway.net.nz [122.56.116.6]
4 11 ms 11 ms 11 ms ae8-10.akbr6.global-gateway.net.nz [122.56.116.5]
5 11 ms 11 ms 11 ms ae7-2.akbr7.global-gateway.net.nz [122.56.119.53]
6 36 ms 35 ms 35 ms xe7-0-4.sgbr3.global-gateway.net.nz [122.56.127.2]
7 36 ms 35 ms 35 ms ae2-10.sgbr4.global-gateway.net.nz [202.50.232.246]
8 37 ms 62 ms 61 ms ae-13.r21.sydnau03.au.bb.gin.ntt.net [103.13.80.125]
9 150 ms 147 ms 151 ms ae-11.r31.tokyjp05.jp.bb.gin.ntt.net [129.250.5.34]
10 153 ms 151 ms 151 ms ae-3.r00.tokyjp08.jp.bb.gin.ntt.net [129.250.6.129]
11 151 ms 158 ms 160 ms ae-1.a00.tokyjp03.jp.bb.gin.ntt.net [129.250.5.51]
12 151 ms 151 ms 151 ms 61.213.179.114
13 223 ms 223 ms 253 ms et-0-0-48-br01-eqty2.blizzardonline.net [137.221.81.33]
...
16 222 ms 223 ms 223 ms 24.105.30.129
Then if I enable mudfish for overwatch it adds entries to the routing tables for the ranges that overwatch gameservers sit on to make windows use it's TAP adapter for those IPs and tunnels everything going through that adapter to, say, a ColoCrossing exit node that drops my ICMP RTT to 180. The route to ColoCrossing (i.e. the route that the VPN is tunneling connections to overwatch through) doesn't seem to be going via sydney at least as far as I can see from the hostnames, IP location lookups, and timing (syd is normally 35-45ms as seen in above traceroute):
Tracing route to node-us-00188.mudfish.net [104.168.154.66]
over a maximum of 30 hops:
1 <1 ms * <1 ms 10.0.0.1
2 4 ms 3 ms 3 ms 125-239-10-1-adsl.sparkbb.co.nz [125.239.10.1]
3 * * 12 ms mdr-ip24-int.msc.global-gateway.net.nz [122.56.116.6]
4 12 ms 11 ms 11 ms ae8-10.akbr6.global-gateway.net.nz [122.56.116.5]
5 13 ms 11 ms 10 ms ae7-2.akbr7.global-gateway.net.nz [122.56.119.53]
6 12 ms 11 ms 15 ms ae10-10.tkbr12.global-gateway.net.nz [202.50.232.29]
7 135 ms 135 ms 135 ms xe7-0-1-10.lebr7.global-gateway.net.nz [202.50.232.162]
8 143 ms 143 ms 139 ms ae3-10.sjbr3.global-gateway.net.nz [122.56.127.25]
9 169 ms 167 ms 167 ms ae0.pabr5.global-gateway.net.nz [203.96.120.74]
10 146 ms 147 ms 147 ms ae-8.r06.plalca01.us.bb.gin.ntt.net [129.250.203.41]
11 192 ms 195 ms 195 ms ae-15.r02.snjsca04.us.bb.gin.ntt.net [129.250.4.119]
12 170 ms 171 ms 171 ms ae-11.r23.snjsca04.us.bb.gin.ntt.net [129.250.6.118]
13 163 ms * 164 ms ae-3.r23.sttlwa01.us.bb.gin.ntt.net [129.250.3.125]
14 164 ms 163 ms 163 ms ae-29.r05.sttlwa01.us.bb.gin.ntt.net [129.250.2.89]
15 163 ms 167 ms 162 ms ae-1.a00.sttlwa01.us.bb.gin.ntt.net [129.250.5.134]
16 160 ms 159 ms 159 ms xe-0-0-25-2.a00.sttlwa01.us.ce.gin.ntt.net [157.238.64.158]
17 164 ms 163 ms 163 ms client-104-168-131-13.hostwindsdns.com [104.168.131.13]
18 161 ms 159 ms 159 ms client-104-168-154-66.hostwindsdns.com [104.168.154.66]
Trace complete.
I can then do a traceroute to the overwatch servers with the VPN enabled (using that ColoCrossing exit node) and see how the first hop has 160MS consistent with being tunneled through the route above and then the remaining hops take it up to 180.
@hio77 are you saying that the route to ColoCrossing is actually routing via sydney as well?