CrowdSupport®
Highlighted
Sully5
Level 3: Gumshoe

International routing problems?

Was connecting to an AWS instance in Singapore and noticed excessive latency. 

 

This has been going on since I connected to the NBN and only affects my home broadband. Ironically when I connect to my own Telstra Air hotspot, the routing is fine ~100ms (I presume this is because Telstra Air is allocated a seperate IP address).

 

Trace route:

 

1  192.168.0.1 (192.168.0.1)  2.720 ms  0.939 ms  1.231 ms

2  gateway.vb11.melbourne.asp.telstra.net (58.162.26.203)  13.967 ms  14.347 ms  15.993 ms

3  203.50.25.12 (203.50.25.12)  13.358 ms  16.312 ms

    203.50.25.14 (203.50.25.14)  12.327 ms

4  bundle-ether12.chw-core10.sydney.telstra.net (203.50.11.124)  30.918 ms  27.504 ms

    bundle-ether12.ken-core10.sydney.telstra.net (203.50.11.122)  23.727 ms

5  bundle-ether1.oxf-gw11.sydney.telstra.net (203.50.6.93)  29.292 ms  30.750 ms  29.738 ms

6  bundle-ether1.sydo-core03.sydney.reach.com (203.50.13.98)  20.557 ms  27.531 ms  28.089 ms

7  i-0-1-0-25.sydo-core03.bi.telstraglobal.net (202.84.223.18)  23.219 ms  30.138 ms  24.889 ms

8  i-15053.sgpl-core02.telstraglobal.net (202.84.140.38)  109.486 ms  116.923 ms  111.601 ms

9  i-15053.sgpl-core02.telstraglobal.net (202.84.140.38)  108.628 ms  105.726 ms

    i-91.sggs01.telstraglobal.net (202.84.244.41)  106.561 ms

10  i-91.sggs01.telstraglobal.net (202.84.244.41)  100.198 ms  107.907 ms *

11  * * *

12  * * *

13  * * *

14  * * *

15  * * *

16  * * *

17  * * *

18  * * 203.83.223.79 (203.83.223.79)  177.992 ms

19  * * *

20  * * *

21  * * *

22  * * *

23  * ec2-3-0-0-9.ap-southeast-1.compute.amazonaws.com (3.0.0.9)  171.860 ms *

 

Any ideas as to what is going on?

 

 

 

 

 

 

Was this helpful?

  • Yes it was, thank you
  • No, I still need help
35 REPLIES 35
Level 24: Supreme Being
Level 24: Supreme Being

Re: International routing problems?

Could you provide a trace route result for a Telstra Air connection?

Sully5
Level 3: Gumshoe

Re: International routing problems?

Telstra Air:

 

Traceroute has started…

 

traceroute to 3.0.0.9 (3.0.0.9), 64 hops max, 72 byte packets

1  mymodem (192.168.20.1)  4.978 ms  1.820 ms  0.950 ms

2  61.9.255.34 (61.9.255.34)  9.617 ms  13.322 ms  9.755 ms

3  172.18.39.21 (172.18.39.21)  9.988 ms  9.705 ms  21.639 ms

4  bundle-ether4.lon-edge902.melbourne.telstra.net (203.50.76.12)  13.082 ms  14.162 ms  17.323 ms

5  bundle-ether11.exi-core10.melbourne.telstra.net (203.50.11.113)  11.219 ms  12.848 ms  11.909 ms

6  bundle-ether12.chw-core10.sydney.telstra.net (203.50.11.124)  28.587 ms  26.007 ms  24.896 ms

7  bundle-ether1.oxf-gw11.sydney.telstra.net (203.50.6.93)  25.009 ms  25.407 ms  26.112 ms

8  bundle-ether1.sydo-core03.sydney.reach.com (203.50.13.98)  24.554 ms  36.327 ms  24.108 ms

