High latency to Singapore server caused by TPG routing

[Eric123]

@Anonymous @david64 @waynezth 

Found this link in the game forum:

https://forum.albiononline.com/index.php/Thread/175614-Australia-to-Asia-server-235-ping/

We talked to our hoster (GCore) about the high ping issues from Australia. What they found out is this: Australian internet provider "TPG Internet" is "announcing" (this is a technical term) their IP range in way that causes all traffic from Australia to Singapore (and the other way around) to be routed via the US, hence the ping is a lot higher than necessary.

The best course of action is for customers of TPG Internet to contact technical support directly. They should open support cases with the following information:

* they are playing an online game and have a very bad ping
* the game servers are located in Singapore
* the IP range of the game servers is 5.45.187.0/24
* problem is that TPG Internet announces their IP ranges in a way that causes traffic from AU to SGP to be routed via the US, for example 61.69.212.0/24, 123.243.158.0/24, 194.193.192.0/24 and others
* i.e. TPG Internet need to announce their IP ranges in SGP properly

Hopefully this will help!

[Eric123]

@Anonymous 

The latency have just increased back to 250ms+ again.

Tracert from Gcore (AS199524) (game server host) and Arelion (AS1299) (Singapore Equinix SG1 snge-b5) (the other end of the connection between Perth and Singapore) to my current IP address shows routing from Singapore -> Japan -> US -> Japan -> Sydney ->Melbourne.

https://lg.gcore.lu/

https://lg.twelve99.net/

My current IP: 203.214.52.*** 

Current tracert result:

Tracing route to 5.45.187.10 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 2 ms 2 ms 2 ms 10.20.26.102
3 3 ms 3 ms 2 ms 27-32-160-2.static.tpgi.com.au [27.32.160.2]
4 87 ms 87 ms 87 ms nme-sot-dry-agr1-Po40.tpgi.com.au [203.219.107.230]
5 88 ms 88 ms 88 ms per-apt-stg-crt2-be10.tpgi.com.au [203.219.58.185]
6 88 ms 88 ms 88 ms per-apt-stg-crt1-be200.tpgi.com.au [203.219.57.193]
7 88 ms 88 ms 87 ms sin-eqx-aye-int1-Hu-0-0-0-20.tpg.com.au [203.219.107.114]
8 224 ms * 224 ms snge-b5-link.ip.twelve99.net [80.239.193.122]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 226 ms 225 ms 226 ms 95.85.74.1
13 208 ms 209 ms 214 ms 5.45.187.10

Trace complete.

Gcore results:

traceroute to 203.214.52.0 (203.214.52.0), 15 hops max, 60 byte packets
1 vrrp.gcore.lu (92.223.85.2) [AS199524/AS202422] 0.185 ms
2 10.255.48.196 (10.255.48.196) [*] 0.453 ms
3 10.255.48.205 (10.255.48.205) [*] 0.996 ms
4 *
5 *
6 lax-b23-link.ip.twelve99.net (62.115.143.244) [AS1299] 171.894 ms
7 lax-b22-link.ip.twelve99.net (62.115.143.39) [AS1299] 191.152 ms
8 tpg-ic-322668.ip.twelve99-cust.net (213.248.95.233) [AS1299] 322.721 ms
9 syd-gls-har-crt4-be-200.tpg.com.au (203.221.3.104) [AS9942] 213.167 ms
10 tpg-ic-322668.ip.twelve99-cust.net (213.248.95.233) [AS1299] 338.622 ms
11 syd-sot-ken2-csw1-tg-4-2.tpgi.com.au (202.7.171.238) [AS7545/AS10026] 203.237 ms
12 27-32-160-88.static.tpgi.com.au (27.32.160.88) [AS7545] 224.267 ms
13 *
14 27-32-160-88.static.tpgi.com.au (27.32.160.88) [AS7545] 216.485 ms
15 *

Arelion result:

Router: snge-b5 / Singapore (Equinix SG1)
Command: traceroute 203.214.52.0

