Highlighted
Sman21
Level 2: Rookie

Routing issues and high pings AGAIN

NBN in Perth 

Connecting to USA server

Once again i have pings over 50 higher than normal making gameing online very hard due to the added latency.

After my initial complaint https://crowdsupport.telstra.com.au/t5/Home-Broadband/Routing-issues/m-p/792375#M80629
something got sorted out and my pings returned to normal for a couple of months.

 

In the last week (any time/day) once again they are over 50 higher.
Could be 2 weeks as i didnt do any online gaming on US servers the week before.

 

I have been a very long time loyal Telstra customer, ive been prepared to pay the higher costs and lower data usage due to the quality of the connection.
If the quality starts becoming crap and worse than other companies there is no point staying.

Friend from Perth i play online with gets 62 less ping than me to the same server using Optus.
He used to only get 5-10 less before.

 

Wont keep paying the extra cost if this quality doesnt  improve.

 

 

Was this helpful?

  • Yes it was, thank you
  • No, I still need help
13 REPLIES 13
Another_IT_Tech
Level 2: Rookie

Re: Routing issues and high pings AGAIN

You are not alone..
From Canberra I was getting Perth Telstra server when I tried Ping from the Telstra speed test webpage but then I downloaded the Ookla windows app and tried ping test and able to Ping servers in Sydney and all tests failed ...
Level 24: Supreme Being
Level 24: Supreme Being

Re: Routing issues and high pings AGAIN

Can you post a trace route?
I am a Premium Services Support Consultant (Telstra Platinum, Telstra Smart Home, Locator/Device Locator and Neto POS). 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
Run a Modern Retail Business with Neto Point of Sale
Sman21
Level 2: Rookie

Re: Routing issues and high pings AGAIN

Yep heres some from when it was working better, still not as good as 5-6months a go
Tracing route to bosrace01-orig.iracing.com [208.118.226.161]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms mygateway [10.0.0.138]
2 * * * Request timed out.
3 3 ms 3 ms 3 ms shhh
4 3 ms 3 ms 5 ms bundle-ether6.wel-core3.perth.telstra.net [203.50.6.214]
5 33 ms 32 ms 32 ms bundle-ether3.fli-core10.adelaide.telstra.net [203.50.6.232]
6 40 ms 40 ms 42 ms bundle-ether16.win-core10.melbourne.telstra.net [203.50.6.229]
7 51 ms 52 ms 51 ms bundle-ether12.ken-core10.sydney.telstra.net [203.50.11.122]
8 52 ms 52 ms 52 ms bundle-ether1.pad-gw11.sydney.telstra.net [203.50.6.61]
9 52 ms 52 ms 52 ms bundle-ether1.sydp-core04.sydney.reach.com [203.50.13.90]
10 232 ms 233 ms 231 ms i-52.tlot-core02.bx.telstraglobal.net [202.84.137.101]
11 227 ms 227 ms 228 ms i-91.tlot02.telstraglobal.net [202.40.149.177]
12 195 ms 195 ms 196 ms l3-peer.tlot02.pr.telstraglobal.net [134.159.62.14]
13 * * * Request timed out.
14 * * * Request timed out.
15 270 ms 272 ms 270 ms bbr02-ae-3-201.bos01.twdx.net [198.160.63.120]
16 264 ms 263 ms 264 ms dcr02-hu-0-0-0-0.bos01.twdx.net [198.160.62.191]
17 268 ms 268 ms 268 ms IRACING.COM.dcr02.bos01.twdx.net [185.134.180.118]
18 * * * Request timed out.
19 269 ms 268 ms 268 ms 208.118.226.161.iracing.com [208.118.226.161]

Trace complete.

Tracing route to bosrace15-orig.iracing.com [67.218.1.15]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms mygateway [10.0.0.138]
2 * * * Request timed out.
3 4 ms 2 ms 3 ms shhh
4 4 ms 3 ms 4 ms bundle-ether6.wel-core3.perth.telstra.net [203.50.6.214]
5 33 ms 33 ms 33 ms bundle-ether3.fli-core10.adelaide.telstra.net [203.50.6.232]
6 40 ms 41 ms 40 ms bundle-ether16.win-core10.melbourne.telstra.net [203.50.6.229]
7 51 ms 52 ms 53 ms bundle-ether12.ken-core10.sydney.telstra.net [203.50.11.122]
8 51 ms 50 ms 50 ms bundle-ether1.pad-gw11.sydney.telstra.net [203.50.6.61]
9 53 ms 52 ms 50 ms bundle-ether1.sydp-core04.sydney.reach.com [203.50.13.90]
10 233 ms 232 ms 231 ms i-52.tlot-core02.bx.telstraglobal.net [202.84.137.101]
11 227 ms 229 ms 228 ms i-91.tlot02.telstraglobal.net [202.40.149.177]
12 195 ms 196 ms 195 ms l3-peer.tlot02.pr.telstraglobal.net [134.159.62.14]
13 * * * Request timed out.
14 * * * Request timed out.
15 269 ms 269 ms 269 ms bbr02-ae-3-201.bos01.twdx.net [198.160.63.120]
16 264 ms 264 ms 264 ms dcr02-hu-0-0-0-0.bos01.twdx.net [198.160.62.191]
17 271 ms 269 ms 268 ms IRACING.COM.dcr02.bos01.twdx.net [185.134.180.118]
18 * * * Request timed out.
19 263 ms 263 ms 264 ms bosrace15-orig.iracing.com [67.218.1.15]