9  i-15303.pthp-core02.telstraglobal.net (202.84.140.33)  64.718 ms  65.166 ms  63.275 ms

10  i-15053.sgpl-core02.telstraglobal.net (202.84.140.38)  105.628 ms  110.718 ms  109.879 ms

11  i-91.sggs01.telstraglobal.net (202.84.244.41)  111.813 ms  104.690 ms  109.492 ms

12  * * *

13  * * *

14  * * *

15  * * *

16  * * *

17  * * *

18  * * *

19  * * *

20  * * *

21  * * *

22  * * *

23  * * *

24  * * *

25  ec2-3-0-0-9.ap-southeast-1.compute.amazonaws.com (3.0.0.9)  114.003 ms  114.236 ms  111.668 ms

Sully5
Level 3: Gumshoe

Re: International routing problems?

I have tried explaining the problem to support but not a single one has understood the issue which I kind of expect. 

 

The Telstra looking-glass gets ~90ms in latency which is completely different to what I am getting.  

Level 24: Supreme Being
Level 24: Supreme Being

Re: International routing problems?

I think the Telstra looking glass only measures the latency in the Telstra network from your modem to  i-91.sggs01.telstraglobal.net (202.84.244.41)

 

If you use this site you also get about 93 Ms https://www.telstra.net/cgi-bin/trace which is the same as Telstra looking glass.

 

I can't explain the extra delay. It appears to be occurring between i-91.sggs01.telstraglobal.net (202.84.244.41) and the destination IP.

 

Sully5
Level 3: Gumshoe

Re: International routing problems?

Thanks for the reply. Do you know who the most appropriate person is to contact about this issue? I'm guessing Telstra Network Operations are the one's who typically deal with this however they don't have a publicly available contact no.

Level 24: Supreme Being
Level 24: Supreme Being

Re: International routing problems?

Sorry I don't know who to contact. Perhaps @343GuiltySpark  or @Yastiandrie  would know or be able to explain the increase in latency on a NBN connection.

 

I was wrong in my previous post about the not being to destination. I did a trace rout at with looking glass tool which returned the following.

 

 1  i-90.sydp-core03.telstraglobal.net (202.84.222.81) 3 msec  2 msec  2 msec
2  i-15401.pthw-core02.telstraglobal.net (202.84.140.30) 49 msec  50 msec  51 msec
3  i-0-0-4-4.sydo-core06.bx.telstraglobal.net (202.84.141.237) 95 msec  94 msec  96 msec
4  i-92.sggs01.telstraglobal.net (202.84.219.173) 95 msec  94 msec  94 msec
5  99.82.176.50 95 msec  93 msec  94 msec
6   *  *  *
7   *  *  *
8  52.93.10.47 [MPLS: Label 553888 Exp 0] 95 msec
    52.93.10.53 96 msec
    52.93.10.37 95 msec
9  52.93.11.77 94 msec
    52.93.11.85 94 msec
    52.93.10.237 94 msec
10 52.93.11.82 [MPLS: Labels 624416/3712 Exp 0] 95 msec
    52.93.10.236 95 msec
    52.93.11.66 95 msec
11 52.93.9.185 [MPLS: Label 3712 Exp 0] 96 msec  96 msec
    52.93.9.97 95 msec
12 52.93.10.99 96 msec
    52.93.10.101 96 msec
    52.93.10.99 95 msec
13  *  *  *
14  *  *  *
15  *  *  *
16  *  *  *
17  *  *  *
18 ec2-3-0-0-9.ap-southeast-1.compute.amazonaws.com (3.0.0.9) 94 msec  94 msec  93 msec

Level 22: Superhuman
Level 22: Superhuman

Re: International routing problems?

There is no guaranteed latency on internet services. If there is an issue a Telstra server/network link on the core network, it will be picked up and fixed by the networks team.
For Official Support start a Secure Chat , try the Online Troubleshooter, Outage Check or Complaint.

Full Disclosure as part of Telstras Social Media Code.

