TPG Community

Get online support

Suboptimal routing from Sydney to Los Angeles

Level 1

I'm seeing some suboptimal routing to LAX in the last few days. For example:

 

traceroute to 66.165.241.249 (66.165.241.249), 64 hops max, 52 byte packets
 1  10.0.4.1 (10.0.4.1)  2.400 ms  2.633 ms  2.090 ms
 2  10.20.20.116 (10.20.20.116)  8.772 ms  7.142 ms  9.292 ms
 3  syd-gls-har-int2-be200.tpgi.com.au (203.221.3.68)  9.554 ms  9.360 ms  9.059 ms
 4  hurricaneelectric1-100g.hkix.net (123.255.91.158)  221.309 ms  222.146 ms  221.230 ms
 5  100ge11-1.core1.lax2.he.net (184.105.64.125)  222.076 ms  223.312 ms  239.959 ms
 6  100ge2-2.core1.lax1.he.net (72.52.92.121)  221.139 ms  220.793 ms  221.896 ms
 7  64.71.134.142 (64.71.134.142)  216.174 ms  214.946 ms  215.547 ms
 8  * * *
 9  66-165-241-249.static.hvvc.us (66.165.241.249)  215.006 ms  215.492 ms  215.351 ms

Seems to be going via Hong Kong instead of direct. Last week it was going direct to LAX, with latency in the 150-160ms range.

I wonder if this is related to the recent Level 3 outage somehow?

1 REPLY 1
Moderator

Hi @cynix ,

 

Thanks for raising this to us. Please send me your account details (Username/Customer ID together with the address on file) also include your best contact number and preferred time together with the complete Tracert and ping test result.

 

In case you need a reference:

 

How do I private message (PM) in the community 

 

Regards,

 


@cynix wrote:

I'm seeing some suboptimal routing to LAX in the last few days. For example:

 

traceroute to 66.165.241.249 (66.165.241.249), 64 hops max, 52 byte packets
 1  10.0.4.1 (10.0.4.1)  2.400 ms  2.633 ms  2.090 ms
 2  10.20.20.116 (10.20.20.116)  8.772 ms  7.142 ms  9.292 ms
 3  syd-gls-har-int2-be200.tpgi.com.au (203.221.3.68)  9.554 ms  9.360 ms  9.059 ms
 4  hurricaneelectric1-100g.hkix.net (123.255.91.158)  221.309 ms  222.146 ms  221.230 ms
 5  100ge11-1.core1.lax2.he.net (184.105.64.125)  222.076 ms  223.312 ms  239.959 ms
 6  100ge2-2.core1.lax1.he.net (72.52.92.121)  221.139 ms  220.793 ms  221.896 ms
 7  64.71.134.142 (64.71.134.142)  216.174 ms  214.946 ms  215.547 ms
 8  * * *
 9  66-165-241-249.static.hvvc.us (66.165.241.249)  215.006 ms  215.492 ms  215.351 ms

Seems to be going via Hong Kong instead of direct. Last week it was going direct to LAX, with latency in the 150-160ms range.

I wonder if this is related to the recent Level 3 outage somehow?