Trace complete.

Heres one from today
Tracing route to bosrace01-orig.iracing.com [208.118.226.161]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms mygateway [10.0.0.138]
2 * * * Request timed out.
3 4 ms 4 ms 4 ms xxxxxxx
4 5 ms 5 ms 5 ms bundle-ether6.wel-core3.perth.telstra.net [203.50.6.214]
5 34 ms 32 ms 32 ms bundle-ether3.fli-core10.adelaide.telstra.net [203.50.6.232]
6 42 ms 39 ms 41 ms bundle-ether16.win-core10.melbourne.telstra.net [203.50.6.229]
7 52 ms 51 ms 51 ms bundle-ether12.ken-core10.sydney.telstra.net [203.50.11.122]
8 52 ms 51 ms 53 ms bundle-ether1.pad-gw11.sydney.telstra.net [203.50.6.61]
9 53 ms 51 ms 51 ms bundle-ether1.sydp-core04.sydney.reach.com [203.50.13.90]
10 232 ms 231 ms 239 ms i-52.tlot-core02.bx.telstraglobal.net [202.84.137.101]
11 199 ms 199 ms 199 ms i-91.tlot02.telstraglobal.net [202.40.149.177]
12 199 ms 198 ms 198 ms xe-11-2-0.edge1.losangeles6.level3.net [4.68.62.9]
13 * * * Request timed out.
14 308 ms 307 ms 307 ms TOWARDEX-TE.bear1.Boston1.Level3.net [4.53.60.66]
15 314 ms 314 ms 313 ms bbr02-et-0-0-7.bos01.twdx.net [198.160.62.0]
16 306 ms 307 ms 307 ms dcr02-hu-0-0-0-0.bos01.twdx.net [198.160.62.191]
17 313 ms 313 ms 313 ms IRACING.COM.dcr02.bos01.twdx.net [185.134.180.118]
18 * * * Request timed out.
19 306 ms 307 ms 306 ms 208.118.226.161.iracing.com [208.118.226.161]


Level 25: The Singularity
Level 25: The Singularity

Re: Routing issues and high pings AGAIN

Looks the same until after it has left the Telstra controlled part of the journey.
Never be afraid to back yourself when trying new things, just always make sure you have 3 escape routes if things go wrong.
Level 21: Augmented

Re: Routing issues and high pings AGAIN

Indeed, first hop that has a problem is Boston... And just to reinforce it - latency is not guaranteed on consumer connections and is heavily dependent on distance... Although, to be honest, I am getting much better right now from forgotten Tasmania...

PS C:\WINDOWS\system32> tracert bosrace01-orig.iracing.com

Tracing route to bosrace01-orig.iracing.com [208.118.226.161]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms mymodem.modem [192.168.0.1]
2 8 ms 7 ms 8 ms 58.162.26.185
3 8 ms 8 ms 8 ms 144.130.220.209
4 9 ms 9 ms 9 ms bundle-ether5.dav-core1.hobart.telstra.net [203.50.11.169]
5 20 ms 19 ms 20 ms bundle-ether6.win-core10.melbourne.telstra.net [203.50.6.140]
6 32 ms 32 ms 32 ms bundle-ether12.ken-core10.sydney.telstra.net [203.50.11.122]
7 32 ms 33 ms 30 ms bundle-ether1.pad-gw11.sydney.telstra.net [203.50.6.61]
8 32 ms 32 ms 32 ms bundle-ether1.sydp-core04.sydney.reach.com [203.50.13.90]
9 211 ms 211 ms 213 ms i-52.tlot-core02.bx.telstraglobal.net [202.84.137.101]
10 211 ms 211 ms 212 ms i-91.tlot02.telstraglobal.net [202.40.149.177]
11 210 ms 210 ms 210 ms l3-peer.tlot02.pr.telstraglobal.net [134.159.62.14]
12 * * * Request timed out.
13 245 ms 245 ms 245 ms TOWARDEX-TE.bear1.Boston1.Level3.net [4.53.60.66]
14 242 ms 243 ms 243 ms bbr02-et-0-0-7.bos01.twdx.net [198.160.62.0]
15 243 ms 243 ms 242 ms dcr02-hu-0-0-0-0.bos01.twdx.net [198.160.62.191]
16 241 ms 241 ms 241 ms IRACING.COM.dcr02.bos01.twdx.net [185.134.180.118]
17 * * * Request timed out.
18 241 ms 241 ms 242 ms 208.118.226.161.iracing.com [208.118.226.161]

DISCLAIMER: I do not work for Telstra or any other ISP. I never did. I have wealth of practical knowledge in Computer Security and Forensic Computing. I have been in the field since 1985.

Likes (formerly Kudos) and solutions are appreciated!!!
The comments expressed by me reflect my user experience and personal opinion.
Level 25: The Singularity
Level 25: The Singularity

