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 Ping

JayeshP9
Moderator Moderator
Moderator
‎17-04-2020 04:19 PM

Hi, There could be issue with game server but from our end we haven't seen any network issue.  Even you can also try another third party speed test like speedtest.net  as well to check ping.

regards

JayeshP9.

0 Likes
Reply
highping123
Level 3
Level 3
‎17-04-2020 04:21 PM

It is not the game server, I have tested connecting to the game using mobile data and also friends with different ISP's. 

speedtest.net gives 14ping 93down 35up

0 Likes
Reply
highping123
Level 3
Level 3
‎17-04-2020 04:22 PM

There are many many people who otherwise have strong connections who are having ping issues with TPG and League of Legends

0 Likes
Reply
david64
Master
Master
‎17-04-2020 05:36 PM

The LOL server for OCE (Oceania) is 104.160.156.1.

Can you and a friend who is not with TPG try this:

tracert -d 104.160.156.1

Compare the number of steps.

You can get an idea of what networks you each go through by doing    ping -a      on each ip address.

0 Likes
Reply
Jordan26
Level 3
Level 3
‎17-04-2020 05:49 PM

Having the exact same issue - started just today. Perfectly fine ping everywhere except when playing League of Legends. Ping in game sits between 150-190. Ping everywhere else is between 15-30. 

Reply
LolplayerOCE
Level 2
Level 2
‎17-04-2020 06:22 PM

Hey, I am also having around 150 ping while in game on League of Legends while my friends not on TPG are not experiencing issues. I have attatched screenshots of my cmd results after putting in the tracert command and also a friend's results who is not with TPG.

0 Likes
Reply
highping123
Level 3
Level 3
‎17-04-2020 06:22 PM

Telstra Connection: 

1 5 ms 1 ms 1 ms 10.1.1.1
2 10 ms 10 ms 9 ms 203.219.198.42
3 10 ms 10 ms 10 ms 27.32.160.195
4 11 ms 11 ms 11 ms 203.219.107.206
5 11 ms 11 ms 12 ms 165.228.52.1
6 13 ms 15 ms 12 ms 203.50.11.107
7 23 ms 23 ms 22 ms 203.50.11.122
8 22 ms 20 ms 22 ms 203.50.11.173
9 25 ms 21 ms 21 ms 203.50.11.175
10 157 ms 157 ms 156 ms 203.54.189.30
11 158 ms 156 ms 158 ms 104.160.143.189
12 172 ms 156 ms 157 ms 104.160.156.8
13 157 ms 195 ms 157 ms 104.160.156.1

 

TPG Connection: 

1 1 ms 1 ms 1 ms 203.209.198.37
2 1 ms 1 ms 1 ms 203.209.199.222
3 1 ms 1 ms 1 ms 14.201.178.69
4 2 ms 1 ms 2 ms 203.220.216.21
5 2 ms 1 ms 2 ms 203.219.155.72
6 2 ms 2 ms 2 ms 203.219.107.202
7 2 ms 2 ms 2 ms 139.130.41.105
8 4 ms 3 ms 3 ms 203.50.11.109
9 14 ms 14 ms 12 ms 203.50.11.124
10 12 ms 12 ms 12 ms 203.50.11.177
11 147 ms 147 ms 147 ms 203.54.189.30
12 147 ms 148 ms 147 ms 104.160.143.184
13 147 ms 147 ms 147 ms 104.160.143.187
14 147 ms 147 ms 147 ms 104.160.156.1

 

My 4G Connection:

1 1 ms <1 ms <1 ms 172.20.10.1
2 * * * Request timed out.
3 21 ms 18 ms 23 ms 10.194.137.109
4 28 ms 35 ms 19 ms 10.194.124.226
5 30 ms 26 ms 31 ms 10.194.124.213
6 * * * Request timed out.
7 45 ms 30 ms 27 ms 124.19.61.215
8 44 ms 27 ms 27 ms 203.54.153.13
9 35 ms 27 ms 23 ms 203.50.11.197
10 39 ms 35 ms 39 ms 203.50.11.198
11 51 ms 38 ms 38 ms 203.50.11.124
12 55 ms 34 ms 34 ms 203.50.11.177
13 56 ms 34 ms 35 ms 203.54.189.30
14 42 ms 35 ms 39 ms 104.160.143.184
15 40 ms 76 ms 33 ms 104.160.143.187
16 42 ms 35 ms 34 ms 104.160.156.1

Reply
david64
Master
Master
‎17-04-2020 08:05 PM

The delay occurs in Telstra's network, the leg heading to 203.54.189.30. The optusnet user "friend low ping" enters Telstra's network at a point which bypasses the slow leg even though it ends up on the same device; so has a different physical connection. The Telstra and TPG connection above encounter a large delay at the same point, however the 4G connection doesn't.

