TPG Community

Ask, answer and talk about our products

Improving Ping to SEA from Perth

Level 3
Considering using 4G adds a bit to the latency, i'm getting much better pings to Singapore servers over 4G mobile wifi.
 
Using TPG NBN (or ADSL, doesn't matter)
>ping 52.219.40.46 (www.changiairport.com.sg, located in AWS SG)
Pinging 52.219.40.46 with 32 bytes of data:
Reply from 52.219.40.46: bytes=32 time=215ms TTL=48
Reply from 52.219.40.46: bytes=32 time=215ms TTL=48
Reply from 52.219.40.46: bytes=32 time=216ms TTL=48
Reply from 52.219.40.46: bytes=32 time=215ms TTL=47
Ping statistics for 52.219.40.46:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 215ms, Maximum = 216ms, Average = 215ms
 
>tracert 52.219.40.46
Tracing route to s3-website-ap-southeast-1.amazonaws.com [52.219.40.46]
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     5 ms     5 ms     5 ms  10-20-25-183.tpgi.com.au [10.20.25.183]
  3     5 ms     5 ms     5 ms  per-pow-stg-crt4-be200.tpgi.com.au [203.29.134.194]
  4    55 ms    55 ms    55 ms  nme-sot-dry-crt2-Be40.tpgi.com.au [203.219.107.229]
  5    55 ms    55 ms    55 ms  syd-apt-ros-crt2-be-10.tpgi.com.au [202.7.171.153]
  6    57 ms    55 ms    55 ms  syd-apt-ros-int2-be100.tpgi.com.au [203.29.134.4]
  7   295 ms   294 ms   294 ms  ix-ae-18-0.tcore1.hk2-hong-kong.as6453.net [180.87.112.221]
  8   317 ms   317 ms   316 ms  if-ae-37-2.tcore2.hk2-hong-kong.as6453.net [116.0.93.144]
  9   317 ms   317 ms   317 ms  if-ae-32-2.tcore2.svw-singapore.as6453.net [180.87.15.80]
 10   215 ms   215 ms   215 ms  180.87.15.206
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13   216 ms   215 ms   216 ms  203.83.223.27
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20   216 ms   215 ms   216 ms  s3-website-ap-southeast-1.amazonaws.com [52.219.40.46]
 
Using mobile wifi (Samsung S7 with Vodafone)
>ping 52.219.40.46
Pinging 52.219.40.46 with 32 bytes of data:
Reply from 52.219.40.46: bytes=32 time=115ms TTL=44
Reply from 52.219.40.46: bytes=32 time=73ms TTL=46
Reply from 52.219.40.46: bytes=32 time=99ms TTL=46
Reply from 52.219.40.46: bytes=32 time=76ms TTL=46
Ping statistics for 52.219.40.46:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 73ms, Maximum = 115ms, Average = 90ms
 
>tracert 52.219.40.46
Tracing route to s3-website-ap-southeast-1.amazonaws.com [52.219.40.46]
over a maximum of 30 hops:
  1     4 ms     3 ms     2 ms  192.168.43.1
  2     *        *        *     Request timed out.
  3    44 ms    28 ms    31 ms  10.247.77.177
  4    57 ms    21 ms    28 ms  10.246.243.254
  5    41 ms    23 ms    27 ms  120.16.253.249
  6    79 ms    29 ms    30 ms  220.101.68.53
  7     *        *        *     Request timed out.
  8    54 ms    21 ms    37 ms  59.154.18.124
  9    78 ms    68 ms    70 ms  203.208.175.189
 10    81 ms    84 ms   116 ms  203.208.148.22
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13    96 ms    79 ms    84 ms  203.83.223.27
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20    71 ms    88 ms    69 ms  s3-website-ap-southeast-1.amazonaws.com [52.219.40.46]
Highlighted
Moderator

Hi @boonhowe,

 

Thanks for the details, PM us your account details (Username/Customer ID together with the address on file).

 

Regards,