Sully5
Level 3: Gumshoe

Re: International routing problems?

I understand there is no guaranteed latencies, but why do the two connection on the same 'Telstra Smart Modem' have two very different response times? This has been going on for over two months, so it definitely doesn't seem like it will be "picked up" anytime soon.    

Sully5
Level 3: Gumshoe

Re: International routing problems?

Here is another affected IP:

 

45.32.100.168 (Singapore)

 

Neighbour literally next door gets 110ms (with AussieBB) whilst I get ~260ms and heck once again, my own Telstra Air connection gets 190ms which again is a massive difference. 

 

1  192.168.0.1 (192.168.0.1)  2.280 ms  1.798 ms  1.005 ms

2  gateway.vb11.melbourne.asp.telstra.net (58.162.26.203)  21.660 ms  9.542 ms  9.011 ms

3  203.50.25.14 (203.50.25.14)  9.890 ms  10.891 ms  10.899 ms

4  bundle-ether12.ken-core10.sydney.telstra.net (203.50.11.122)  21.121 ms

    bundle-ether12.chw-core10.sydney.telstra.net (203.50.11.124)  24.019 ms  22.729 ms

5  bundle-ether1.pad-gw11.sydney.telstra.net (203.50.6.61)  22.819 ms  21.846 ms  22.347 ms

6  bundle-ether1.sydo-core03.sydney.reach.com (203.50.13.98)  24.565 ms

    bundle-ether1.sydp-core04.sydney.reach.com (203.50.13.90)  22.268 ms

    bundle-ether1.sydo-core03.sydney.reach.com (203.50.13.98)  24.326 ms

7  i-20802.eqnx-core02.telstraglobal.net (202.84.141.25)  158.349 ms  157.104 ms

    i-73.paix-core02.telstraglobal.net (202.84.247.45)  179.439 ms

8  i-92.eqnx03.telstraglobal.net (202.84.247.17)  156.232 ms  156.066 ms  156.180 ms

9  ae20.cr6-sjc1.ip4.gtt.net (173.205.49.221)  177.988 ms  167.852 ms

    gtt-peer.paix02.pr.telstraglobal.net (134.159.61.98)  178.167 ms

10  89.149.131.6 (89.149.131.6)  207.020 ms

    141.136.110.158 (141.136.110.158)  306.689 ms  307.002 ms

11  ip4.gtt.net (103.232.18.42)  306.279 ms  294.251 ms  309.602 ms

12  * * *

13  * * *

14  * * *

15  45.32.100.168 (45.32.100.168)  276.901 ms  263.014 ms  302.362 ms

 

Guarantee or not, Telstra should be doing better, especially when they position themselves as a 'Premium' provider.  

Level 22: Superhuman
Level 22: Superhuman

Re: International routing problems?

From my Telstra FTTP connection in North QLD

Server: 3.0.0.9 1 

 

1 <1 ms <1 ms <1 ms mymodem.modem [192.168.0.1]
2 1 ms 1 ms 1 ms gateway.qb51.townsville.asp.telstra.net [58.162.26.31]
3 17 ms 17 ms 17 ms 144.130.213.209
4 19 ms 18 ms 18 ms bundle-ether6.cha-core4.brisbane.telstra.net [203.50.11.140]
5 33 ms 33 ms 33 ms bundle-ether20.ken-core10.sydney.telstra.net [203.50.11.178]
6 32 ms 31 ms 33 ms bundle-ether1.pad-gw11.sydney.telstra.net [203.50.6.61]
7 33 ms 33 ms 33 ms bundle-ether1.sydp-core04.sydney.reach.com [203.50.13.90]
8 32 ms 33 ms 33 ms i-0-1-0-25.sydo-core03.bi.telstraglobal.net [202.84.223.18]
9 79 ms 78 ms 79 ms i-15303.pthp-core02.telstraglobal.net [202.84.140.33]
10 130 ms 124 ms 126 ms i-15053.sgpl-core02.telstraglobal.net [202.84.140.38]
11 123 ms 124 ms 124 ms i-91.sggs01.telstraglobal.net [202.84.244.41]
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 174 ms 174 ms 175 ms 203.83.223.79
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 179 ms 179 ms 180 ms ec2-3-0-0-9.ap-southeast-1.compute.amazonaws.com [3.0.0.9]

 