As a comparison, I'm in Sydney on ADSL2+ and get 13ms to 203.50.11.175 and 140ms to 203.54.189.30.

We can see if this improves at different times of the day.

A TPG engineer might be able to explain why it happens, but I don't know who can fix it.

 

This user has a similar problem:

 https://community.tpg.com.au/t5/Broadband-Internet/TPG-FTTB-evening-latency/m-p/58053

 

0 Likes
Reply
david64
Master
Master
‎17-04-2020 11:39 PM

11:27 pm

tracert -d 104.160.156.1

         ............

13   14 ms   13 ms   13 ms   104.160.156.1

 

still going via the previously slow  203.54.189.30.

0 Likes
Reply
JayeshP9
Moderator Moderator
Moderator
‎18-04-2020 09:23 AM

Hi highping 123,

I have done ping and tracert for 104.160.156.1 over TPG service and noted its normal

============================================================

See below result for your refence.

Tracert as below:

Tracing route to pr01.syd01.riotdirect.net [104.160.156.1]
over a maximum of 30 hops:
  1     5 ms     4 ms     3 ms  DESKTOP-UBOT9CL [10.224.10.31]
  2     5 ms     4 ms     3 ms  203-213-0-201.tpgi.com.au [203.213.0.201]
  3     5 ms     4 ms     4 ms  syd-apt-ros-wgw1-be-10.tpgi.com.au [203.29.134.7]
  4     5 ms     5 ms     5 ms  be300.sglebbrdr11.aapt.net.au [203.219.107.198]
  5     6 ms     6 ms     5 ms  Bundle-Ether100.ken-edge903.sydney.telstra.net [139.130.93.21]
  6     6 ms     8 ms     6 ms  bundle-ether2.chw-edge903.sydney.telstra.net [203.50.11.175]
  7     8 ms     6 ms     5 ms  rio3430665.lnk.telstra.net [203.54.189.30]
  8     6 ms     6 ms     7 ms  ae3.br02.syd01.riotdirect.net [104.160.143.189]
  9     8 ms     6 ms     6 ms  ae-1.br01.syd01.riotdirect.net [104.160.156.8]
 10     7 ms     6 ms     6 ms  pr01.syd01.riotdirect.net [104.160.156.1]
Trace complete.

========================================================

Ping test as below:

Pinging 104.160.156.1 with 32 bytes of data:
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=7ms TTL=53
Reply from 104.160.156.1: bytes=32 time=7ms TTL=53
Reply from 104.160.156.1: bytes=32 time=7ms TTL=53
Reply from 104.160.156.1: bytes=32 time=10ms TTL=53
Reply from 104.160.156.1: bytes=32 time=7ms TTL=53
Reply from 104.160.156.1: bytes=32 time=5ms TTL=53
Reply from 104.160.156.1: bytes=32 time=5ms TTL=53
Reply from 104.160.156.1: bytes=32 time=7ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=7ms TTL=53
Reply from 104.160.156.1: bytes=32 time=7ms TTL=53
Reply from 104.160.156.1: bytes=32 time=113ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=7ms TTL=53
Reply from 104.160.156.1: bytes=32 time=7ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=7ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=7ms TTL=53
Reply from 104.160.156.1: bytes=32 time=5ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=7ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=7ms TTL=53
Reply from 104.160.156.1: bytes=32 time=5ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=5ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=7ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=49ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=10ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=7ms TTL=53
Reply from 104.160.156.1: bytes=32 time=7ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=7ms TTL=53
Reply from 104.160.156.1: bytes=32 time=7ms TTL=53
Reply from 104.160.156.1: bytes=32 time=58ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=7ms TTL=53
Reply from 104.160.156.1: bytes=32 time=7ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=7ms TTL=53
Reply from 104.160.156.1: bytes=32 time=8ms TTL=53
Reply from 104.160.156.1: bytes=32 time=5ms TTL=53
Reply from 104.160.156.1: bytes=32 time=54ms TTL=53
Reply from 104.160.156.1: bytes=32 time=7ms TTL=53
Reply from 104.160.156.1: bytes=32 time=7ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=7ms TTL=53
Reply from 104.160.156.1: bytes=32 time=7ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=7ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Reply from 104.160.156.1: bytes=32 time=7ms TTL=53
Reply from 104.160.156.1: bytes=32 time=6ms TTL=53
Ping statistics for 104.160.156.1:
    Packets: Sent = 77, Received = 77, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 5ms, Maximum = 113ms, Average = 9ms
Control-C
 

regards
JayeshP9.

 

0 Likes
Reply