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

Kataplexia
Level 2
Level 2
‎18-04-2020 04:48 PM

It is not normal. I am with iinet but I am following the same routing as discussed (same parent company)

My ping is usally stable at ~66ms, but with LoL it is now at ~170ms - all other programs are not experiencing any issues.

 

See below:

 

Tracing route to 104.160.156.1 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 15 ms 14 ms 15 ms 150.101.32.131
3 15 ms 15 ms 15 ms 150.101.35.243
4 15 ms 14 ms 15 ms 150.101.34.171
5 15 ms 15 ms 15 ms 203.8.179.1
6 15 ms 15 ms 15 ms 165.228.23.133
7 15 ms 16 ms 15 ms 203.50.6.187
8 17 ms 16 ms 17 ms 203.50.6.188
9 44 ms 43 ms 43 ms 203.50.6.234
10 57 ms 98 ms 58 ms 203.50.6.231
11 66 ms 66 ms 68 ms 203.50.11.124
12 66 ms 65 ms 66 ms 203.50.11.177
13 159 ms 160 ms 160 ms 203.54.189.30
14 161 ms 160 ms 160 ms 104.160.143.184
15 160 ms 159 ms 160 ms 104.160.143.187
16 159 ms 160 ms 159 ms 104.160.156.1

Trace complete.

 

----

 

Pinging rio3430665.lnk.telstra.net [203.54.189.30] with 32 bytes of data:
Reply from 203.54.189.30: bytes=32 time=160ms TTL=243
Reply from 203.54.189.30: bytes=32 time=160ms TTL=243
Reply from 203.54.189.30: bytes=32 time=160ms TTL=243
Reply from 203.54.189.30: bytes=32 time=160ms TTL=243

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

 

----

0 Likes
Reply
Kataplexia
Level 2
Level 2
‎18-04-2020 04:49 PM

I should mention that I am connecting from Perth WA

0 Likes
Reply
JayeshP9
Moderator Moderator
Moderator
‎18-04-2020 05:02 PM

Hi Kataplexia,

 

See below ping test has done now from TPG provided service at 4:58PM

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=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=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=16ms 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=5ms TTL=53
Reply from 104.160.156.1: bytes=32 time=8ms 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=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=16ms 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=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=12ms TTL=53
Reply from 104.160.156.1: bytes=32 time=21ms 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=7ms TTL=53
Reply from 104.160.156.1: bytes=32 time=8ms 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=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=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 = 57, Received = 57, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 5ms, Maximum = 21ms, Average = 7ms
Control-C
 
See below Tracert performed two times at 5:00 PM
 
Tracing route to pr01.syd01.riotdirect.net [104.160.156.1]
over a maximum of 30 hops:
  1     4 ms     4 ms     5 ms  DESKTOP-UBOT9CL [10.224.10.29]
  2     5 ms     5 ms     4 ms  203-213-0-201.tpgi.com.au [203.213.0.201]
  3     5 ms     6 ms     5 ms  syd-apt-ros-wgw1-be-10.tpgi.com.au [203.29.134.7]
  4     5 ms     6 ms     6 ms  be300.sglebbrdr11.aapt.net.au [203.219.107.198]
  5     7 ms     6 ms     5 ms  Bundle-Ether100.ken-edge903.sydney.telstra.net [139.130.93.21]
  6     6 ms     5 ms     5 ms  bundle-ether2.chw-edge903.sydney.telstra.net [203.50.11.175]
  7     6 ms     6 ms     7 ms  rio3430665.lnk.telstra.net [203.54.189.30]
  8     7 ms     6 ms     6 ms  ae3.br02.syd01.riotdirect.net [104.160.143.189]
  9     7 ms     6 ms     6 ms  ae-1.br01.syd01.riotdirect.net [104.160.156.8]
 10     6 ms     6 ms     6 ms  pr01.syd01.riotdirect.net [104.160.156.1]
Trace complete.
 
 
Tracing route to pr01.syd01.riotdirect.net [104.160.156.1]
over a maximum of 30 hops:
  1     5 ms     4 ms     4 ms  DESKTOP-UBOT9CL [10.224.10.29]
  2    33 ms    37 ms    26 ms  203-213-0-201.tpgi.com.au [203.213.0.201]
  3     5 ms     5 ms     5 ms  syd-apt-ros-wgw1-be-10.tpgi.com.au [203.29.134.7]
  4     6 ms     5 ms     5 ms  be300.sglebbrdr11.aapt.net.au [203.219.107.198]
  5     6 ms     6 ms     6 ms  Bundle-Ether100.ken-edge903.sydney.telstra.net [139.130.93.21]
  6     5 ms     5 ms     4 ms  bundle-ether2.chw-edge903.sydney.telstra.net [203.50.11.175]
  7     7 ms     6 ms     5 ms  rio3430665.lnk.telstra.net [203.54.189.30]
  8     6 ms     5 ms     6 ms  ae3.br02.syd01.riotdirect.net [104.160.143.189]
  9     6 ms     7 ms     6 ms  ae-1.br01.syd01.riotdirect.net [104.160.156.8]
 10     7 ms     7 ms     6 ms  pr01.syd01.riotdirect.net [104.160.156.1]
Trace complete.
 
regards
JayeshP9.
0 Likes
Reply
Kataplexia
Level 2
Level 2
‎18-04-2020 05:49 PM

OK. I have worked in IT and understand that the easiest thing to do is to put the problem back onto the end-user, but how can my issue have been created with no change to my own configuration? This issue is not affecting everyone, some people have decent ping - others do not. If you search around - there are also threads on whirlpool regarding this same issue; Some people can ping 104.160.156.1 and get a reasonable response - all others get stuck at 203.54.189.30. The issue cannot be with the game server, it is a routing issue. My connection is stable with all other applications.

0 Likes
Reply
shamsmehra90
Level 2
Level 2
‎08-05-2020 10:24 PM

Hi,

My ping has gone up like 60ms on everything. For example, when I play League of Legends, I normally get 40ms. Now I get almost 100ms and it's really annoying. I have done a Speedtest on my phone and the ping on my phone is perfectly fine so I figured it's something to do with my computer,

Can anyone help?

 

Regards, mcdvoicesurvey.onl

mybk-experience.onl

0 Likes
Reply