I just switched over to Telstra NBN (FTTB) today, and noticed that there seems to be high latency/packet loss when routing to Chinese addresses:
------------------------------------------------------------------------------------
C:\Windows\System32>tracert cctv.cn
Tracing route to cctv.cn [202.108.8.82]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dsldevice.gateway [10.0.0.138]
2 12 ms 7 ms 6 ms 58.162.26.194
3 8 ms 8 ms 7 ms 144.130.210.210
4 8 ms 10 ms 9 ms bundle-ether11.exi-core10.melbourne.telstra.net
[203.50.11.113]
5 23 ms 24 ms 25 ms bundle-ether12.chw-core10.sydney.telstra.net [20
3.50.11.124]
6 22 ms 24 ms 22 ms bundle-ether1.oxf-gw11.sydney.telstra.net [203.5
0.6.93]
7 23 ms 23 ms 24 ms bundle-ether1.sydo-core03.sydney.reach.com [203.
50.13.98]
8 138 ms 139 ms 138 ms i-0-4-2-0.hkth-core01.bx.telstraglobal.net [202.
84.144.85]
9 137 ms 137 ms 138 ms i-0-1-1-0.hkhh11.bi.telstraglobal.net [202.84.15
4.42]
10 602 ms 600 ms * 219.158.40.233
11 515 ms 516 ms 515 ms 219.158.25.141
12 603 ms 605 ms 601 ms 219.158.19.193
13 577 ms 583 ms * 219.158.23.13
14 * 648 ms 664 ms 219.158.6.109
15 * 662 ms 658 ms 124.65.194.102
16 664 ms 660 ms 656 ms 61.148.143.18
17 * 620 ms 612 ms 61.49.42.130
18 681 ms 687 ms 704 ms zz-8-82-a8.bta.net.cn [202.108.8.82]
Trace complete.
------------------------------------------------------------------------------------
For some reason there's a massive spike at hop 10 (219.158.40.233) – this happens consistently no matter what website I tracert on. However when using the Telstra looking glass here, it seems to be fine:
------------------------------------------------------------------------------------
1 gigabitethernet3-3.exi1.melbourne.telstra.net (203.50.77.49) 0.273 ms 0.280 ms 0.225 ms
2 bundle-ether3-100.exi-core10.melbourne.telstra.net (203.50.80.1) 2.089 ms 3.124 ms 1.835 ms
3 bundle-ether12.chw-core10.sydney.telstra.net (203.50.11.124) 16.954 ms 16.168 ms 17.106 ms
4 bundle-ether1.oxf-gw11.sydney.telstra.net (203.50.6.93) 15.360 ms 16.446 ms 17.032 ms
5 bundle-ether1.sydo-core03.sydney.reach.com (203.50.13.98) 17.607 ms 16.039 ms 17.483 ms
6 i-0-2-0-4.hkth-core01.bx.telstraglobal.net (202.84.141.133) 132.664 ms 131.518 ms
7 i-0-1-1-0.hkhh11.bi.telstraglobal.net (202.84.154.42) 129.446 ms
8 219.158.40.233 (219.158.40.233) 237.855 ms 235.037 ms 235.983 ms
9 219.158.25.141 (219.158.25.141) 297.566 ms 297.249 ms 305.688 ms
10 219.158.97.25 (219.158.97.25) 235.229 ms 234.661 ms 234.980 ms
11 219.158.11.161 (219.158.11.161) 307.940 ms 312.740 ms 305.189 ms
12 219.158.8.81 (219.158.8.81) 415.998 ms 426.419 ms 455.110 ms
13 124.65.194.102 (124.65.194.102) 388.757 ms 397.308 ms 406.758 ms
14 61.148.143.18 (61.148.143.18) 415.117 ms 428.799 ms 413.008 ms
15 61.49.42.130 (61.49.42.130) 407.365 ms
------------------------------------------------------------------------------------
I don't know much about networking, but this seems strange to me. Any ideas what the issue could be? It's causing a lot of issues with streaming sites that fail to load videos and continuously buffer.