LtYu
Level 2: Rookie

Why traffic to Chinese server need to go to US first (Hijacked by US?)

Hi guys,

please help!

 

Tried to connect Chinese server from my local desktop, Telstra NBN (FTTC), HIGH PING (latency)!!

 

Tracing route to 223.252.226.255 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms RT-AC86U-57B0 [192.168.1.1]
2 <1 ms <1 ms <1 ms mymodem.modem [192.168.0.1]
3 28 ms 25 ms 17 ms gateway.vb02.melbourne.asp.telstra.net [58.162.26.194]
4 10 ms 5 ms 5 ms ae10.win-ice301.melbourne.telstra.net [203.50.61.145]
5 7 ms 7 ms 7 ms bundle-ether25.win-core10.melbourne.telstra.net [203.50.61.144]
6 18 ms 18 ms 18 ms bundle-ether12.ken-core10.sydney.telstra.net [203.50.11.122]
7 18 ms 18 ms 19 ms bundle-ether1.pad-gw11.sydney.telstra.net [203.50.6.61]
8 20 ms 17 ms 23 ms unknown.telstraglobal.net [210.176.152.125]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 161 ms 160 ms 162 ms las-b23-link.ip.twelve99.net [213.248.92.106]
14 160 ms 162 ms * las-b22-link.ip.twelve99.net [62.115.143.39]
15 160 ms 159 ms 165 ms las-b24-link.ip.twelve99.net [62.115.125.163]
16 303 ms 318 ms 317 ms chinaunicom-ic-151188-las-bb1.ip.twelve99.net [213.248.94.126]
17 312 ms 326 ms 311 ms 219.158.102.153
18 337 ms 334 ms 352 ms 219.158.16.69
19 325 ms 310 ms 326 ms 219.158.5.149
20 366 ms 350 ms 366 ms 219.158.100.174
21 349 ms * * 124.160.189.102
22 335 ms 364 ms 333 ms 223.252.226.255

Trace complete.

----------------------------------

 