i-91.sggs01.telstraglobal.net [202.84.244.41] is when it its Singapore and is leaving the Telstra global network - issue would appear to be in Singapore at that stage.

 

Server: 45.32.100.168 

 

1 <1 ms <1 ms <1 ms mymodem.modem [192.168.0.1]
2 1 ms 1 ms 2 ms gateway.qb51.townsville.asp.telstra.net [58.162.26.31]
3 17 ms 16 ms 17 ms 144.130.213.209
4 17 ms 18 ms 18 ms bundle-ether6.cha-core4.brisbane.telstra.net [203.50.11.140]
5 33 ms 33 ms 32 ms bundle-ether20.ken-core10.sydney.telstra.net [203.50.11.178]
6 33 ms 31 ms 33 ms bundle-ether1.pad-gw11.sydney.telstra.net [203.50.6.61]
7 33 ms 31 ms 33 ms bundle-ether1.sydp-core04.sydney.reach.com [203.50.13.90]
8 167 ms 168 ms 167 ms i-20802.eqnx-core02.telstraglobal.net [202.84.141.25]
9 166 ms 167 ms 166 ms i-92.eqnx03.telstraglobal.net [202.84.247.17]
10 184 ms 168 ms 172 ms ae20.cr6-sjc1.ip4.gtt.net [173.205.49.221]
11 227 ms 227 ms 228 ms 89.149.131.6
12 227 ms 227 ms 227 ms ip4.gtt.net [103.232.18.42]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 278 ms 278 ms 278 ms 45.32.100.168

 

i-92.eqnx03.telstraglobal.net [202.84.247.17] is in the USA - not sure why its going there -

ae20.cr6-sjc1.ip4.gtt.net [173.205.49.221] is also USA according to IPlookup

89.149.131.6 is apparently Dublin but is more likely sydney

ip4.gtt.net [103.232.18.42] indicates its come back to Sydney then according to IPLookup 45.32.100.168 is in Singapore. 

For Official Support start a Secure Chat , try the Online Troubleshooter, Outage Check or Complaint.

Full Disclosure as part of Telstras Social Media Code.

Sully5
Level 3: Gumshoe

Re: International routing problems?

The 45.32.100.168 IP is definitely in Singapore, no idea why it is taking this scenic route... 

Sully5
Level 3: Gumshoe

Re: International routing problems?

I decided to do a comparison for 45.32.100.168 amongst different ISP's through their looking glass based in Sydney, spoiler, Telstra was the slowest!

 

Telstra:

240ms

 

TPG:

164ms

 

Optus:

154ms

 

AussieBroadband:

97ms

 

There is something very wrong here, could we get a response from someone in network's on what is going on?

 

 

 

 

 

Level 22: Superhuman
Level 22: Superhuman

Re: International routing problems?

As advised earlier there is no guaranteed Latency on consumer services as highlighted in this post https://crowdsupport.telstra.com.au/t5/Broadband-nbn/International-routing-latency-and-ping/ta-p/309...

 

Additionally consumer internet services are best effort services as defined below, which doesn't guarantee the fastest route or transmit corrupted or lost packets that can can impact latency.

 

Best Effort Definition: Best effort refers to a network service that attempts to deliver messages to their intended destinations but which does not provide any special features that re-transmit corrupted or lost packets. Thus, there are no guarantees regarding delivery.

 

This is only a community forum where customers are assisted by other customers and is not monitored by the networks team.

For Official Support start a Secure Chat , try the Online Troubleshooter, Outage Check or Complaint.

