TPG Community

Get online support

Latency and internet speed

drravi1110
Level 2
Since yesterday I have noticed high latency and slow internet speed while using VPN.
My normal latency without VPN is about 10ms and download speed about 270 Mbps, with VPN it was about 150-160ms and dowload 90-100 Mbps, but all of sudden latency has increased to 340-350ms and download speed dropped to 50-60 Mbps.
I have configured a VPN server in Mumbai India. I use that server for gaming and watching Indian movies/shows etc.
I have been using this server for the last 2 years without any issue.
I checked my VPN server using Telstra's network at my friend's house and the latency is152ms and downlod speed 110 Mbps, there is something wrong with your network or you are voluntarily throttling the network.
9 REPLIES 9
david64
Level 11

@drravi1110 .

Normally, your latency and download speed with VPN is about the same as your friend's.

Can you do a ping command and tracert command from your ethernet computer (avoids wifi problems) to the VPN server to see where delays are occurring. Compare with doing it on your friend's computer.

You could post both results here.

drravi1110
Level 2

I don't have ethernet, done over wifi

ravishankartiwari@MacBook-Pro ~ % traceroute 103.13.112.104
traceroute to 103.13.112.104 (103.13.112.104), 64 hops max, 52 byte packets
1 192.168.15.1 (192.168.15.1) 5.888 ms 2.230 ms 1.719 ms
2 192.168.1.1 (192.168.1.1) 2.757 ms 1.931 ms 1.869 ms
3 10.20.20.221 (10.20.20.221) 148.003 ms 10.221 ms 10.556 ms
4 27-32-160-193.static.tpgi.com.au (27.32.160.193) 9.663 ms 137.386 ms 10.287 ms
5 per-apt-stg-crt1-be20.tpgi.com.au (203.219.57.14) 170.697 ms 169.067 ms 184.363 ms
6 sin-eqx-aye-int1-hu-0-0-0-20.tpg.com.au (203.219.107.114) 93.835 ms 94.198 ms 94.234 ms
7 9498.sgw.equinix.com (27.111.228.40) 225.232 ms 293.070 ms 222.727 ms
8 116.119.73.45 (116.119.73.45) 316.536 ms 294.988 ms 295.213 ms
9 nsg-static-118.9.76.182-airtel.com (182.76.9.118) 285.261 ms 346.518 ms 283.716 ms
10 103.149.113.70 (103.149.113.70) 331.232 ms 381.501 ms 307.231 ms

 

ravishankartiwari@MacBook-Pro ~ % ping 103.13.112.104
PING 103.13.112.104 (103.13.112.104): 56 data bytes
64 bytes from 103.13.112.104: icmp_seq=0 ttl=45 time=343.403 ms
64 bytes from 103.13.112.104: icmp_seq=1 ttl=45 time=363.676 ms
64 bytes from 103.13.112.104: icmp_seq=2 ttl=45 time=385.412 ms
64 bytes from 103.13.112.104: icmp_seq=3 ttl=45 time=301.704 ms
64 bytes from 103.13.112.104: icmp_seq=4 ttl=45 time=321.303 ms
64 bytes from 103.13.112.104: icmp_seq=5 ttl=45 time=340.031 ms

 

This is what has changed since yesterday, before that I was getting about 150-160 ms

I routinely  keep checking this, I could not go back to my friend's home and do the check.

drravi1110
Level 2

Checked through ethernet and different ISP

P:\>tracert 103.13.112.104

Tracing route to 103.13.112.104 over a maximum of 30 hops

1 1 ms 1 ms <1 ms 192.168.20.1
2 7 ms 6 ms 6 ms loop121200240.bng.mel.aussiebb.net [121.200.24.1]
3 88 ms 88 ms 88 ms hundredgige0-0-0-20.core1.vdc03.mel.aussiebb.net [202.142.143.112]
4 88 ms 87 ms 87 ms be2.core1.ia-dcb.portmel.aussiebb.net [202.142.143.42]
5 88 ms 88 ms 87 ms hundredgige0-0-0-8.core1.vdc01.per.aussiebb.net [180.150.0.145]
6 88 ms 88 ms 87 ms be1.core2.vdc01.per.aussiebb.net [202.142.143.207]
7 88 ms 87 ms 88 ms be2.core2.nextdc-p1.per.aussiebb.net [202.142.143.205]
8 88 ms 87 ms 88 ms be3.core1.sg1-equinix.sin.aussiebb.net [180.150.2.85]
9 88 ms 88 ms 98 ms 9498.sgw.equinix.com [27.111.228.40]
10 262 ms 257 ms 257 ms 116.119.46.166
11 262 ms 271 ms 262 ms nsg-static-118.9.76.182-airtel.com [182.76.9.118]
12 262 ms 258 ms 259 ms 103.149.113.70
13 * * * Request timed out.
14 258 ms 258 ms 258 ms 103.13.112.104

Trace complete.

P:\>ping 103.13.112.104

Pinging 103.13.112.104 with 32 bytes of data:
Reply from 103.13.112.104: bytes=32 time=258ms TTL=47
Reply from 103.13.112.104: bytes=32 time=258ms TTL=47
Reply from 103.13.112.104: bytes=32 time=258ms TTL=47
Reply from 103.13.112.104: bytes=32 time=258ms TTL=47

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

 

