TPG Community

Get online support
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Ask a Question

High latency recently on Hong Kong servers.

JaydenSoric5
Level 2
Level 2
‎16-10-2021 05:03 PM

I play Counter strike global offensive and world of tanks on Hong kong servers as australian servers do not have enough players. I never had an issue with Hong Kong servers, I would usually get between 70-150 however recently I have been getting between 250 to 500 which is unplayable. I have linked the issue which the World of tanks devs have labeled. 

0 Likes
Reply
7 REPLIES 7
BasilDV
Moderator Moderator
Moderator
‎17-10-2021 04:37 PM

Hi @JaydenSoric5

 

Welcome to the Community!

 

We'd like to have a better understanding of the situation.

Please send me a PM with your TPG username or customer ID number along with your Tracert and Ping test result.

 

BasilDV

0 Likes
Reply
JaydenSoric5
Level 2
Level 2
‎17-10-2021 11:19 PM

Hi BasilDV.

 

How can I do a Tracert and ping test and also how would I be able to send you the results?

 

 

0 Likes
Reply
david64
Master
Master
‎18-10-2021 01:03 AM

Hi @JaydenSoric5 . On your computer, open a command window and do these commands.

ping -n 20 92.223.52.65

tracert 92.223.52.65

 

Copy and paste the results into your reply here.

Click on the link PM in the moderator's reply for how to send a private message.

Is the chart produced while you are actively gaming or with the game in an idle state? The response time to the router should be 1 ms with no packet loss. Are you doing this on wifi device or ethernet device?

0 Likes
Reply
JaydenSoric5
Level 2
Level 2
‎18-10-2021 06:07 PM

Ping statistics for 92.223.52.65:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 276ms, Maximum = 278ms, Average = 277ms

 

Tracing route to hk2-sl-a65.fe.core.pw [92.223.52.65]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms ARCHER_VR1600V [192.168.1.1]
2 6 ms 5 ms 5 ms 10.20.26.4
3 6 ms 6 ms 5 ms 203.29.134-193.tpgi.com.au [203.29.134.193]
4 55 ms 54 ms 55 ms syd-tpg-wat-crt2-ge-3-1.static.tpgi.com.au [203.26.22.125]
5 56 ms 54 ms 54 ms syd-gls-har-crt1-he-0-3-0-0.tpgi.com.au [202.7.162.114]
6 57 ms 55 ms 54 ms syd-gls-har-int2-be200.tpgi.com.au [203.221.3.68]
7 277 ms 277 ms 277 ms gcore2-100g.hkix.net [123.255.91.99]
8 * * * Request timed out.
9 * * * Request timed out.
10 277 ms 277 ms 277 ms hk2-sl-a65.fe.core.pw [92.223.52.65]

 

The chart was produced while game was in idle state however it tends to jump between 280-500 ingame. I did it on WIFI device.

 

 

0 Likes
Reply
JaydenSoric5
Level 2
Level 2
‎23-10-2021 07:30 PM

Update, it recently went back down to 100 ping and was staying at 100 till randomly my game timed out and now its back at 300.

0 Likes
Reply
tcdaniels
Level 2
Level 2
‎22-09-2022 02:28 PM

Im having the same issue 

C:\Users\gti99>ping -n 20 92.223.52.65

Pinging 92.223.52.65 with 32 bytes of data:
Reply from 92.223.52.65: bytes=32 time=225ms TTL=48
Reply from 92.223.52.65: bytes=32 time=225ms TTL=48
Reply from 92.223.52.65: bytes=32 time=223ms TTL=48
Reply from 92.223.52.65: bytes=32 time=227ms TTL=48
Reply from 92.223.52.65: bytes=32 time=224ms TTL=48
Reply from 92.223.52.65: bytes=32 time=223ms TTL=48
Reply from 92.223.52.65: bytes=32 time=225ms TTL=48
Reply from 92.223.52.65: bytes=32 time=224ms TTL=48
Reply from 92.223.52.65: bytes=32 time=223ms TTL=48
Reply from 92.223.52.65: bytes=32 time=223ms TTL=48
Reply from 92.223.52.65: bytes=32 time=227ms TTL=48
Reply from 92.223.52.65: bytes=32 time=223ms TTL=48
Reply from 92.223.52.65: bytes=32 time=223ms TTL=48
Reply from 92.223.52.65: bytes=32 time=224ms TTL=48
Reply from 92.223.52.65: bytes=32 time=224ms TTL=48
Reply from 92.223.52.65: bytes=32 time=223ms TTL=48
Reply from 92.223.52.65: bytes=32 time=223ms TTL=48
Reply from 92.223.52.65: bytes=32 time=223ms TTL=48
Reply from 92.223.52.65: bytes=32 time=223ms TTL=48
Reply from 92.223.52.65: bytes=32 time=223ms TTL=48

