TPG routing to Japan (Tokyo) is not optimal

[localjrw]

Does anyone know why routing to Japan (Tokyo) is going via the United States (LA)? 

It adds a 100+ msec latency to traffic and makes gaming on any asian servers largely unworkable.

For some reason a speed test performs properly (see attached screenshot).

A VPN to Tokyo will also work and bypass this routing issue.

Here is my tracert for a gaming server in an Alibaba data centre Tokyo, Japan.

The latency is awful at 236 msec because the traffic is going to Los Angeles and my game confirms this latency in the top corner of the screen.

C:\>tracert 47.91.24.239

Tracing route to 47.91.24.239 over a maximum of 30 hops

1 2 ms 13 ms 11 ms ARCHER_VR1600V [10.1.1.1]
2 9 ms 7 ms 6 ms 10.20.26.82
3 8 ms 8 ms 8 ms 60-240-241-194.static.tpgi.com.au [60.240.241.194]
4 20 ms 20 ms 20 ms syd-gls-har-crt2-BE20.tpgi.com.au [203.26.22.57]
5 24 ms 20 ms 21 ms syd-gls-har-int1-hu0-3-0-3.tpgi.com.au [203.221.3.67]
6 166 ms 166 ms 167 ms las-b24-link.ip.twelve99.net [213.248.95.232]
7 166 ms 166 ms 166 ms lax-b23-link.ip.twelve99.net [62.115.143.38]
8 173 ms 173 ms 171 ms sjo-b23-link.ip.twelve99.net [62.115.116.40]
9 220 ms 220 ms 220 ms bbixusainc-svc075529-lag003674.ip.twelve99-cust.net [62.115.50.6]
10 * * * Request timed out.
11 230 ms 235 ms 229 ms 101.203.70.86
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 235 ms 234 ms 236 ms 47.91.24.239

Trace complete.

Does anyone know why TPG does this routing or how to fix it?

[Shane]

Hi @localjrw,

Let us help check this latency issue and get to the bottom of this. Could you shoot us a PM with your details to better understand the situation.

How to send a PM?

Regards,

Does anyone know why routing to Japan (Tokyo) is going via the United States (LA)? 

It adds a 100+ msec latency to traffic and makes gaming on any asian servers largely unworkable.

For some reason a speed test performs properly (see attached screenshot).

A VPN to Tokyo will also work and bypass this routing issue.

Here is my tracert for a gaming server in an Alibaba data centre Tokyo, Japan.

The latency is awful at 236 msec because the traffic is going to Los Angeles and my game confirms this latency in the top corner of the screen.

C:\>tracert 47.91.24.239

Tracing route to 47.91.24.239 over a maximum of 30 hops

1 2 ms 13 ms 11 ms ARCHER_VR1600V [10.1.1.1]
2 9 ms 7 ms 6 ms 10.20.26.82
3 8 ms 8 ms 8 ms 60-240-241-194.static.tpgi.com.au [60.240.241.194]
4 20 ms 20 ms 20 ms syd-gls-har-crt2-BE20.tpgi.com.au [203.26.22.57]
5 24 ms 20 ms 21 ms syd-gls-har-int1-hu0-3-0-3.tpgi.com.au [203.221.3.67]
6 166 ms 166 ms 167 ms las-b24-link.ip.twelve99.net [213.248.95.232]
7 166 ms 166 ms 166 ms lax-b23-link.ip.twelve99.net [62.115.143.38]
8 173 ms 173 ms 171 ms sjo-b23-link.ip.twelve99.net [62.115.116.40]
9 220 ms 220 ms 220 ms bbixusainc-svc075529-lag003674.ip.twelve99-cust.net [62.115.50.6]
10 * * * Request timed out.
11 230 ms 235 ms 229 ms 101.203.70.86
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 235 ms 234 ms 236 ms 47.91.24.239

Trace complete.

Does anyone know why TPG does this routing or how to fix it?

[pdpanozzo]

This issue appeared to be fixed around a month ago, but as of this morning it is now happening again. Below are the results of a trace route I did this morning.

4 7 ms 7 ms 7 ms syd-gls-har-crt2-be-40.tpg.com.au [202.7.173.101]
5 13 ms 7 ms 7 ms syd-gls-har-int1-he0-3-0-2.tpgi.com.au [203.221.3.3]
6 164 ms 164 ms 163 ms las-b24-link.ip.twelve99.net [213.248.95.232]
7 161 ms 160 ms 161 ms lax-b23-link.ip.twelve99.net [62.115.143.38]
8 160 ms 160 ms 161 ms sjo-b23-link.ip.twelve99.net [62.115.116.40]
9 216 ms 215 ms 215 ms bbixusainc-svc075529-lag003674.ip.twelve99-cust.net [62.115.50.6]
10 * * * Request timed out.
11 262 ms 261 ms 260 ms 101.203.70.86
12 263 ms 264 ms * 116.251.83.81
13 * * * Request timed out.
14 * * * Request timed out.
15 262 ms 262 ms 262 ms 47.91.24.239

[localjrw]

Agree. About a month ago it was fixed. As of this morning (30/11/2022) the routing issue is back again.

[BasilDV]

Hi @pdpanozzo and @localjrw

Kindly send me a PM with your account details to check on this further.

BasilDV

[pdpanozzo]

Thanks for your help, the issue as of this morning has been resolved.

For anyone who is interested this is what the trace route should look like.

4 8 ms 7 ms 8 ms syd-gls-har-crt3-be-40.tpg.com.au [202.7.173.69]
5 9 ms 7 ms 7 ms syd-gls-har-int2-be100.tpgi.com.au [203.221.3.4]
6 107 ms 115 ms 110 ms ix-xe-1-1-2-0.tcore1.tv2-tokyo.as6453.net [180.87.181.192]
7 108 ms 107 ms 109 ms if-et-15-2.hcore1.ovc-tokyo.as6453.net [120.29.217.10]
8 108 ms 107 ms 107 ms softbank221110034233.bbtec.net [221.110.34.233]
9 * * * Request timed out.
10 157 ms 155 ms 155 ms 101.203.70.86
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 162 ms 161 ms 161 ms 47.91.24.239

[BasilDV]

Glad that this has been resolved @pdpanozzo.

Have a good day!

BasilDV