TPG Community

Get online support

Pings to Asia have doubled this week.

Pinkyoshi
Level 2

I normally get under 130 ping to Hong Kong , but this week the pings have doubled to 250

 

tried getting new ips by resetting etc, no avail

 

when using either expressvpn or mullvad i get sub 140 pings

 

seems the routing has changed last week

 

C:\Users\Mee>ping 159.138.26.73

Pinging 159.138.26.73 with 32 bytes of data:
Reply from 159.138.26.73: bytes=32 time=245ms TTL=43
Reply from 159.138.26.73: bytes=32 time=245ms TTL=43
Reply from 159.138.26.73: bytes=32 time=245ms TTL=43
Reply from 159.138.26.73: bytes=32 time=244ms TTL=43

Ping statistics for 159.138.26.73:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 244ms, Maximum = 245ms, Average = 244ms

C:\Users\Mee>ping 159.138.26.73

Pinging 159.138.26.73 with 32 bytes of data:
Reply from 159.138.26.73: bytes=32 time=138ms TTL=46
Reply from 159.138.26.73: bytes=32 time=138ms TTL=46
Reply from 159.138.26.73: bytes=32 time=138ms TTL=46
Reply from 159.138.26.73: bytes=32 time=139ms TTL=46

 

C:\Users\Mee>tracert 159.138.26.73

Tracing route to ecs-159-138-26-73.compute.hwclouds-dns.com [159.138.26.73]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 13 ms 13 ms 13 ms 10.20.26.20
3 14 ms 15 ms 14 ms syd-apt-XXX-int2-be100.tpgi.com.au [203.29.134.4]
4 155 ms 155 ms 155 ms ix-xe-0-0-1-0.tcore1.hk2-hongkong.as6453.net [116.0.67.46]
5 155 ms 155 ms 155 ms if-be-46-2.ecore1.hk2-hongkong.as6453.net [116.0.67.5]
6 156 ms 155 ms 155 ms 180.87.169.11
7 243 ms 243 ms 243 ms HundredGE0-1-0-0.br03.hkg08.pccwbtn.net [63.223.29.142]
8 243 ms 242 ms 243 ms HundredGE0-1-0-0.br03.hkg08.pccwbtn.net [63.223.29.142]
9 243 ms 243 ms 243 ms 63-216-156-26.static.pccwglobal.net [63.216.156.26]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * ^C
C:\Users\Mee>tracert 159.138.26.73

Tracing route to ecs-159-138-26-73.compute.hwclouds-dns.com [159.138.26.73]
over a maximum of 30 hops:

1 17 ms 14 ms 14 ms 10.64.0.1
2 25 ms 27 ms 27 ms vlan96.as03.syd1.au.m247.com [89.44.10.1]
3 15 ms 15 ms 15 ms 37.120.220.210
4 17 ms 14 ms 15 ms 217.138.223.72
5 14 ms 14 ms 14 ms 113.29.26.249
6 15 ms 16 ms 16 ms ae2.3608.edge4.Sydney1.level3.net [4.69.208.206]
7 66 ms 24 ms 14 ms NTT-level3-Syndey1.Level3.net [4.68.38.206]
8 16 ms 15 ms 15 ms ae-1.r21.sydnau03.au.bb.gin.ntt.net [129.250.5.44]
9 * * * Request timed out.
10 137 ms 138 ms 147 ms ae-10.r27.tkokhk01.hk.bb.gin.ntt.net [129.250.7.67]
11 138 ms 138 ms 139 ms ae-1.a01.tkokhk01.hk.bb.gin.ntt.net [129.250.5.36]
12 294 ms 294 ms 294 ms ae-0.huawei.tkokhk01.hk.bb.gin.ntt.net [203.131.240.194]
13 * * * Request timed out.
14 * * * Request timed out.
15 140 ms 139 ms 139 ms 11.92.129.147
16 * * * Request timed out.
17 * * * Request timed out.
18 ^C

 

 

 

 

3 REPLIES 3
Ahra_G
Moderator

Hi @Pinkyoshi

 

Could you please also do trace route? Is this your typical ping results? 

 

Thanks! 

Ahra_G

Pinkyoshi
Level 2

bottom 2 tracerts are without and with vpn

 

without vpn

 

C:\Users\Mee>tracert 159.138.26.73

Tracing route to ecs-159-138-26-73.compute.hwclouds-dns.com [159.138.26.73]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 * * 15 ms syd-apt-XXX-int2-be100.tpgi.com.au [203.29.134.4]
4 155 ms 155 ms 155 ms ix-xe-0-0-1-0.tcore1.hk2-hongkong.as6453.net [116.0.67.46]
5 156 ms 156 ms 156 ms if-be-46-2.ecore1.hk2-hongkong.as6453.net [116.0.67.5]
6 156 ms 155 ms 156 ms 180.87.169.11
7 243 ms 243 ms 243 ms HundredGE0-2-0-0.br03.hkg08.pccwbtn.net [63.223.29.170]
8 244 ms 244 ms 244 ms 63-216-156-26.static.pccwglobal.net [63.216.156.26]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * 252 ms 246 ms 11.92.129.133
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * ^C
C:\Users\Mee>

 

 

with vpn

 

C:\Users\Mee>tracert 159.138.26.73

Tracing route to ecs-159-138-26-73.compute.hwclouds-dns.com [159.138.26.73]
over a maximum of 30 hops:

1 13 ms 18 ms 14 ms 10.64.0.1
2 14 ms 15 ms 14 ms vlan96.as03.syd1.au.m247.com [89.44.10.1]
3 15 ms 15 ms 15 ms 37.120.220.210
4 14 ms 15 ms 14 ms 217.138.223.72
5 14 ms 14 ms 14 ms 113.29.26.249
6 15 ms 15 ms 14 ms ae2.3608.edge4.Sydney1.level3.net [4.69.208.206]
7 16 ms 37 ms 15 ms NTT-level3-Syndey1.Level3.net [4.68.38.206]
8 31 ms 22 ms 15 ms ae-1.r21.sydnau03.au.bb.gin.ntt.net [129.250.5.44]
9 106 ms * 112 ms ae-8.r22.sngpsi07.sg.bb.gin.ntt.net [129.250.6.144]
10 * * * Request timed out.
11 159 ms 144 ms 138 ms ae-1.a01.tkokhk01.hk.bb.gin.ntt.net [129.250.5.36]
12 291 ms 292 ms 291 ms ae-0.huawei.tkokhk01.hk.bb.gin.ntt.net [203.131.240.194]
13 * * * Request timed out.
14 * * * Request timed out.
15 142 ms 138 ms 139 ms 11.92.129.147
16 * 147 ms 140 ms 11.92.129.131
17 * ^C

 

 

 

 

BasilDV
Moderator

Hi @Pinkyoshi

 

We'll raise this to our Engineering team for further investigation.

Someone will be in touch with you within 24 to 48 hours once an update becomes available.

 

BasilDV