drravi1110
Level 2

Checked on iPhone, Optus 5G

Latency is 192 ms

drravi1110
Level 2

Thanks TPG

Its back to what it was

ravishankartiwari@MacBook-Pro ~ % ping 103.13.112.104

PING 103.13.112.104 (103.13.112.104): 56 data bytes

64 bytes from 103.13.112.104: icmp_seq=0 ttl=51 time=149.458 ms

64 bytes from 103.13.112.104: icmp_seq=1 ttl=51 time=147.451 ms

64 bytes from 103.13.112.104: icmp_seq=2 ttl=51 time=150.479 ms

64 bytes from 103.13.112.104: icmp_seq=3 ttl=51 time=149.038 ms

64 bytes from 103.13.112.104: icmp_seq=4 ttl=51 time=147.846 ms

64 bytes from 103.13.112.104: icmp_seq=5 ttl=51 time=152.957 ms

64 bytes from 103.13.112.104: icmp_seq=6 ttl=51 time=147.279 ms

64 bytes from 103.13.112.104: icmp_seq=7 ttl=51 time=148.123 ms

64 bytes from 103.13.112.104: icmp_seq=8 ttl=51 time=148.259 ms

64 bytes from 103.13.112.104: icmp_seq=9 ttl=51 time=149.791 ms

64 bytes from 103.13.112.104: icmp_seq=10 ttl=51 time=146.694 ms

64 bytes from 103.13.112.104: icmp_seq=11 ttl=51 time=147.820 ms

64 bytes from 103.13.112.104: icmp_seq=12 ttl=51 time=146.543 ms

64 bytes from 103.13.112.104: icmp_seq=13 ttl=51 time=147.672 ms

64 bytes from 103.13.112.104: icmp_seq=14 ttl=51 time=146.391 ms

64 bytes from 103.13.112.104: icmp_seq=15 ttl=51 time=149.739 ms

 

Well done, I appreciate your quick action

drravi1110
Level 2
Today there was service interruption in morning
And the latency has increased again
Can we please have a permanent solution to this issue
Ahra_G
Moderator

Hi @drravi1110

 

Actual throughput speeds may be slower and could vary due to many factors, including but not limited to the type / source of content being accessed, hardware and software configuration, the number of users simultaneously using the network and performance of interconnecting infrastructure not operated by TPG.

 

I've managed to locate your account and recent update indicated that the connection issue is now raised to our Engineering Team for further investigation.

Please ensure to leave your modem connected and turned on for remote testing purposes. 

 

Updates will be provided via phone call or SMS.


Regards,

Ahra_G

drravi1110
Level 2

As mentioned previously, when I check latency with Telstra's network, it is about 140 ms, see below

 

U:\>ping 103.13.112.104

Pinging 103.13.112.104 with 32 bytes of data:
Reply from 103.13.112.104: bytes=32 time=140ms TTL=46
Reply from 103.13.112.104: bytes=32 time=140ms TTL=46
Reply from 103.13.112.104: bytes=32 time=140ms TTL=46
Reply from 103.13.112.104: bytes=32 time=140ms TTL=46

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

U:\>tracert 103.13.112.104

Tracing route to 103.13.112.104 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.16.251
  2     1 ms     1 ms     1 ms  10.168.46.177
  3     1 ms     1 ms     1 ms  10.136.1.1
  4     3 ms     3 ms     3 ms  10.136.1.2
  5     2 ms     1 ms     1 ms  203.37.26.249
  6     2 ms     2 ms     2 ms  bundle-ether17.win-edge903.melbourne.telstra.net
 [110.145.252.1]
  7     2 ms     2 ms     2 ms  bundle-ether2.lon-edge903.melbourne.telstra.net
[203.50.11.197]
  8     3 ms     2 ms     3 ms  bundle-ether13.exi-core10.melbourne.telstra.net
[203.50.11.198]
  9    16 ms    16 ms    16 ms  bundle-ether2.way-core10.adelaide.telstra.net [2
03.50.6.230]
 10    44 ms    43 ms    42 ms  bundle-ether3.pie-core10.perth.telstra.net [203.
50.6.235]
 11    45 ms    42 ms    42 ms  bundle-ether1.pthp-core02.telstraglobal.net.9.50
.203.in-addr.arpa [203.50.9.2]
 12    92 ms    91 ms    90 ms  i-15053.sgpl-core02.telstraglobal.net [202.84.14
0.38]
 13    88 ms    89 ms    90 ms  i-15053.sgpl-core02.telstraglobal.net [202.84.14
0.38]
 14    88 ms    88 ms    88 ms  i-93.istt04.telstraglobal.net [202.84.224.190]
 15    88 ms    88 ms    88 ms  unknown.telstraglobal.net [210.57.30.87]
 16   149 ms   150 ms   149 ms  116.119.46.166
 17   150 ms   150 ms   150 ms  nsg-static-118.9.76.182-airtel.com [182.76.9.118
]
 18   140 ms   143 ms   140 ms  103.149.113.70
 19     *        *        *     Request timed out.
 20   143 ms   141 ms   140 ms  103.13.112.104

Trace complete.

Riezl
Moderator

Hi @drravi1110, we have forwarded your message to our Engineering Team. You will be contacted by the Case Engineer for any additional updates.