High ping MW2

[Kurt16]

Hi, for the last 2-3 weeks my ping has gone from 70ms to 120-140ms consistently.im wondering if something has changed or there is a test i can do.

I did some ping tests as per the ping help tab. Results below

C:\Users\Kurtb>ping tpg.com.au

Pinging tpg.com.au [203.26.27.38] with 32 bytes of data:
Reply from 203.26.27.38: bytes=32 time=58ms TTL=61
Reply from 203.26.27.38: bytes=32 time=58ms TTL=61
Reply from 203.26.27.38: bytes=32 time=57ms TTL=61
Reply from 203.26.27.38: bytes=32 time=65ms TTL=61

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

C:\Users\Kurtb>ping 203.12.160.35

Pinging 203.12.160.35 with 32 bytes of data:
Reply from 203.12.160.35: bytes=32 time=9ms TTL=228
Reply from 203.12.160.35: bytes=32 time=15ms TTL=228
Reply from 203.12.160.35: bytes=32 time=9ms TTL=228
Reply from 203.12.160.35: bytes=32 time=15ms TTL=228

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

C:\Users\Kurtb>ping 127.0.0.1

Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

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

[BasilDV]

Hi @Kurt16 

We'd like to check on this further and see what we can do to improve it.

Kindly send us a private message with your account details.

BasilDV

[david64]

Hi @Kurt16 . When doing this testing, you should use an ethernet computer. Wifi connection can cause slower or varying response times, either due to the nature of wifi or interference from other networks.

The address 127.0.0.1 is an internal address in the computer operating system and will always be fast.

You can ping your router's LAN ip address (usually 192.168.1.1). Should be about 1 ms response time. 

My response time to 203.12.160.35 (TPG's DNS) is 5 ms.

My response time to tpg.com.au is 5 ms. You should do   tracert tpg.com.au   command to see where delays are occurring.

Regarding your game MW2, you need to know the host name or ip address of the game server to see if delays are occurring somewhere else in the network.

[Kurt16]

Hey @david64 ,

i am cuurrently connected via a hardwired ethernet cable, so shouldnt have any dramas there.

internlly i get >1ms to the router so that seems good.

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Ping to TPG is as below:

Pinging 203.12.160.35 with 32 bytes of data:
Reply from 203.12.160.35: bytes=32 time=9ms TTL=228
Reply from 203.12.160.35: bytes=32 time=24ms TTL=228
Reply from 203.12.160.35: bytes=32 time=9ms TTL=228
Reply from 203.12.160.35: bytes=32 time=9ms TTL=228

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

as for Tracert results below:

Tracing route to tpg.com.au [203.26.27.38]
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 9 ms 9 ms 10.20.26.161
3 57 ms 57 ms 60 ms 203-219-57-130.tpgi.com.au [203.219.57.130]
4 58 ms 58 ms 58 ms nme-apt-bur-dom1-po70.tpgi.com.au [202.7.162.205]
5 61 ms 63 ms 63 ms syd-sot-ken-crt2-he-0-3-0-0.tpgi.com.au [202.7.162.78]
6 66 ms 62 ms 58 ms syd-sot-ken-wrt3-te0-3-0.tpgi.com.au [202.7.214.254]
7 57 ms 57 ms 57 ms www.tpg.com.au [203.26.27.38]

Trace complete.