CrowdSupport®
Level 1: Cadet

Bad routing to Hong Kong (High ping / latency)

Hello, 

 

I'm receiveing extremely high ping / latency when connecting to Hong Kong servers. I used to be getting 130 ping with telstra to the specified IP, but all of a sudden my ping has spiked up to 300. 

 

My routing is going Syd > Hong kong > Syd > USA > Hong Kong. This is the reason i'm getting such high ping. I had a friend ping the same IP ( 43.239.136.109 ) And he was getting 130ms (He's in Syd, AUS and is with Telstra)

 

I'm currently on NBN getting 42 down and 19 up so that's not an issue.See screenshot for speedtest results( https://prnt.sc/q50pog

 

I use DHCP, and with different telstra IP's i get different pings to the same server. To get a new IP i turn my router off and on, and the best ping i have gotten since the spike has been 300. I've had a high of 400 ping with one IP, but most of the time i'm getting 340. When doing a tracert the to server i play on, i'm getting 18 hops. 

 

Tracing route to hosted-by.i3d.net [43.239.136.109]
over a maximum of 30 hops:

1 1 ms 2 ms 1 ms mygateway.gateway [10.0.0.138]
2 12 ms 10 ms 13 ms 58.162.26.79
3 9 ms 8 ms 10 ms ae10.stl-ice302.sydney.telstra.net [203.50.61.97]
4 10 ms 11 ms 11 ms bundle-ether26.chw-core10.sydney.telstra.net [203.50.61.96]
5 12 ms 13 ms 11 ms bundle-ether1.oxf-gw11.sydney.telstra.net [203.50.6.93]
6 11 ms 12 ms 11 ms bundle-ether1.sydo-core03.sydney.reach.com [203.50.13.98]
7 11 ms 11 ms 9 ms i-10403.sydo-core04.telstraglobal.net [202.84.222.130]
8 185 ms 185 ms 189 ms i-10604.1wlt-core02.telstraglobal.net [202.84.141.225]
9 194 ms 194 ms 194 ms i-0-6-0-1.paix-core02.telstraglobal.net [202.84.143.198]
10 198 ms 196 ms 196 ms i-92.paix02.telstraglobal.net [202.84.247.41]
11 194 ms 194 ms 193 ms liberty_global-peer.eqnx03.pr.telstraglobal.net [134.159.63.85]
12 194 ms 194 ms 194 ms be2015.ccr21.sfo01.atlas.cogentco.com [154.54.7.173]
13 209 ms 209 ms 209 ms be3693.ccr21.pdx01.atlas.cogentco.com [154.54.81.66]
14 346 ms 347 ms 347 ms be3701.ccr21.hkg02.atlas.cogentco.com [154.54.87.122]
15 343 ms 344 ms 345 ms be3453.rcr51.hkg01.atlas.cogentco.com [154.54.0.17]
16 348 ms 348 ms 347 ms be2044.nr12.b065790-1.hkg01.atlas.cogentco.com [154.24.37.46]
17 221 ms 223 ms 222 ms 154.18.7.82
18 300 ms 300 ms 300 ms hosted-by.i3d.net [43.239.136.109]

 

Using the Telstra looking glass i pinged the same IP and here are the results i got

 

Result from https://lg.telstraglobal.com/

 

1 i-91.sydp-core04.telstraglobal.net (202.84.222.85) 1 msec 0 msec 2 msec 2 i-20802.eqnx-core02.telstraglobal.net (202.84.141.25) 137 msec 136 msec 140 msec 3 i-0-0-0-1.paix-core02.telstraglobal.net (202.84.143.210) 179 msec 178 msec 178 msec 4 i-92.paix02.telstraglobal.net (202.84.247.41) 181 msec 181 msec 203 msec 5 134.159.63.85 177 msec 177 msec 177 msec 6 be2015.ccr21.sfo01.atlas.cogentco.com (154.54.7.173) 178 msec be2016.ccr22.sfo01.atlas.cogentco.com (154.54.0.177) 178 msec be2015.ccr21.sfo01.atlas.cogentco.com (154.54.7.173) 178 msec 7 be3694.ccr21.pdx01.atlas.cogentco.com (154.54.84.30) 193 msec be3693.ccr21.pdx01.atlas.cogentco.com (154.54.81.66) 196 msec be3694.ccr21.pdx01.atlas.cogentco.com (154.54.84.30) 193 msec 8 be3701.ccr21.hkg02.atlas.cogentco.com (154.54.87.122) 329 msec 329 msec 330 msec 9 be3453.rcr51.hkg01.atlas.cogentco.com (154.54.0.17) 331 msec 330 msec 331 msec 10 be2044.nr12.b065790-1.hkg01.atlas.cogentco.com (154.24.37.46) 331 msec 331 msec 331 msec 11 154.18.7.82 201 msec 201 msec 201 msec 12 hosted-by.i3d.net (43.239.136.109) 202 msec 201 msec 201 msec

 

Result from https://www.telstra.net/cgi-bin/trace

 

1 i-91.sydp-core04.telstraglobal.net (202.84.222.85) 1 msec 0 msec 2 msec
2 i-20802.eqnx-core02.telstraglobal.net (202.84.141.25) 137 msec 136 msec 140 msec
3 i-0-0-0-1.paix-core02.telstraglobal.net (202.84.143.210) 179 msec 178 msec 178 msec
4 i-92.paix02.telstraglobal.net (202.84.247.41) 181 msec 181 msec 203 msec
5 134.159.63.85 177 msec 177 msec 177 msec
6 be2015.ccr21.sfo01.atlas.cogentco.com (154.54.7.173) 178 msec
be2016.ccr22.sfo01.atlas.cogentco.com (154.54.0.177) 178 msec
be2015.ccr21.sfo01.atlas.cogentco.com (154.54.7.173) 178 msec
7 be3694.ccr21.pdx01.atlas.cogentco.com (154.54.84.30) 193 msec
be3693.ccr21.pdx01.atlas.cogentco.com (154.54.81.66) 196 msec
be3694.ccr21.pdx01.atlas.cogentco.com (154.54.84.30) 193 msec
8 be3701.ccr21.hkg02.atlas.cogentco.com (154.54.87.122) 329 msec 329 msec 330 msec
9 be3453.rcr51.hkg01.atlas.cogentco.com (154.54.0.17) 331 msec 330 msec 331 msec
10 be2044.nr12.b065790-1.hkg01.atlas.cogentco.com (154.24.37.46) 331 msec 331 msec 331 msec
11 154.18.7.82 201 msec 201 msec 201 msec
12 hosted-by.i3d.net (43.239.136.109) 202 msec 201 msec 201 msec

 

I then used the Optus looking glass ( http://looking-glass.optus.net.au/lg/ ) 

 

Tracing the route to 43.239.136.109
VRF info: (vrf in name/id, vrf out name/id)
1 124.19.62.49 0 msec 0 msec 1 msec
2 * * *
3 * * *
4 59.154.18.6 2 msec 2 msec
59.154.18.10 2 msec
5 203.208.177.189 117 msec 117 msec 116 msec
6 203.208.158.193 116 msec
203.208.178.17 117 msec
203.208.178.13 117 msec
7 116.0.67.169 117 msec 117 msec 117 msec
8 116.0.67.87 119 msec 119 msec 119 msec
9 180.87.160.177 117 msec 118 msec 164 msec
10 43.239.136.109 118 msec 118 msec 118 msec

 

Optus is getting 117 ping, but telstra is getting 201. I'm considering switching to Optus if there is no solution for this. The telstra result makes no sense really, because i used to get 130 ping to the HK server, and my friend is getting 130 to the same server currently and he's with telstra?

 

When looking at a submarine cable map ( https://live.infrapedia.com/?neLng=215.21429259413367&neLat=19.862583283997793&swLng=62.887293108444... )

 

You can see that the Indigo-Central line (Syd to perth) Is not owned by telstra. It is however owned by optus. This is how i beleive optus is getting such low ping to HK.

 

Can someone please tell me how i can fix my routing Syd > Hong kong > Syd > USA > Hong Kong? Would a public DNS help? Would changing to a Static IP help? 

 

Any help would be much appreciated. I'll be checking for answers and replying reguarly. Cheers.

Was this helpful?

  • Yes it was, thank you
  • No, I still need help
5 REPLIES 5
Highlighted
Level 23: Superhero
Level 23: Superhero

Re: Bad routing to Hong Kong (High ping / latency)

From memory there was/is a damaged fiber cable between Singapore and Hong Kong that could be the cause of your increased latency. However in general there is no guaranteed latency for consumer services.
For Official Support Chat Now, try the Online Troubleshooter, check for Outages or Raise a Complaint.

Full Disclosure as part of Telstras Social Media Code.
  • I work for Telstra in the following products.
  • Telstra Platinum, Telstra Business Services, Telstra Smart Home, Velocity, Locator and NBN faults.
  • I'm not here in an official capacity, I just like fixing things and respond in my own time when I can.
  • Include "@343GuiltySpark" in your reply to get my attention if you're after me specifically.
  • My opinions are my own and not that of Telstra's, just so we're all on the same page.
Highlighted
Level 1: Cadet

Re: Bad routing to Hong Kong (High ping / latency)


@343GuiltySpark wrote:
From memory there was/is a damaged fiber cable between Singapore and Hong Kong that could be the cause of your increased latency. However in general there is no guaranteed latency for consumer services.

Even if there was a damaged fibre cable, it doesn't explain how my routing is going Syd > Hong kong > Syd > USA > Hong Kong. 

Highlighted
Level 1: Cadet

Re: Bad routing to Hong Kong (High ping / latency)

Updated tracert: 

 

Tracing route to hosted-by.i3d.net [43.239.136.109]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms mygateway.gateway [10.0.0.138]
2 12 ms 10 ms 12 ms 58.162.26.79
3 9 ms 10 ms 10 ms ae10.stl-ice302.sydney.telstra.net [203.50.61.97]
4 10 ms 10 ms 11 ms bundle-ether26.chw-core10.sydney.telstra.net [203.50.61.96]
5 11 ms 10 ms 11 ms bundle-ether1.oxf-gw11.sydney.telstra.net [203.50.6.93]
6 10 ms 10 ms 12 ms bundle-ether1.sydo-core03.sydney.reach.com [203.50.13.98]
7 14 ms 11 ms 10 ms i-10403.sydo-core04.telstraglobal.net [202.84.222.130]
8 184 ms 181 ms 184 ms i-10604.1wlt-core02.telstraglobal.net [202.84.141.225]
9 195 ms 195 ms 194 ms i-0-6-0-1.paix-core02.telstraglobal.net [202.84.143.198]
10 224 ms 195 ms 194 ms i-92.paix02.telstraglobal.net [202.84.247.41]
11 193 ms 194 ms 194 ms liberty_global-peer.eqnx03.pr.telstraglobal.net [134.159.63.85]
12 194 ms 194 ms 194 ms be2016.ccr22.sfo01.atlas.cogentco.com [154.54.0.177]
13 228 ms 209 ms 209 ms be3694.ccr21.pdx01.atlas.cogentco.com [154.54.84.30]
14 343 ms 341 ms 342 ms be3701.ccr21.hkg02.atlas.cogentco.com [154.54.87.122]
15 343 ms 344 ms 343 ms be3453.rcr51.hkg01.atlas.cogentco.com [154.54.0.17]
16 345 ms 345 ms 345 ms be2044.nr12.b065790-1.hkg01.atlas.cogentco.com [154.24.37.46]
17 225 ms 278 ms 224 ms 154.18.7.82
18 400 ms 396 ms 401 ms hosted-by.i3d.net [43.239.136.109]

Trace complete.

 

Still going Syd > Hong kong > Syd > USA > Hong Kong. I've tried resetting my modem multiple times, using multiple different modems and nothing has worked. Anyone know what i can do? I've heard support can't do anything about it so im not going to waste my time there. 

Highlighted
Level 24: Supreme Being
Level 24: Supreme Being

Re: Bad routing to Hong Kong (High ping / latency)

Connection isn't going Sydney > Hong Kong > Sydney

 

6 10 ms 10 ms 12 ms bundle-ether1.sydo-core03.sydney.reach.com [203.50.13.98] SYDNEY


7 14 ms 11 ms 10 ms i-10403.sydo-core04.telstraglobal.net [202.84.222.130] SYDNEY


8 184 ms 181 ms 184 ms i-10604.1wlt-core02.telstraglobal.net [202.84.141.225] LA - USA


9 195 ms 195 ms 194 ms i-0-6-0-1.paix-core02.telstraglobal.net [202.84.143.198] PALO ALTO - USA


10 224 ms 195 ms 194 ms i-92.paix02.telstraglobal.net [202.84.247.41] PALO ALTO - USA


11 193 ms 194 ms 194 ms liberty_global-peer.eqnx03.pr.telstraglobal.net [134.159.63.85] SAN JOSE - USA


12 194 ms 194 ms 194 ms be2016.ccr22.sfo01.atlas.cogentco.com [154.54.0.177] SAN FRANCISO - USA
13 228 ms 209 ms 209 ms be3694.ccr21.pdx01.atlas.cogentco.com [154.54.84.30] PORTLAND -USA

I am Complex Customer Service Specialist, nominally working with most assurance products. However, I am not an official representative on CrowdSupport.

IT Helpdesk and Technicial Support by Telstra Platinum
Smart Home Automation & Monitoring from Telstra
Helping Australians Find the Things that Matter Most with Telstra Locator
Highlighted
Level 1: Cadet

Re: Bad routing to Hong Kong (High ping / latency)


@Yastiandrie wrote:

Connection isn't going Sydney > Hong Kong > Sydney

 

6 10 ms 10 ms 12 ms bundle-ether1.sydo-core03.sydney.reach.com [203.50.13.98] SYDNEY


7 14 ms 11 ms 10 ms i-10403.sydo-core04.telstraglobal.net [202.84.222.130] SYDNEY


8 184 ms 181 ms 184 ms i-10604.1wlt-core02.telstraglobal.net [202.84.141.225] LA - USA


9 195 ms 195 ms 194 ms i-0-6-0-1.paix-core02.telstraglobal.net [202.84.143.198] PALO ALTO - USA


10 224 ms 195 ms 194 ms i-92.paix02.telstraglobal.net [202.84.247.41] PALO ALTO - USA


11 193 ms 194 ms 194 ms liberty_global-peer.eqnx03.pr.telstraglobal.net [134.159.63.85] SAN JOSE - USA


12 194 ms 194 ms 194 ms be2016.ccr22.sfo01.atlas.cogentco.com [154.54.0.177] SAN FRANCISO - USA
13 228 ms 209 ms 209 ms be3694.ccr21.pdx01.atlas.cogentco.com [154.54.84.30] PORTLAND -USA


 

And Sydney > 6 US hops > hong kong is acceptable? Regardless, it's terrible routing. No one here has been able to explain WHY it is going to the US, nor provide any solutions. Thanks heaps

Set it & forget it

With direct debit there’s no need to give paying your bill another thought.

Avoid queuing up and never worry about late fees again.

Setup direct debit