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

Improving Ping to SEA from Perth

boonhowe
Level 3
Level 3
‎19-06-2019 06:19 PM
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]
0 Likes
Reply
Anonymous
Not applicable
‎19-06-2019 07:32 PM

Hi @boonhowe,

 

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

 

Regards,

0 Likes
Reply
boonhowe
Level 3
Level 3
‎28-07-2019 04:06 AM

still no updates?

0 Likes
Reply
Anonymous
Not applicable
‎30-07-2019 04:13 PM

Hi @boonhowe,

 

Last month this issue has been escalated to our Engineering Team for further handling. Last 24/Jun/19 one of our Engineers contacted you confirmed that the service is working.

 

If you're still having latency issue with the service. Please post the latest Tracert together ping test for reference and we'll re-escalate this to our Engineering Team for another investigation.

 

Cheers!

0 Likes
Reply
boonhowe
Level 3
Level 3
‎30-07-2019 05:48 PM

No change

Using TPG NBN
>ping 52.219.40.46
Pinging 52.219.40.46 with 32 bytes of data:
Reply from 52.219.40.46: bytes=32 time=221ms TTL=47
Reply from 52.219.40.46: bytes=32 time=221ms TTL=47
Reply from 52.219.40.46: bytes=32 time=220ms TTL=47
Reply from 52.219.40.46: bytes=32 time=220ms 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 = 220ms, Maximum = 221ms, Average = 220ms
 
>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     6 ms     5 ms  10-20-25-87.tpgi.com.au [10.20.25.87]
  3     5 ms     5 ms     5 ms  per-apt-stg-crt1-be100.tpgi.com.au [203.219.57.129]
  4    64 ms    63 ms    63 ms  nme-apt-bur-crt1-be60.tpgi.com.au [203.219.57.13]
  5    60 ms    62 ms    62 ms  nme-sot-dry-crt1-be-30.tpgi.com.au [202.7.173.22]
  6    58 ms    63 ms    63 ms  syd-apt-ros-crt1-be-10.tpgi.com.au [202.7.171.141]
  7    60 ms    58 ms    58 ms  203.29.134-68.tpgi.com.au [203.29.134.68]
  8   205 ms   204 ms   204 ms  ix-ae-18-0.tcore1.hk2-hong-kong.as6453.net [180.87.112.221]
  9   230 ms   229 ms   229 ms  if-ae-37-6.tcore2.hk2-hong-kong.as6453.net [116.0.93.136]
 10   230 ms   230 ms   230 ms  if-ae-32-4.tcore2.svw-singapore.as6453.net [116.0.93.169]
 11   220 ms   220 ms   220 ms  180.87.15.206
 12   221 ms   221 ms   221 ms  52.93.9.166
 13   220 ms   220 ms   220 ms  52.93.9.185
 14   221 ms   221 ms   221 ms  203.83.223.27
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21   221 ms   220 ms   220 ms  s3-website-ap-southeast-1.amazonaws.com [52.219.40.46]
Trace complete.
 
Using Mobile Wifi (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=87ms TTL=46
Reply from 52.219.40.46: bytes=32 time=86ms TTL=46
Reply from 52.219.40.46: bytes=32 time=74ms TTL=46
Reply from 52.219.40.46: bytes=32 time=78ms 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 = 74ms, Maximum = 87ms, Average = 81ms
 
>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     3 ms     2 ms     5 ms  192.168.43.1
  2     *        *        *     Request timed out.
  3   199 ms    51 ms    30 ms  10.247.77.181
  4    63 ms    35 ms    31 ms  10.246.243.253
  5    55 ms    21 ms    41 ms  120.16.253.249
  6    45 ms    38 ms    40 ms  220.101.68.53
  7     *        *        *     Request timed out.
  8    60 ms    39 ms    60 ms  59.154.18.126
  9   165 ms    73 ms    79 ms  203.208.175.189
 10    86 ms    86 ms   155 ms  203.208.148.22
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 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   288 ms    78 ms    82 ms  s3-website-ap-southeast-1.amazonaws.com [52.219.40.46]
Trace complete.
0 Likes
Reply
boonhowe
Level 3
Level 3
‎30-07-2019 05:55 PM

Not sure if this Tracert visual mapping tool is accurate, but it looks weird to have the routing all over the place

Tracert TPG.jpgTracert Voda.jpg

0 Likes
Reply
Anonymous
Not applicable
‎30-07-2019 06:26 PM

Hi @boonhowe,

 

Thanks for the additional details. This has been re-escalated to our Engineering Team for another assessment. Expect an update from one of our Engineers within 24-48hrs via SMS or Phone call once it's available.

 

Cheers!

0 Likes
Reply
Anonymous
Not applicable
‎31-07-2019 05:26 PM

Hi @boonhowe,
 

We've seen that you have been in contact with one of our Engineers and provided the findings with the escalated latency issue. At the moment it is currently under monitoring and assessment further updates will be provided when it's available.
 

Let us know should you require further assistance.
 

Cheers!

0 Likes
Reply
palpalpalpal
Level 2
Level 2
‎14-06-2020 05:22 AM

The ping is sometimes 60ms which is totally ok. but now its been 300ms for a month can you let us know why is this. Cause we have experienced some better pings now and then. and normally it would be fixed in couple of days. but now dude, been a month.  fix it please 

0 Likes
Reply
palpalpalpal
Level 2
Level 2
‎14-06-2020 05:23 AM

The ping is sometimes 60ms which is totally ok. but now its been 300ms for a month can you let us know why is this. Cause we have experienced some better pings now and then. and normally it would be fixed in couple of days. but now dude, been a month.  fix it please 

0 Likes
Reply