Full Disclosure as part of Telstras Social Media Code.

Sully5
Level 3: Gumshoe

Re: International routing problems?

Sorry, but that is complete nonsense. When other ISP's are able to route the same path up to 145ms faster, you know there is a problem. Guarantee or not, Telstra should actually get their "world class network operations" to look at the issue and investigate. 

 

Here is the impression I'm getting from Telstra, charge premium prices, deliver routing that is beaten by the most budget carriers, some of which even use Telstra for IP Transit! Guess you don't always get what you pay for. 

 

You can't go to support to fix the issue because they simply don't know what to do, Crowd-support can't help because their OWN forum isn't monitored by staff. 

 

Sorry Telstra, but this isn't good enough. 

Level 25: The Singularity
Level 25: The Singularity

Re: International routing problems?

Just to add my 2ms worth. I'm getting 295ms on my TPG connection and 184ms on Telstra mobile to 3.0.0.9

To 45.32.100.168 it is 269ms via TPG and 298ms via Telstra.

The latency jumps are occurring outside Australia on both lots of tests.
Never be afraid to back yourself when trying new things, just always make sure you have 3 escape routes if things go wrong.
Sully5
Level 3: Gumshoe

Re: International routing problems?

The tests I conducted were through the looking glass based in Sydney. Appreciate your response however. 

Level 22: Superhuman
Level 22: Superhuman

Re: International routing problems?

Latency isn't supported as the is no guaranteed latency, hence when you call or contact support online they are unable to assist. To my knowledge other ISP's in Australia do not have latency guarantees either. As your data is reaching its destination there isn't a fault. Crowd Support is Monitored by a social media team, not the networks team.
For Official Support start a Secure Chat , try the Online Troubleshooter, Outage Check or Complaint.

Full Disclosure as part of Telstras Social Media Code.

Sully5
Level 3: Gumshoe

Re: International routing problems?

Can the social media team not forward the issue to Networks?

Level 22: Superhuman
Level 22: Superhuman

Re: International routing problems?

Crowd Support isn't a channel to raise faults and I'm not sure if they will be able to. However I don't speak for the Social Media team and we'll need to allow them provide a response to your question.
For Official Support start a Secure Chat , try the Online Troubleshooter, Outage Check or Complaint.

Full Disclosure as part of Telstras Social Media Code.

Sully5
Level 3: Gumshoe

Re: International routing problems?

If it isn't a channel to raise faults, why did support tell me this was my best shot at getting the issue resolved? 

Level 22: Superhuman
Level 22: Superhuman

Re: International routing problems?

There are only two ways to get faults raised officially by calling Telstra and via live chat, no form of social media is a medium to raise a fault due to privacy reasons (Except for the sport apps such as AFL and NRL that Crowd Support is the official channel for) As Crowd Support is only a community forum the members here can't access your account information or have access to the tools to diagnose (depending on the issue) and raise a fault. Staff that are here on Crowd Support officially and here as another customer (me) can't access your accounts due to privacy reasons.

 

For issues out of scope for level 1 faults that can't be escalated to level 2 or are out of scope you may have been referred here as there is an active community of customers assisting other customers.

For Official Support start a Secure Chat , try the Online Troubleshooter, Outage Check or Complaint.

Full Disclosure as part of Telstras Social Media Code.

Sully5
Level 3: Gumshoe

Re: International routing problems?

Could a staff member please respond to this? I utilise AWS on a daily basis and would really appreciate if someone could forward this to the Network team as there is obviously a routing fault going-on. 

Sully5
Level 3: Gumshoe

Re: International routing problems?

Well here is an update, my ping to 3.0.0.9 has now shot up to 270ms!

 

traceroute to 3.0.0.9 (3.0.0.9), 64 hops max, 52 byte packets

1  192.168.0.1 (192.168.0.1)  2.600 ms  1.112 ms  0.904 ms