Ping statistics for 92.223.52.65:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 223ms, Maximum = 227ms, Average = 223ms

C:\Users\gti99>tracert 92.223.52.65

Tracing route to hk2-sl-a65.fe.core.pw [92.223.52.65]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192-168-1-1.tpgi.com.au [192.168.1.1]
2 9 ms 10 ms 8 ms cbr-trn-nor-lns1-lo.tpgi.com.au [10.20.22.41]
3 104 ms 103 ms 101 ms syd-gls-har-crt3-be-200.tpg.com.au [203.221.3.103]
4 101 ms 101 ms 100 ms per-apt-stg-crt1-Hu-0-2-0-2.tpg.com.au [202.7.162.134]
5 102 ms 103 ms 105 ms sin-eqx-aye-int1-Hu-0-0-0-20.tpg.com.au [203.219.107.114]
6 223 ms 223 ms 226 ms gcore2-100g.hkix.net [123.255.91.99]
7 226 ms 223 ms 230 ms 10.255.14.211
8 226 ms 226 ms 225 ms 10.255.14.232
9 224 ms 223 ms 228 ms hk2-sl-a65.fe.core.pw [92.223.52.65]

Trace complete.

 

any help will be gratefully appreciated

0 Likes
Reply
Anonymous
Not applicable
‎22-09-2022 03:16 PM

Hi @tcdaniels,

 

We got you. Let us help fix the latency issue affecting the service. Could shoot us a PM with your details to better understand the situation.

How to send a PM? 

 

--

 

Im having the same issue 

C:\Users\gti99>ping -n 20 92.223.52.65

Pinging 92.223.52.65 with 32 bytes of data:
Reply from 92.223.52.65: bytes=32 time=225ms TTL=48
Reply from 92.223.52.65: bytes=32 time=225ms TTL=48
Reply from 92.223.52.65: bytes=32 time=223ms TTL=48
Reply from 92.223.52.65: bytes=32 time=227ms TTL=48
Reply from 92.223.52.65: bytes=32 time=224ms TTL=48
Reply from 92.223.52.65: bytes=32 time=223ms TTL=48
Reply from 92.223.52.65: bytes=32 time=225ms TTL=48
Reply from 92.223.52.65: bytes=32 time=224ms TTL=48
Reply from 92.223.52.65: bytes=32 time=223ms TTL=48
Reply from 92.223.52.65: bytes=32 time=223ms TTL=48
Reply from 92.223.52.65: bytes=32 time=227ms TTL=48
Reply from 92.223.52.65: bytes=32 time=223ms TTL=48
Reply from 92.223.52.65: bytes=32 time=223ms TTL=48
Reply from 92.223.52.65: bytes=32 time=224ms TTL=48
Reply from 92.223.52.65: bytes=32 time=224ms TTL=48
Reply from 92.223.52.65: bytes=32 time=223ms TTL=48
Reply from 92.223.52.65: bytes=32 time=223ms TTL=48
Reply from 92.223.52.65: bytes=32 time=223ms TTL=48
Reply from 92.223.52.65: bytes=32 time=223ms TTL=48
Reply from 92.223.52.65: bytes=32 time=223ms TTL=48

Ping statistics for 92.223.52.65:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 223ms, Maximum = 227ms, Average = 223ms

C:\Users\gti99>tracert 92.223.52.65

Tracing route to hk2-sl-a65.fe.core.pw [92.223.52.65]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192-168-1-1.tpgi.com.au [192.168.1.1]
2 9 ms 10 ms 8 ms cbr-trn-nor-lns1-lo.tpgi.com.au [10.20.22.41]
3 104 ms 103 ms 101 ms syd-gls-har-crt3-be-200.tpg.com.au [203.221.3.103]
4 101 ms 101 ms 100 ms per-apt-stg-crt1-Hu-0-2-0-2.tpg.com.au [202.7.162.134]
5 102 ms 103 ms 105 ms sin-eqx-aye-int1-Hu-0-0-0-20.tpg.com.au [203.219.107.114]
6 223 ms 223 ms 226 ms gcore2-100g.hkix.net [123.255.91.99]
7 226 ms 223 ms 230 ms 10.255.14.211
8 226 ms 226 ms 225 ms 10.255.14.232
9 224 ms 223 ms 228 ms hk2-sl-a65.fe.core.pw [92.223.52.65]

Trace complete.

 

any help will be gratefully appreciated

0 Likes
Reply