Is there any reason for TPG to be routing traffic to Tokyo through LA in the US? This increases ping to game servers in Tokyo drastically, and seems to only have become a problem in the last few months (starting around mid-October). I've included my traceroute to an Amazon game server in Shibuya, Tokyo, and it shows the data going to LA before going back to Tokyo. The suboptimal routing is also reflected in the in-game ping counters, where they are a constant 263-320ms, which is a huge increase compared to the 150-180ms I had previously.   traceroute to 3.113.217.147 (3.113.217.147), 64 hops max, 52 byte packets 1 10.20.20.240 (10.20.20.240) 12.767 ms 9.530 ms 10.604 ms 2 syd-apt-ros-int1-hu0-3-0-2 (203.29.134.3) 13.623 ms 19.333 ms 12.364 ms 3 ix-hge-0-0-0-15.ecore1.lvw-losangeles.as6453.net (64.86.197.96) 187.945 ms 188.417 ms * 4 * * * 5 if-ae-28-2.tcore2.av3-toyohashi.as6453.net (64.86.252.33) 387.390 ms * * 6 if-ae-2-2.tcore1.av3-toyohashi.as6453.net (180.87.3.130) 341.315 ms * 316.896 ms 7 if-ae-36-2.tcore1.tv2-tokyo.as6453.net (180.87.181.206) 308.346 ms 301.733 ms 302.928 ms 8 180.87.181.22 (180.87.181.22) 301.724 ms 299.457 ms 389.570 ms 9 52.93.251.213 (52.93.251.213) 239.198 ms 52.93.251.217 (52.93.251.217) 246.265 ms 248.323 ms 10 150.222.90.21 (150.222.90.21) 254.756 ms 52.95.30.44 (52.95.30.44) 237.706 ms 52.95.30.62 (52.95.30.62) 245.588 ms 11 * * * 12 52.93.72.117 (52.93.72.117) 261.537 ms 15.230.160.49 (15.230.160.49) 241.594 ms 150.222.242.31 (150.222.242.31) 237.431 ms 13 52.93.72.226 (52.93.72.226) 314.916 ms 52.95.31.228 (52.95.31.228) 302.715 ms 52.93.72.250 (52.93.72.250) 304.026 ms 14 52.93.72.255 (52.93.72.255) 295.734 ms 52.95.31.184 (52.95.31.184) 288.697 ms 52.93.72.227 (52.93.72.227) 333.010 ms 15 15.230.129.15 (15.230.129.15) 289.933 ms 52.95.31.193 (52.95.31.193) 246.341 ms 52.95.31.128 (52.95.31.128) 238.267 ms 16 15.230.129.76 (15.230.129.76) 240.001 ms 15.230.129.66 (15.230.129.66) 246.043 ms 52.95.30.216 (52.95.30.216) 247.207 ms 17 * * * 18 * 15.230.161.196 (15.230.161.196) 258.116 ms * Is there a solution to this routing? ... View more