2  gateway.vb11.melbourne.asp.telstra.net (58.162.26.203)  9.103 ms  8.948 ms  9.265 ms

3  203.50.25.12 (203.50.25.12)  11.389 ms

    203.50.25.14 (203.50.25.14)  10.319 ms

    203.50.25.12 (203.50.25.12)  11.492 ms

4  bundle-ether12.chw-core10.sydney.telstra.net (203.50.11.124)  23.645 ms  23.646 ms

    bundle-ether12.ken-core10.sydney.telstra.net (203.50.11.122)  23.070 ms

5  bundle-ether1.oxf-gw11.sydney.telstra.net (203.50.6.93)  24.807 ms  25.698 ms

    bundle-ether1.pad-gw11.sydney.telstra.net (203.50.6.61)  23.537 ms

6  bundle-ether1.sydp-core04.sydney.reach.com (203.50.13.90)  23.230 ms  24.069 ms

    bundle-ether1.sydo-core03.sydney.reach.com (203.50.13.98)  24.154 ms

7  i-0-1-0-25.sydo-core03.bi.telstraglobal.net (202.84.223.18)  23.568 ms

    i-15303.pthp-core02.telstraglobal.net (202.84.140.33)  59.081 ms

    i-0-1-0-25.sydo-core03.bi.telstraglobal.net (202.84.223.18)  24.805 ms

8  i-15053.sgpl-core02.telstraglobal.net (202.84.140.38)  104.428 ms

    i-15303.pthp-core02.telstraglobal.net (202.84.140.33)  58.058 ms  59.479 ms

9  i-15053.sgpl-core02.telstraglobal.net (202.84.140.38)  104.898 ms

    i-91.sggs01.telstraglobal.net (202.84.244.41)  137.288 ms  105.568 ms

10  * i-91.sggs01.telstraglobal.net (202.84.244.41)  105.200 ms  104.082 ms

11  * * *

12  * * *

13  * * *

14  * * *

15  * * *

16  * * *

17  203.83.223.79 (203.83.223.79)  267.712 ms

    203.83.223.27 (203.83.223.27)  259.427 ms *

18  203.83.223.27 (203.83.223.27)  258.608 ms  258.538 ms

    203.83.223.79 (203.83.223.79)  258.370 ms

19  * * *

20  * * *

21  * * *

22  * * *

23  * ec2-3-0-0-9.ap-southeast-1.compute.amazonaws.com (3.0.0.9)  342.907 ms  269.759 ms

 

'Best effort' actually takes some effort.

 

 

Level 25: The Singularity
Level 25: The Singularity

Re: International routing problems?

The jumps in latency are occurring at the AWS boundary between Hong Kong and Singapore (203.83.223.79).

Have you contacted AWS to find out if there is an issue?

Never be afraid to back yourself when trying new things, just always make sure you have 3 escape routes if things go wrong.
Sully5
Level 3: Gumshoe

Re: International routing problems?

Yep, Amazon just pin it back at the ISP which in this case is Telstra for taking a sub-optimal route. Kind of makes sense when all other ISP's perform the route in around 100ms.

Sully5
Level 3: Gumshoe

Re: International routing problems?

It also doesn't make sense that Telstra's own looking-glass does the route in around ~95ms whereas I am getting 250ms... 

Sully5
Level 3: Gumshoe

Re: International routing problems?

Since Telstra is the most incompetent company in the world, I have taken routing into my own hands. Ended up creating an Azure instance based in Melbourne and am using it as a VPN server. 

 

Here is a summary of the latency differences between the two:

 

3.0.0.9 (Amazon Web Services, Singapore)

 

Latency with Telstra: 250ms 

Latency over VPN: 98ms

 

45.32.100.168 (Vultr, Singapore)

 

Latency with Telstra: 240ms

Latency with VPN: 100ms

 

Conclusions: Telstra routing is hopeless; in the worse case scenario, there was a 240% decrease in latency which is a massive improvement. 

 

