After doing a traceroute, the traffic goes to Los Angeles and then back to China.
And?
Don't mean to be blunt, but you aren't saying where you are tracing from, or providing more info like a traceroute, or if this is even a problem instead of an observation.
Quote
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Windows\system32>tracert -w 100 www.qq.com
Tracing route to www.qq.com [240e:e1:8100:28::2:16]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms xxxxx.net [2001:470:xxxx:1::1]
2 * * * Request timed out.
3 124 ms 97 ms 89 ms ge3-13.core1.hkg1.he.net [2001:470:0:ba::1]
4 196 ms * 69 ms 10ge3-1.core1.tyo1.he.net [2001:470:0:26a::1]
5 258 ms 226 ms * 10ge1-13.core1.lax2.he.net [2001:470:0:294::1]
6 * * * Request timed out.
7 348 ms * 323 ms 2001:252:0:302::1
8 406 ms * * 2001:252:0:100::1
9 407 ms * 381 ms 2001:252:0:1::2
10 368 ms * 363 ms 2001:c68::1
11 481 ms * * 2001:c68:0:1200::1
12 * * 442 ms 2001:c68:0:1000::2
13 * * * Request timed out.
14 462 ms * 422 ms 240e:18:1:3010::89
15 * * * Request timed out.
16 * 428 ms * 240e:18:10:a02::2
17 429 ms * 415 ms 240e:18:10:2103::2
18 437 ms * * 240e:e1:813f::2
19 * 460 ms * 240e:e1:813f::e
20 * * * Request timed out.
21 465 ms * * 240e:e1:8100:28::2:16
22 475 ms * * 240e:e1:8100:28::2:16
23 457 ms * 460 ms 240e:e1:8100:28::2:16
Trace complete.
C:\Windows\system32>tracert -w 1000 www.cnnic.cn
Tracing route to www.cnnic.cn [2001:dc7:dd01:0:218:241:97:42]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms xxxxx.net [2001:470:xxxx:1::1]
2 * * * Request timed out.
3 115 ms 118 ms 145 ms ge3-13.core1.hkg1.he.net [2001:470:0:ba::1]
4 236 ms 194 ms 188 ms 10ge3-1.core1.tyo1.he.net [2001:470:0:26a::1]
5 332 ms 294 ms 240 ms 10ge1-13.core1.lax2.he.net [2001:470:0:294::1]
6 * * * Request timed out.
7 382 ms 397 ms 399 ms 2001:252:0:302::1
8 * * * Request timed out.
9 415 ms 365 ms 361 ms 2001:252:0:1::2001
10 401 ms 372 ms 353 ms 2400:dd00:0:2::130
11 371 ms 392 ms 370 ms 2400:dd00:0:4::205
12 372 ms 336 ms 348 ms 2400:dd00:1:1012::4
13 379 ms 373 ms 430 ms 2001:dc7:ddff::106
14 * 420 ms 394 ms 2001:dc7:dd01:0:218:241:97:42
Trace complete.
C:\Windows\system32>
From Hong Kong.
Simple, HE doesn't peer with them directly in HKG. They learn their routes up in LAX. Maybe they aren't at a mutual peering location in HKG.
Quote from: broquea on June 18, 2015, 08:56:25 AM
Simple, HE doesn't peer with them directly in HKG. They learn their routes up in LAX. Maybe they aren't at a mutual peering location in HKG.
So should I get IPv6 connectivity from a domestic ISP instead of HE?
One should always strive to get native IPv6 from whomever. Tunnels are a quick fix to get you on and using it.
Quote from: broquea on June 18, 2015, 09:05:40 AM
One should always strive to get native IPv6 from whomever. Tunnels are a quick fix to get you on and using it.
But this problem should also occur on others using HE.NET's transit?
If you are using a HK based tunnel to compare, then probably? You could always go try testing on http://lg.he.net
Quote from: broquea on June 18, 2015, 09:19:30 AM
If you are using a HK based tunnel to compare, then probably? You could always go try testing on http://lg.he.net
Same problem on IPv4, but I think domestic ISPs have direct transit lines to China, and IPv6 is not yet very common in China.