And I tried to ping 223.252.226.255 via Telstra looking glass (POP Sydney, https://lg.telstraglobal.com/)
The latency is ~150ms, I tried traceroute, but it cannot complete, and gives an error.

 

Why it is ~360 ms latency from my local NBN, and it went to US first?

 

Thanks, guys

Was this helpful?

  • Yes it was, thank you
  • No, I still need help
14 REPLIES 14
jayonaise
Support Team
Support Team

Re: Why traffic to Chinese server need to go to US first (Hijacked by US?)

Have you been experiencing this problem before, or is this a more recent issue?

 

There is a previous thread on the same subject here:

https://tel.st/nlf3m

 

Jupiter
Level 25: The Singularity
Level 25: The Singularity

Re: Why traffic to Chinese server need to go to US first (Hijacked by US?)

That's not an unusual route to get to that endpoint. From my non-Telstra connection:

1 101 ms 1 ms 1 ms ---.---.---.---
2 15 ms 8 ms 5 ms 10.128.5.61
3 6 ms 5 ms 5 ms 10.240.64.136
4 5 ms 4 ms 5 ms 10.240.64.164
5 5 ms 5 ms 5 ms 10.240.64.0
6 5 ms 5 ms 5 ms et1-2.br-01.ndm1.vic.spirit.net.au [202.90.50.44]
7 6 ms 6 ms 5 ms static-101.110.255.49.in-addr.VOCUS.net.au [49.255.112.101]
8 166 ms 165 ms 165 ms be150.cor02.mel11.vic.vocus.network [114.31.196.56]
9 * * * Request timed out.
10 166 ms 165 ms 165 ms be802.lsr01.dody.nsw.vocus.network [103.1.76.148]
11 165 ms 165 ms 165 ms be220.cor02.syd04.nsw.vocus.network [103.1.77.17]
12 165 ms 165 ms 165 ms be202.bdr03.sjc01.ca.us.vocus.network [114.31.199.43]
13 165 ms 165 ms 165 ms 173.205.35.1
14 173 ms 165 ms 165 ms ae2.cr5-sjc1.ip4.gtt.net [89.149.180.26]
15 323 ms 326 ms 326 ms ip4.gtt.net [173.205.40.118]
16 328 ms 325 ms 329 ms 219.158.97.181
17 320 ms 319 ms 325 ms 219.158.19.90
18 323 ms 333 ms 319 ms 219.158.19.69
19 318 ms 318 ms 317 ms 219.158.98.222
20 339 ms 329 ms * 124.160.189.138
21 * * * Request timed out.
22 328 ms 328 ms 328 ms 223.252.226.255

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

Re: Why traffic to Chinese server need to go to US first (Hijacked by US?)

Thanks for the reply, I have this issue since I got connected, it may be related route-policy of Telstra global.

LtYu
Level 2: Rookie

Re: Why traffic to Chinese server need to go to US first (Hijacked by US?)

I knew some ISPs have a better route, e.g. AARNet, Swoop, but since it is ~150ms via Telstra global looking glass (From Sydney POP) in my screenshot earlier, then I expect I should get similar latency.

 

BTW, I can see Chinese AS in Telstra global (AS4637) peer list below,

 

53China Mobile International Limited
Hong Kong
XAS58453
79China Telecom Backbone
China
XAS4134
107China Telecom Next Generation Carrier Network
China
 AS4809
117China Unicom Backbone
China
 AS4837

 

but the traffic goes via

3Telia Company AB
Sweden
XAS1299

 

Thanks,

LtYu
Level 2: Rookie

Re: Why traffic to Chinese server need to go to US first (Hijacked by US?)

Thanks for the reply,

 

I knew some ISPs have good route to China,  e.g. AARNet, Swoop

 

AARNet looking glass (https://lg.aarnet.edu.au/)

--- 223.252.226.255 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 1805ms
rtt min/avg/max/mdev = 156.396/156.734/157.891/0.621 ms

Swoop (DCSI) looking glass (http://lg.as58511.net/looking-glass/)

--- 223.252.226.255 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 151.717/152.524/155.413/1.032 ms

 

So when I get a similar ping from Telstra looping glass (https://lg.telstraglobal.com/)  by choosing Sydney POP, I expect a similar ping from my local

Date Min Latency (ms) Max Latency (ms) Avg Latency (ms) Std Deviation (ms) Loss (%)

Fri Apr 23 11:00:26 2021 UTC1471481470.40

 

Thanks

 

Mkrtich
Level 21: Augmented
Level 21: Augmented

Re: Why traffic to Chinese server need to go to US first (Hijacked by US?)

Hi - there are some interesting trace entries in your screen information however I am not experienced in these matters. As a matter of interest, have you always had the ASUS as the secondary router and have you done a similar tracert command with a PC directly connected to the Ethernet port of your primary Telstra Modem (if not in Bridge Mode) rather than using the ASUS Router? 

 

Wondering if your Telstra modem has DHCP IPv6 Prefix Definition and DHCP IPv6 Enabled, if an IPv6 connection would show the same outcome. There may be some IPV4 to IPV6  or IPV6 to IPV4 encapsulations and conversions occurring between ISP routers during the transmission paths. If the Telstra modem is a Gen1.1 or 2, you could force it to use IPV6 by disconnecting it from the Internet which places it into auto 4G back up mode for testing. If that doesn't help , you could try enabling IPv4/IPv6 in the 4G screen of your modem to see if any difference.  

 

Your target server address - is it a very popular site - 223.252.226.255  - it must sit in a sizeable network which must have up to 65,536 IP addresses (Subnet Mask 255:255:0:0) as it ends with a .255 ( usually used as the reserved broadcast address for smaller 255.255.255.0 networks with under 254 IP addresses) .The closest I got to identifying it was 223.252.226.0/25 - according to Google it looks like Shanghai NetEast Computer. Interesting that twelve99.net is indeed Sweden's Telia USA based routers - just shows how varied the routing is with the Internet. 

 

Does the Telstra Looking Glass Perth POP also fail its BGP test? I don't know if Telstra has two international Gateways or everything goes via Sydney. 

 

 

LtYu
Level 2: Rookie

Re: Why traffic to Chinese server need to go to US first (Hijacked by US?)

Thanks for your replay, I am using TELSTRA SMART MODEMTM GEN 2

 

I got the similar result when tried to connect directly to Telstra router

 

Tracing route to 223.252.226.255 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms mymodem.modem [192.168.0.1]
2 5 ms 5 ms 5 ms gateway.vb02.melbourne.asp.telstra.net [58.162.26.194]
3 9 ms 32 ms 11 ms ae10.win-ice301.melbourne.telstra.net [203.50.61.145]
4 6 ms 8 ms 5 ms bundle-ether25.win-core10.melbourne.telstra.net [203.50.61.144]
5 17 ms 17 ms 19 ms bundle-ether12.ken-core10.sydney.telstra.net [203.50.11.122]
6 17 ms 19 ms 18 ms bundle-ether1.pad-gw11.sydney.telstra.net [203.50.6.61]
7 18 ms 17 ms 18 ms unknown.telstraglobal.net [210.176.152.125]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 160 ms 160 ms 160 ms las-b23-link.ip.twelve99.net [213.248.92.106]
13 160 ms * 160 ms las-b22-link.ip.twelve99.net [62.115.143.39]
14 160 ms 191 ms 160 ms las-b24-link.ip.twelve99.net [62.115.125.163]
15 322 ms 311 ms 327 ms chinaunicom-ic-151188-las-bb1.ip.twelve99.net [213.248.94.126]
16 335 ms 323 ms 335 ms 219.158.102.153
17 357 ms 343 ms 359 ms 219.158.16.69
18 354 ms 320 ms 334 ms 219.158.5.149
19 370 ms 377 ms 377 ms 219.158.100.174
20 * * * Request timed out.
21 345 ms 363 ms 361 ms 223.252.226.255

Trace complete.

 

==========================

 

When I am using Perth POP on Telstra looking glass, the latency is even better ~110ms

 

Date Min Latency (ms) Max Latency (ms) Avg Latency (ms) Std Deviation (ms) Loss (%)

Sat Apr 24 07:42:18 2021 UTC1091101090.490

 

Also, I tried trace route, and here is the info before Telstra looking glass give me an error

It seems Telstra is definitely capable to send traffic

from Telstra Global AS4637 to Chinese Backbone of CNC group AS4837 

 

---------------Telstra looking glass trace route result (partial)---------------------

1 i-0-4-0-1.pthp-core02.telstraglobal.net (202.84.140.246) 2 msec 3 msec 1 msec
2 i-15053.sgpl-core02.telstraglobal.net (202.84.140.38) 49 msec 49 msec 50 msec
3 i-15053.sgpl-core02.telstraglobal.net (202.84.140.38) [MPLS: Label 24107 Exp 0] 80 msec 79 msec 79 msec
4 202.84.249.161 78 msec 77 msec 79 msec
5 202.84.249.161 [MPLS: Label 24021 Exp 0] 81 msec 81 msec 80 msec
6 i-90.hkhh11.telstraglobal.net (202.84.154.238) 80 msec 79 msec 79 msec (Telstra Global AS4637)
7 219.158.40.233 80 msec 81 msec 79 msec  (Chinese Router AS4837)
8 219.158.10.61 91 msec 89 msec 87 msec
9 219.158.96.206 87 msec 85 msec 87 msec
10 219.158.8.121 84 msec 83 msec 85 msec
11 *
219.158.101.178 107 msec 107 msec
12 124.160.189.98 107 msec
124.160.189.90 111 msec 109 msec
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *

 

 

====================

 

So, the traffic from my home and Telstra looking glass are different, from AS4637 , I could not reach Chinese Router,  it went to US instead.....  There should something Telstra could do to help fix it !

 

7 18 ms 17 ms 18 ms unknown.telstraglobal.net [210.176.152.125]   <----AS4637
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 160 ms 160 ms 160 ms las-b23-link.ip.twelve99.net [213.248.92.106]

HOME ^^^^

 

6 i-90.hkhh11.telstraglobal.net (202.84.154.238) 80 msec 79 msec 79 msec     <------AS4637
7 219.158.40.233 80 msec 81 msec 79 msec

Telstra Looking glass 

 

=============================================

When I plug off NBN cable (FTTC), and use mobile backup

 

Status
IPv4 disconnected  IPv6 connected
Similar trace route below

Tracing route to 223.252.226.255 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms mymodem.modem [192.168.0.1]
2 <1 ms <1 ms <1 ms 192.0.0.1
3 * * * Request timed out.
4 22 ms 30 ms * 192.0.0.1
5 37 ms 34 ms 53 ms 192.0.0.1
6 28 ms 29 ms 29 ms 192.0.0.1
7 54 ms 26 ms 29 ms 192.0.0.1
8 30 ms 29 ms 29 ms Bundle-Ether27.win-edge903.melbourne.telstra.net [165.228.35.29]
9 35 ms 27 ms 30 ms bundle-ether13.win-core10.melbourne.telstra.net [203.50.11.194]
10 55 ms 41 ms 38 ms bundle-ether12.ken-core10.sydney.telstra.net [203.50.11.122]
11 63 ms 55 ms 42 ms bundle-ether1.pad-gw11.sydney.telstra.net [203.50.6.61]
12 48 ms 38 ms 31 ms unknown.telstraglobal.net [210.176.152.125]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 189 ms 187 ms 184 ms las-b23-link.ip.twelve99.net [213.248.92.106]
18 190 ms 189 ms 182 ms las-b22-link.ip.twelve99.net [62.115.143.39]
19 185 ms 181 ms 188 ms las-b24-link.ip.twelve99.net [62.115.125.163]
20 330 ms 335 ms 331 ms chinaunicom-ic155914-las-bb1.ip.twelve99-cust.net [213.248.82.206]
21 352 ms 343 ms 327 ms 219.158.96.25
22 352 ms 351 ms 379 ms 219.158.3.145
23 340 ms 337 ms 327 ms 219.158.5.145
24 349 ms 367 ms 346 ms 219.158.109.242
25 * * * Request timed out.
26 396 ms 372 ms 451 ms 124.160.189.34
27 344 ms 367 ms 365 ms 223.252.226.255

Mkrtich
Level 21: Augmented
Level 21: Augmented

Re: Why traffic to Chinese server need to go to US first (Hijacked by US?)

Thanks for your feedback. Will review tomorrow in further detail.

 

Just did a tracert from a test modem - I get the same result as you directly connected to the Internet and I am based in Brisbane - actually slightly worse. 

 

Tracing route to 223.252.226.255 over a maximum of 30 hops

1 8 ms 16 ms 14 ms 192.168.15.1
2 11 ms 10 ms 13 ms gateway.qb01.brisbane.asp.telstra.net [58.162.26.1]
3 12 ms 9 ms 9 ms ae10.woo-ice301.brisbane.telstra.net [203.50.61.17]
4 10 ms 12 ms 11 ms bundle-ether25.woo-core10.brisbane.telstra.net [203.50.61.16]
5 21 ms 21 ms 23 ms bundle-ether20.chw-core10.sydney.telstra.net [203.50.11.180]
6 22 ms 21 ms 24 ms bundle-ether1.oxf-gw11.sydney.telstra.net [203.50.6.93]
7 21 ms 28 ms 20 ms unknown.telstraglobal.net [210.176.152.137]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 162 ms 163 ms 162 ms las-b23-link.ip.twelve99.net [213.248.92.106]
12 162 ms 177 ms 163 ms las-b22-link.ip.twelve99.net [62.115.143.39]
13 163 ms 162 ms 161 ms las-b24-link.ip.twelve99.net [62.115.125.163]
14 333 ms 341 ms 338 ms 219.158.34.245
15 325 ms 321 ms * 219.158.96.25
16 355 ms 352 ms 351 ms 219.158.3.145
17 331 ms * * 219.158.18.65
18 367 ms * 387 ms 219.158.100.174
19 357 ms * * 124.160.189.110
20 * 390 ms 381 ms 223.252.226.255

Trace complete.

Mkrtich
Level 21: Augmented
Level 21: Augmented

Re: Why traffic to Chinese server need to go to US first (Hijacked by US?)

Hi - I am not familiar enough with routing data. Are the ping times are usually less than tracert times due to the additional identity information required that routers have to send back and forth for a tracert output. I got the same result as you did when using Telstra Looking Glass for a tracert - it stopped after the 11th entry, so I don't know if it is an issue with the Telstra tool, so I used another one to see if any difference.

 

1 i-90.sydp-core03.telstraglobal.net (202.84.222.81) 2 msec 0 msec 0 msec
2 i-90.sydp-core03.telstraglobal.net (202.84.222.81) [MPLS: Label 24060 Exp 0] 115 msec 116 msec 116 msec
3 202.84.138.90 116 msec 115 msec 116 msec
4 202.84.138.90 [MPLS: Label 24021 Exp 0] 117 msec 116 msec 117 msec
5 i-90.hkhh11.telstraglobal.net (202.84.154.238) 116 msec 116 msec 116 msec
6 219.158.40.233 118 msec 119 msec 119 msec
7 219.158.10.29 121 msec 125 msec 127 msec
8 219.158.96.210 124 msec 123 msec 127 msec
9 219.158.103.41 122 msec * 122 msec
10 219.158.114.246 143 msec
219.158.101.178 146 msec
219.158.114.246 144 msec
11 124.160.189.142 143 msec
124.160.189.94 149 msec
124.160.189.106 144 msec

 

In the above result, it was interesting to see a Telstra Router in Hong Kong being used for this test path which was not showing up in a ordinary CMD tracert path output, implying it is direct route?  For the CMD tracert, it appears to me that there are two sources of delay, one in the linkage from Los Angeles to Unicom and the second greater delay is within Unicom to Shanghai.

 

I used Hurricane Electric's, a US Network provider, web site for a Looking Glass probe test and got the same pattern. https://lg.he.net/  - select Looking Glass from left hand side margin then Sydney. It gave me two results, the first does a test from their Freemont 2 site in San Jose (faster) and the second from Sydney (slower). On both these probes, the significant delays come after packets reach the router in China. 

 

Irrespective of the milli seconds involved, I am old school and think its a miracle that information can travel that distance in under half a second. Is your concern about the time from a gaming application or another reason? 

 

LtYu
Level 2: Rookie

Re: Why traffic to Chinese server need to go to US first (Hijacked by US?)

Thank you very much for the reply.

 

Yes the latency is quite important when I play games with my friends in China,

I hope Telstra could fix it because its looking glass shows the possibility that the latency could be as low as ~150ms with a direct route.  It is anyway an issue when my local traceroute shows a big difference compare its looking glass.

 

===

From Hurricane Electric's, a US Network provider you used.

 

According to 

https://www.ipaddress.com/ipv4/72.52.93.38

https://www.ipaddress.com/ipv4/219.158.96.233

 

~24ms - ~39ms china169-backbone-as4837.100gigabitethernet12-2.core1.lax2.he.net (72.52.93.38)  <----- It is still 6939 (HURRICANE) in America

~179ms - ~243ms 219.158.96.233 <----------- This is 4837 (CHINA UNICOM China169 Backbone)

 

I think the ~150ms is the travel time from America to China, seems reasonable.

 

========

I am not a network engineer, it is difficult for me to argue with Telstra, and their online support team not quite sure about the traceroute/latency/traffic/peer stuff I was talking about.

 

I hope Telstra could use a direct route when connecting to Chinese servers because there is according to Telstra looking glass. As the biggest ISP in Australia, I believe Telstra is totally capable of it.

 

Thanks

 

 

Mkrtich
Level 21: Augmented
Level 21: Augmented

Re: Why traffic to Chinese server need to go to US first (Hijacked by US?)

Yes, it remains a puzzle. I assume given the country of origin, that the ASUS Router's enabled WTFast Gamers Private Network settings are doing the best they can for the registered games that WTF handle. Telstra's Gen 2 modem's optional Game Optimiser is based on the Duma OS - you may find some information on Crowd Support regarding how it handles connections to China - the Game Optimiser Product Support people actively participate in Crowd Support and are known to respond well to customer enquiries. 

LtYu
Level 2: Rookie

Re: Why traffic to Chinese server need to go to US first (Hijacked by US?)

Thanks,

 

WTFast sounds interesting, my Asus RT-AC86U supports WTFast stuff, let me try it and see.

 

Telstra Game Optimiser is $10 a month, what I don't understand is if this Game Optimiser thing can fix my traffic routing, then does that mean Telstra is asking for an extra $10 to provide the service then should already provide, Telstra is making my traffic diverted to the US intentionally in order to ask people pay it? 

 

When I sign with Telstra NBN (when NBN first time ready in my area), I did check the ping from Telstra Looking Glass, and I had raised this issue many times before via online chat. It misleads the public that especially I got ~350ms at home, but ~150ms from Telstra Looking Glass.

cf4
Level 25: The Singularity
Level 25: The Singularity

Re: Why traffic to Chinese server need to go to US first (Hijacked by US?)

Telstra game optimizer doesn't effect the route taken to the game server it only makes the modem connect to the game server with least latency and also prioritizes certain types of traffic, so I don't think it will fix the routing problem.

LtYu
Level 2: Rookie

Re: Why traffic to Chinese server need to go to US first (Hijacked by US?)

Thanks for your reply,

 

I hope I will get some feedback from Telstra Support Team next week.

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