Since Telstra doesn't even want to try and resolve the issue, I will be going to the TIO over false advertising and suggest that anyone else who faces the issue do the same. Completely unacceptable that they drag customers in by showing amazing ping times on their looking-glass and then the reality is that you get no where near what was indicated. Maybe this will actually get them to look over the issue instead of just blatantly ignoring it and use the scape-goat excuse of saying latency isn't guaranteed. What is the point of a looking-glass if you're not going to take the same routes?

Level 25: The Singularity
Level 25: The Singularity

Re: International routing problems?

Looking glass is run by Telstra Global, which is different to the Retail Telstra that you deal with. The TIO won't act on your complaint in all likelihood.
Never be afraid to back yourself when trying new things, just always make sure you have 3 escape routes if things go wrong.
Sully5
Level 3: Gumshoe

Re: International routing problems?

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

 

Where on this site does it say 'Telstra Global'?

Level 25: The Singularity
Level 25: The Singularity

Re: International routing problems?

My god, that's and ancient remnant. I thought all the telstra.net pages were deprecated a decade ago.

 

I was using https://lg.telstraglobal.com/

Never be afraid to back yourself when trying new things, just always make sure you have 3 escape routes if things go wrong.
Sully5
Level 3: Gumshoe

Re: International routing problems?

Here is a response I got on another forum:

 

"Easy.

Vulture doesn’t connect or buy services from Telstra; so Telstra routes the traffic to GTT via the highest bandwidth to GTT in Palo Alto, California instead. Telstra does not Peer on the free peering exchanges either; since they’re “special” and don’t give away free bandwidth to other providers without payment.

So – You can either tell Vultur to sign a 10G transit contract with Telstra at $40,000-$60,000 USD a month so that there’s a direct network path between your bigpond connection and your vultur server. (I’m sure vultur will be happy to pass on the cost of that link to you to save you a few hundred milliseconds.)

Or.

You change ISPs to one who peers in Singapore either on SGIX or Equinix EIE SG where vultur likely does. Most other Australian ISPs do indeed peer on the local Singapore peering exchanges which is why another provider works fine. .

Telstra doesn’t peer generally. They’d much rather other providers pay to transit their network or reach a Telstra customer. They only free-peer with Optus/TPG/Vocus in OZ. Everyone else has to pay, or transit via a Global upstream such as GTT or Telia."

 

That is most probably the answer to our latency woes that none of these "Telstra Platinum" people were able to tell me. 

TLDR: Want good ping? Don't choose Telstra. 

Level 22: Superhuman
Level 22: Superhuman

Re: International routing problems?

1: Telstra Platinum aren't network specialists that can dig that deep as it's out if scope.
2: Even if that answer is correct then having a Telstra connection doesn't your increase ping/latency doesn't apply to every situation.
For Official Support start a Secure Chat , try the Online Troubleshooter, Outage Check or Complaint.

Full Disclosure as part of Telstras Social Media Code.

flare
Level 2: Rookie

Re: International routing problems?

We have been having similar issues lately when connecting to servers in Malaysia. We have accepted that Telstra always seems to take a longer route, Canberra -> Sydney -> Adelaide -> Perth -> Singapore -> Malaysia but even so round trips are usually within 110ms.

 