Re: Routing issues and high pings AGAIN

I'm getting about 258ms one both my Telstra and TPG connections at the moment.
Never be afraid to back yourself when trying new things, just always make sure you have 3 escape routes if things go wrong.
Sman21
Level 2: Rookie

Re: Routing issues and high pings AGAIN

Yeah looks like its an issue between the LosAngeles and Boston hop, so yep may not be 100% telstra issue this time.

Around 260 is my normal ping, i understand ping isnt guaranteed but as its crucial for online gaming 50+ is just too much to be competitive with.
Then when you see others from perth with different cheaper isps getting better pings and data plans, it makes you question if its worth it.
Sman21
Level 2: Rookie

Re: Routing issues and high pings AGAIN

Ok so found out some new info and it appears to be a routing issue once again caused by Telstra trying to cut costs.
"In your case, the increased pings seem to again be because Telstra does not advertise their various IP blocks consistently. As they've reassigned different IP addresses to you over time, you've been put into completely different IP blocks (101.160.0.0/11 currently, 60.224.0.0/13 until mid-March, and 124.176.0.0/12 back until mid-February). Telstra is not advertising your current IP block (101.160.0.0/11) to Telia (a good Tier-1 backbone ISP), but they are advertising the 124.176.0.0/12 block you were on back in February to them. From our ISP:

The best path to get to 101.160.0.0/11 is through Level3 (3356), however there is an asymmetric routing with Telstra’s connectivity with Level 3. Their inbound routing to US from AU lands on Los Angeles; return route from US back to AU goes thru San Francisco Bay, as Level 3 hands off traffic to Telstra at NYC. This alone is the reason why there is 105ms+ of added latency, as the return route is adding a much longer sub-sea cable path to get back to AU.
So we hand-off traffic to you to our ISP in Boston, they hand it off to Level3 in Boston, Level3 hands it off to Telstra in NY City, and Telstra uses a bad route back to AU.
Level 21: Augmented

Re: Routing issues and high pings AGAIN

Can you prove it? TBH, I would trust more major Telco than some gaming company... But that's just my 5c worth...
DISCLAIMER: I do not work for Telstra or any other ISP. I never did. I have wealth of practical knowledge in Computer Security and Forensic Computing. I have been in the field since 1985.

Likes (formerly Kudos) and solutions are appreciated!!!
The comments expressed by me reflect my user experience and personal opinion.
Level 25: The Singularity
Level 25: The Singularity

Re: Routing issues and high pings AGAIN

And it doesn't add up. 120km (the difference between the Sydney-San Francisco and Sydney-Los Angeles routes) is more like 12ms.
Never be afraid to back yourself when trying new things, just always make sure you have 3 escape routes if things go wrong.
Level 21: Augmented

Re: Routing issues and high pings AGAIN

That's a very good point... You have earnt your level, @Jupiter!!!
DISCLAIMER: I do not work for Telstra or any other ISP. I never did. I have wealth of practical knowledge in Computer Security and Forensic Computing. I have been in the field since 1985.

Likes (formerly Kudos) and solutions are appreciated!!!
The comments expressed by me reflect my user experience and personal opinion.
Sman21
Level 2: Rookie

Re: Routing issues and high pings AGAIN

Its directly from a major network company TOWARDEX
They have been looking into why my and many other Telstra customers get 50+ pings every few months
Heres another quote from towardex to the game company
Additionally, from what our ISP can tell, Telstra seems to be pretty consistent in their BGP advertisements to their "settlement-free" network peers (where neither Telstra nor the peer have to pay the other to exchange traffic), but is much less consistent in their advertisements to the networks from which they buy transit (where Telstra has to pay the other network to exchange traffic).

The wild ping-time swings that they are seeing over time as their IP address floats to different Telstra IP blocks is likely caused by different paid transit backbone networks becoming available or unavailable to carry traffic into or out of Telstra's network.

So to me it seems like telstra are trying to avoid paying for traffic, by not advertising ip blocks to the major network carriers, this results in them using the cheaper carriers that end up equalling higher pings and packet loss.

Just like the last time when they found out Telstra werent advertising the ip blocks and then did stuff to try to trick the carriers into not sending traffic back the way it came by making it appear to be a longer route to avoid having to pay for incoming traffic.
Level 21: Augmented

Re: Routing issues and high pings AGAIN

TOWARDEX's own network map does not suggest "major network company"...
DISCLAIMER: I do not work for Telstra or any other ISP. I never did. I have wealth of practical knowledge in Computer Security and Forensic Computing. I have been in the field since 1985.

Likes (formerly Kudos) and solutions are appreciated!!!
The comments expressed by me reflect my user experience and personal opinion.

Telstra Smart Modem

Plug in and connect in minutes. Smart.

Find out more
Find out more about the Telstra 24x7 App ×
Manage your services and take advantage of offers while you’re out and about with the Telstra 24x7® App Download now
Earn points on our new rewards program and enjoy tier benefits like discounted movie tickets and moreFind out more

Need a hand or want to share your expertise?
Register for CrowdSupport and get involved

Register now