traceroute to 203.214.52.0 (203.214.52.0), 30 hops max, 60 byte packets
1 osa-b1-link.ip.twelve99.net (62.115.112.13) 72.393 ms * *
2 lax-b23-link.ip.twelve99.net (62.115.142.128) 182.060 ms tky-b3-link.ip.twelve99.net (62.115.126.135) 185.352 ms 185.356 ms
3 osa-b1-link.ip.twelve99.net (62.115.115.63) 92.989 ms lax-b23-link.ip.twelve99.net (62.115.142.128) 188.798 ms *
4 tpg-ic-322668.ip.twelve99-cust.net (213.248.95.233) 321.681 ms 345.682 ms 329.631 ms
5 syd-gls-har-crt3-be-100.tpg.com.au (203.221.3.33) 208.581 ms tpg-ic-322668.ip.twelve99-cust.net (213.248.95.233) 337.639 ms 345.543 ms
6 tpg-ic-322668.ip.twelve99-cust.net (213.248.95.233) 337.561 ms syd-gls-har-crt3-be-100.tpg.com.au (203.221.3.33) 218.404 ms 218.119 ms
7 syd-sot-ken-crs2-Te-0-6-0-10.tpgi.com.au (203.26.22.118) 210.898 ms 223.310 ms adl-ts3-2600-106.tpgi.com.au (203.29.135.106) 221.707 ms
8 27-32-160-88.static.tpgi.com.au (27.32.160.88) 211.155 ms 27-32-160-24.static.tpgi.com.au (27.32.160.24) 200.930 ms syd-sot-ken-crs2-Te-0-6-0-10.tpgi.com.au (203.26.22.118) 209.327 ms
9 * nme-apt-bur-crt2-te-gi-0-7-0-17.tpgi.com.au (202.7.171.234) 216.427 ms *
10 * * *
11 * * *

[Eric123]

@Anonymous 

Just to add. Tracert result from Gcore and Arelion looking glass to my current local gateway (27.32.160.2) shows optimal latency (86ms), which again suggest TPG did not announces some of the IP correctly and causes traffic from AU to SGP to be routed via the US.

Arelion results:

Router: snge-b5 / Singapore (Equinix SG1)
Command: traceroute 27.32.160.2

traceroute to 27.32.160.2 (27.32.160.2), 30 hops max, 60 byte packets
1 tpg-ic-372709.ip.twelve99-cust.net (80.239.193.123) 0.895 ms 0.941 ms 1.032 ms
2 per-apt-stg-crt1-Hu-0-2-0-3.tpg.com.au (203.219.107.113) 46.808 ms 46.814 ms 46.800 ms
3 per-pow-stg-crt3-be10.tpgi.com.au (203.219.58.178) 86.295 ms 86.311 ms nme-apt-bur-crt1-be60.tpgi.com.au (203.219.57.13) 84.697 ms
4 nme-apt-bur-crt2-te-gi-0-7-0-17.tpgi.com.au (202.7.171.234) 84.975 ms nme-sot-dry-crt1-Be40.tpgi.com.au (203.219.107.225) 87.091 ms 87.209 ms
5 * 27-32-160-2.static.tpgi.com.au (27.32.160.2) 85.623 ms *

Gcore results:

traceroute to 27.32.160.2 (27.32.160.2), 15 hops max, 60 byte packets
1 vrrp.gcore.lu (92.223.85.2) [AS199524/AS202422] 0.133 ms
2 10.255.48.196 (10.255.48.196) [*] 0.463 ms
3 10.255.48.205 (10.255.48.205) [*] 1.326 ms
4 7545.sgw.equinix.com (27.111.229.211) [*] 1.755 ms
5 7545.sgw.equinix.com (27.111.229.211) [*] 1.571 ms
6 nme-apt-bur-crt1-be60.tpgi.com.au (203.219.57.13) [AS7545] 85.086 ms
7 nme-sot-dry-crt1-Be40.tpgi.com.au (203.219.107.225) [AS7545] 87.817 ms
8 *
9 27-32-160-2.static.tpgi.com.au (27.32.160.2) [AS7545] 86.272 ms

[BasilDV]

Hi @Eric123

We'll chase this with your case manager and have him to call you within the day for further discussion.

BasilDV

[Eric123]

Hi @BasilDV @Anonymous @david64 @waynezth 

Just got off the phone with the costumer retention team. The response I got was that TPG technical team assess that there is no issue with the service provided and everything meets there expectation. I was given two options to either stay or leave TPG. It's shocking that TPG do not even recognize this as an issue, nor have any desire to improve your network performance, despite all the evidence and troubleshooting provided by the customer.

It's sad to say after being a loyal customer for over a decade, but we will have to look for other providers if this issue cannot be resolved.