Recently the route has changed and we are now getting 380ms++ round trips :-(

 

[root@centos ~]# traceroute 110.xx.xx.xx
traceroute to 110.xx.xx.xx (110.xx.xx.xx), 30 hops max, 60 byte packets
1 gateway (192.168.100.1) 0.340 ms 0.365 ms 0.382 ms
2 192.168.1.254 (192.168.1.254) 1.990 ms 1.997 ms 2.004 ms
3 gateway.ab01.canberra.asp.telstra.net (58.162.26.177) 3.620 ms 4.397 ms 4.745 ms
4 144.130.218.209 (144.130.218.209) 5.197 ms 5.180 ms 5.855 ms
5 Bundle-Ethernet6.civ-core2.canberra.telstra.net (203.50.8.34) 8.241 ms 8.233 ms 9.326 ms
6 bundle-ether15.chw-core10.sydney.telstra.net (203.50.6.81) 16.106 ms 22.749 ms 22.727 ms
7 bundle-ether1.oxf-gw11.sydney.telstra.net (203.50.6.93) 10.290 ms 11.641 ms 11.617 ms
8 bundle-ether1.sydo-core03.sydney.reach.com (203.50.13.98) 11.246 ms 11.182 ms 13.516 ms
9 i-73.paix-core02.telstraglobal.net (202.84.247.45) 199.104 ms 199.034 ms 198.599 ms
10 i-92.paix02.telstraglobal.net (202.84.247.41) 201.807 ms 199.060 ms 199.787 ms
11 liberty_global-peer.eqnx03.pr.telstraglobal.net (134.159.63.85) 155.737 ms 155.583 ms 156.463 ms
12 be2013.ccr41.sjc03.atlas.cogentco.com (154.54.5.105) 156.360 ms 156.371 ms 154.309 ms
13 be3144.ccr22.sjc01.atlas.cogentco.com (154.54.5.101) 156.263 ms 156.289 ms 155.840 ms
14 be3176.ccr41.lax01.atlas.cogentco.com (154.54.31.189) 167.914 ms be3177.ccr42.lax01.atlas.cogentco.com (154.54.40.145) 168.476 ms 168.789 ms
15 be3360.ccr41.lax04.atlas.cogentco.com (154.54.25.150) 168.027 ms 167.952 ms 167.565 ms
16 38.104.210.82 (38.104.210.82) 167.537 ms 167.134 ms 167.512 ms
17 ae-4.cr-gw-1-sin-pip.sg.globaltransit.net (124.158.224.97) 268.953 ms 267.848 ms 268.790 ms
18 ae-1.cr-gw-2-kul-pip.my.globaltransit.net (61.11.212.57) 264.749 ms ae-10.cr-gw-1-sin-pip.sg.globaltransit.net (124.158.224.61) 268.715 ms 267.508 ms
19 ae-2.cr-gw-1-kul-pip.my.globaltransit.net (61.11.210.105) 266.713 ms 266.720 ms 267.101 ms
20 xe-0-2-0-0.edge-gw-2-kul-pip.my.globaltransit.net (61.11.210.175) 268.711 ms 267.497 ms xe-1-2-0-0.edge-gw-2-kul-pip.my.globaltransit.net (61.11.211.175) 263.621 ms
21 gi-0-1.cr-gw-2-mah.my.aims.my (124.158.228.6) 266.614 ms 268.546 ms 269.074 ms
22 * * *
23 cloud.xx.xx (110.xx.xx.xx) 387.190 ms 386.966 ms 387.471 ms

 

Reported to Telstra more than 2 weeks ago and as usual been given the run around and response there is nothing wrong.

 

Now looking for alternative providers.

 

Level 25: The Singularity
Level 25: The Singularity

Re: International routing problems?

I suspect that there is an issue in the Singapore leg as I can't get a traceroute to progess beyond there by any of my connections (Telstra, TPG or my corporate VPN out of the USA). My corporate connection gets stuck within the Singtel network (pings of low 500ms). My TPG connection doesn't even get out of its own network segment within Singapore.

Never be afraid to back yourself when trying new things, just always make sure you have 3 escape routes if things go wrong.
flare
Level 2: Rookie

Re: International routing problems?

The SG connection is just one of them . We are having timeouts with every site including to and from some of our servers in Sydney, Google,Facebook etc.

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
Find out more about the Telstra 24x7 App and direct debit ×
Manage your services and take advantage of offers while you’re out and about with the Telstra 24x7® App Find out more

Avoid queueing up and never worry about late fees againSet up direct debit

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

Register now