High latency to a particular ip

[tingjunwu94]

Hi I am experiencing high latency when connecting to a particular server, and below is my traceroute log

Tracing route to 66.203.112.17 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms xxx
2 12 ms 12 ms 12 ms xxx
3 12 ms 12 ms 12 ms xxx
4 13 ms 12 ms 12 ms xxx
5 13 ms 13 ms 13 ms xxx
6 * * * Request timed out.
7 15 ms 15 ms 15 ms 59.154.57.72
8 14 ms 15 ms 15 ms 61.88.33.9
9 14 ms 14 ms 14 ms 124.19.71.2
10 14 ms 13 ms 14 ms 31.217.251.93
11 14 ms 14 ms 14 ms 396356.cust.gslnetworks.com [31.217.251.223]
12 * * * Request timed out.
13 165 ms 165 ms 165 ms 66.203.112.17

Trace complete.

I can see in the last hop, the latency jumped to 165ms, can tpg fix this from their side?

[Shane]

Hi @tingjunwu94 ,

What is the location of this server? Could you also perform a tracert on a different server (google) to compare the results and post them on this thread?

Regards,

[david64]

Hi @tingjunwu94 . Can you check this again. It looks to be fixed today.

Do  ping 66.203.112.17

Response time should be good. Problem was over in Los Angeles.

Question to ask TPG is why your game traffic is being routed from Sydney to Los Angeles when the game server is in Sydney?

59.154.57.72       SingTel Optus Sydney
61.88.33.9           " 

124.19.71.2         "
31.217.251.93     GSL Networks Los Angeles
31.217.251.223   "
66.203.112.17     Latitude Sydney

In your tracert display, there is no security risk in leaving addresses in line 3 onwards displayed. They are all public ip addresses of TPG and other carriers.

[tingjunwu94]

I think I am still seeing the issue

Tracing route to 66.203.112.17 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms
2 12 ms 12 ms 12 ms
3 13 ms 12 ms 12 ms syd-gls-har-wgw1-be-100.tpgi.com.au [203.221.3.7]
4 12 ms 12 ms 13 ms 203-219-107-194.static.tpgi.com.au [203.219.107.194]
5 13 ms 14 ms 13 ms bundle-ether140.22btpr01.optus.net.au [61.88.32.18]
6 * * * Request timed out.
7 16 ms 15 ms 15 ms 59.154.57.72
8 16 ms 14 ms 17 ms 61.88.33.9
9 14 ms 13 ms 13 ms 124.19.71.2
10 14 ms 13 ms 13 ms 31.217.251.93
11 14 ms 13 ms 14 ms 396356.cust.gslnetworks.com [31.217.251.223]
12 * * * Request timed out.
13 165 ms 165 ms 165 ms 66.203.112.17

the ping response is

Pinging 66.203.112.17 with 32 bytes of data:
Reply from 66.203.112.17: bytes=32 time=165ms TTL=48
Reply from 66.203.112.17: bytes=32 time=165ms TTL=48
Reply from 66.203.112.17: bytes=32 time=165ms TTL=48
Reply from 66.203.112.17: bytes=32 time=166ms TTL=48

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

[tingjunwu94]

Hi, the ip is in NSW and it is an Australian server

tracert to 8.8.8.8 is fine

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms
2 12 ms 11 ms 12 ms
3 13 ms 12 ms 12 ms 203-221-3-17.tpgi.com.au [203.221.3.17]
4 12 ms 12 ms 12 ms 72.14.197.162
5 14 ms 14 ms 14 ms 72.14.235.125
6 14 ms 13 ms 13 ms 209.85.247.127
7 12 ms 12 ms 12 ms dns.google [8.8.8.8]

I am only getting latency for the ip I specified in the post.

[david64]

@tingjunwu94 . That's strange. I did this at 10:01.

Question remains @Shane , why is this being routed to Los Angeles?

(See my post from 11:30 today.)

tracert 66.203.112.17

Tracing route to 66.203.112.17 over a maximum of 30 hops

1 <1 ms 3 ms <1 ms ARCHER_VR1600V [192.168.1.1]
2 5 ms 4 ms 4 ms 

3 5 ms 4 ms 5 ms syd-gls-har-wgw1-be200.tpgi.com.au [203.221.3.71]
4 5 ms 5 ms 6 ms 203-219-107-194.static.tpgi.com.au [203.219.107.194]
5 6 ms 5 ms 5 ms bundle-ether140.22btpr01.optus.net.au [61.88.32.18]
6 * * * Request timed out.
7 8 ms 9 ms 9 ms 59.154.57.76
8 9 ms 9 ms 8 ms 61.88.33.9
9 6 ms 8 ms 6 ms 124.19.71.2
10 7 ms 5 ms 6 ms 31.217.251.93
11 6 ms 7 ms 7 ms 396356.cust.gslnetworks.com [31.217.251.223]
12 * * * Request timed out.
13 7 ms 7 ms 6 ms 66.203.112.17

Trace complete.

ping -n 1 66.203.112.17

Pinging 66.203.112.17 with 32 bytes of data:
Reply from 66.203.112.17: bytes=32 time=6ms TTL=51

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

[Shane]

Let us help understand what causing this unusual route, could you shoot me a PM with your details? @tingjunwu94 

Regards,