For Tieba.baidu.com I am seeing something a bit different. I can get the contents of the page and it renders, but in a text only form. The stylesheets are *VERY* slow to load, if they even manage to do so along with the images on the site. tieba.baidu.com is running from Verizon Online to Verizon Business, to NTT Communications (routes from Los Angeles to Tokyo, Japan, then to Hong Kong), where it will hit the server. For all content associated to the Baidu page I'm back in the situation as I mentioned earlier. This is hitting a CDN which is causing me to route through China Telecom, where I'm hitting a lot of latency, and a lot of packet loss.
pan.baidu.com is the same case as above, as it is hosted on the same family of sites.
http://www.acfun.tv/ will not even get past the initial GET request. The connection stalls while attempting to get the initial portions of the page. In essence, I'm not even reaching the server. This is once again, hitting China Telecom. I can't tell what else is being requested on the page as I cannot get that far.
I can get portions of Sina to load up immediately here, as half of their site is hitting a CDN located in the United States. The other half of their site, including some scripts are once again, hitting the problem China Telecom paths. Since Sina owns the Chinese social network Weibo, I tested this site and did not run into any issues. Weibo is hitting some distant networks, but they are not hitting China telecom paths. The rest of the site is being served from a CDN in North America (note: I am redirected to us.weibo.com).
www.bilibili.tv is hitting a server located in a datacenter (Ubiquity Servers) in California, and does not touch any Chinese communications network for any of the proceeding GET requests for content. Pointing to bilibili.tv has some latency before it redirects to www.bilibili.tv as it is hitting a server which routes via China Telecom.
So the common problem is between China Telecom and Verizon. The two companies will need to work this issue out to find out where the breakdown is between the two providers.
Hopefully this will suffice:
WinMTR Statistics for pan.baidu.com
WinMTR statistics| Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
| 192.168.3.1 | 0 | 60 | 60 | 0 | 0 | 0 | 0 |
| 10.41.15.1 | 0 | 60 | 60 | 7 | 8 | 19 | 8 |
| P0-0-0-2.BFLONY-LCR-21.verizon-gni.net | 0 | 60 | 60 | 7 | 9 | 28 | 9 |
| xe-1-1-0-0.NWRK-BB-RTR1.verizon-gni.net | 0 | 60 | 60 | 19 | 36 | 121 | 23 |
| 0.xe-7-0-0.XL3.LAX1.ALTER.NET | 2 | 56 | 55 | 86 | 90 | 114 | 87 |
| 0.xe-10-1-0.GW2.LAX1.ALTER.NET | 2 | 56 | 55 | 86 | 90 | 144 | 86 |
| Internet-gw.customer.alter.net | 75 | 16 | 4 | 0 | 473 | 497 | 496 |
| 202.97.52.201 | 48 | 21 | 11 | 407 | 442 | 501 | 411 |
| 202.97.52.165 | 29 | 28 | 20 | 0 | 574 | 652 | 562 |
| 202.97.58.117 | 17 | 36 | 30 | 555 | 569 | 647 | 561 |
| 202.97.53.81 | 44 | 23 | 13 | 560 | 593 | 651 | 566 |
| 180.149.128.26 | 58 | 19 | 8 | 0 | 574 | 584 | 572 |
| 180.149.128.138 | 29 | 28 | 20 | 0 | 692 | 1104 | 560 |
| 180.149.129.54 | 35 | 26 | 17 | 561 | 568 | 648 | 648 |
| No response from host | 100 | 12 | 0 | 0 | 0 | 0 | 0 |
| No response from host | 100 | 12 | 0 | 0 | 0 | 0 | 0 |
| No response from host | 100 | 12 | 0 | 0 | 0 | 0 | 0 |
| 180.149.132.99 | 33 | 28 | 19 | 556 | 597 | 651 | 561 |
WinMTR Statistics for tieba.baidu.com
WinMTR statistics| Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
| 192.168.3.1 | 0 | 60 | 60 | 0 | 0 | 0 | 0 |
| 10.41.15.1 | 0 | 60 | 60 | 7 | 9 | 16 | 9 |
| P0-0-1-2.BFLONY-LCR-21.verizon-gni.net | 0 | 60 | 60 | 6 | 11 | 17 | 11 |
| xe-1-1-0-0.NWRK-BB-RTR1.verizon-gni.net | 0 | 60 | 60 | 18 | 38 | 108 | 96 |
| 0.xe-11-0-0.BR3.NYC4.ALTER.NET | 2 | 56 | 55 | 23 | 26 | 60 | 24 |
| xe-0-2-0-6.r06.nycmny01.us.bb.gin.ntt.net | 2 | 56 | 55 | 59 | 64 | 78 | 65 |
| ae-2.r22.nycmny01.us.bb.gin.ntt.net | 2 | 56 | 55 | 58 | 69 | 107 | 107 |
| ae-0.r23.nycmny01.us.bb.gin.ntt.net | 7 | 48 | 45 | 0 | 70 | 110 | 68 |
| ae-1.r20.asbnva02.us.bb.gin.ntt.net | 2 | 56 | 55 | 79 | 89 | 105 | 85 |
| ae-2.r21.lsanca03.us.bb.gin.ntt.net | 4 | 52 | 50 | 115 | 126 | 137 | 121 |
| ae-3.r21.tokyjp05.jp.bb.gin.ntt.net | 2 | 56 | 55 | 195 | 225 | 249 | 223 |
| ae-0.r25.tokyjp05.jp.bb.gin.ntt.net | 2 | 56 | 55 | 190 | 207 | 279 | 207 |
| ae-6.r22.tokyjp01.jp.bb.gin.ntt.net | 2 | 56 | 55 | 185 | 200 | 234 | 198 |
| p64-5-1-0.r21.tkokhk01.hk.bb.gin.ntt.net | 0 | 60 | 60 | 242 | 260 | 274 | 253 |
| as-5.r20.newthk02.hk.bb.gin.ntt.net | 0 | 60 | 60 | 251 | 266 | 290 | 263 |
| ae-1.r02.newthk02.hk.bb.gin.ntt.net | 2 | 56 | 55 | 240 | 253 | 272 | 249 |
| 203.131.246.146 | 0 | 60 | 60 | 260 | 274 | 390 | 267 |
| No response from host | 100 | 12 | 0 | 0 | 0 | 0 | 0 |
| 180.76.2.37 | 13 | 40 | 35 | 245 | 256 | 276 | 257 |
No need for me to post the other traces. The first one demonstrates the problem well enough.
