TPG Community

Get online support

300 ping to basically all Singapore data centers

bergosaurus
Level 2

No description available.

 

Can we get this fixed? No idea why for the last 6+ months we've been getting +300 ms to singapore and half the routes go through USA.

 

This is effecting ALL isps using your routes. iinet included.

 

For context aussy broadband gets 110-120 ping to every address here.

 

Before you ask no I wont pm you for further information so you can take this issue "offline" & continue to not address it. This isn't account bound and is effecting everyone.

3 REPLIES 3
Aubrey
Moderator

Hi @bergosaurus, we're already investigating this matter and we're keen to get to the bottom of this. We're asking users to send in their details so we can create a ticket under their account and do a monitoring. Results of their ping tests and trace routes would also be helpful.

 

Aubrey

bergosaurus
Level 2

https://community.tpg.com.au/t5/Broadband-Internet/Bad-ping-to-Singapore-in-preparation-for-Albion-O...

 

Above is tracert from January that another user has already done. And heres one to amazons singapore data center.

 

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.26.133
3 101 ms 101 ms 101 ms syd-apt-ros-crt3-be-200.tpgi.com.au [203.29.134.110]
4 101 ms 101 ms 101 ms syd-sot-ken-crs2-Te-0-6-0-10.tpgi.com.au [203.26.22.118]
5 100 ms 99 ms 100 ms nme-sot-dry-agr2-Po40.tpgi.com.au [203.219.107.226]
6 101 ms 100 ms 100 ms per-apt-stg-crt1-be10.tpgi.com.au [203.219.58.177]
7 101 ms 101 ms 101 ms sin-eqx-aye-int1-Hu-0-0-0-20.tpg.com.au [203.219.107.114]
8 101 ms 101 ms 101 ms 16509.sgw.equinix.com [27.111.228.87]
9 * * * Request timed out.
10 217 ms 217 ms 218 ms 52.93.11.21
11 101 ms 100 ms 101 ms 52.93.11.26
12 102 ms 108 ms 110 ms 150.222.3.235
13 101 ms 100 ms 100 ms 15.230.29.116
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 101 ms 100 ms 100 ms ec2-13-228-0-251.ap-southeast-1.compute.amazonaws.com [13.228.0.251]

 

Seems like a pretty standard fix & I don't understand why its taking so long / Why its not actually being addressed outside of requesting tracerts/pings even though its clearly widespread and can be triaged internally.

I guess this thread will go dead like the other 20

 

ISPs on the Optus network don't have this issue

 

 

 

 

Aubrey
Moderator

The user in the above post has been contacted by our engineering team and we note that his issue has been resolved in February. 

 

Our engineers will provide further updates to those with existing tickets. 

 

Aubrey