Issue #2379 resolved

cloudfront cdn report 48+% packet lost

沈 晟
created an issue

I noticed bitbucket start using cloudfront as a cdn solution. And I been having trouble since then.

Turn out couldfront been giving 48+% packet lost. So it is causing the web page can't fully loaded:

{{{ ping cdn.bitbucket.org -t Pinging d2aq0a746ftmav.nrt4.cloudfront.net [216.137.53.244] with 32 bytes of data: ... ... Ping statistics for 216.137.53.22: Packets: Sent = 587, Received = 302, Lost = 285 (48% loss), Approximate round trip times in milli-seconds: Minimum = 124ms, Maximum = 287ms, Average = 160ms }}}

I'm from Shanghai China

Comments (7)

  1. 沈 晟 reporter

    It seems to be a problem. I'm using China Telecom. When I connect cdn.bitbucket.org, i been redirect to d2aq0a746ftmav.nrt4.cloudfront.net [216.137.53.178]. which seems to be a one very bad connection.

    On the other client in China Netcom, When I connect cdn.bitbucket.org, i been redirect to 2aq0a746ftmav.sin2.cloudfront.net (204.246.165.140) . and it have no packet loss what so ever. ever from china telecom

  2. Erik van Zijst staff

    Routing between China Telecom and the various cloudfront servers is of course beyond our control and without a point of presence in Shanghai even impossible to diagnose.

    However, if you run a few traceroutes to the host that is most affected by it, it will probably reveal the router(s) that cause the bottleneck. If that is still on China Telecom's network, you should be able to take it up with them. If the bottleneck lies beyond that, they might still be able investigate it further.

    Cheers, Erik

  3. 沈 晟 reporter

    sure thing. I did few traceroute with -q 1, -q 10 and ping

    remark: latency is normal for us(china) as it bump to 200-400ms. packet lost isn't.

    traceroute  -q 10 cdn.bitbucket.org
    traceroute to cdn.bitbucket.org (216.137.53.27), 30 hops max, 40 byte packets
     1  192.168.10.1 (192.168.10.1)  0.404 ms  0.517 ms  0.638 ms  0.746 ms  0.855 ms  0.964 ms * * * *
     2  * * * 172.18.0.238 (172.18.0.238)  11.157 ms  11.394 ms  11.713 ms  2.108 ms  2.288 ms  2.628 ms  2.984 ms
     3  10.1.1.102 (10.1.1.102)  2.914 ms  3.058 ms  3.485 ms  3.544 ms  3.588 ms  3.505 ms  3.413 ms  3.499 ms  3.251 ms  3.671 ms
     4  10.1.1.253 (10.1.1.253)  1.596 ms  1.519 ms  1.523 ms  1.896 ms  1.853 ms  1.956 ms  1.953 ms  1.573 ms  1.561 ms  1.541 ms
     5  10.1.1.254 (10.1.1.254)  1.773 ms  1.747 ms  1.393 ms  1.388 ms  1.915 ms  1.907 ms  1.954 ms  2.361 ms  2.368 ms  1.703 ms
     6  10.1.1.2 (10.1.1.2)  1.775 ms  1.714 ms  1.765 ms  2.178 ms  2.129 ms  2.133 ms  2.191 ms  2.165 ms  2.544 ms  2.541 ms
     7  10.1.0.245 (10.1.0.245)  4.107 ms  3.998 ms  2.785 ms  3.195 ms  3.225 ms  2.749 ms * * * *
     8  61.87.251.14 (61.87.251.14)  2.158 ms  2.250 ms  2.665 ms  2.179 ms  2.182 ms  2.021 ms  1.873 ms  2.682 ms  2.633 ms  2.458 ms
     9  202.158.160.117 (202.158.160.117)  2.679 ms  2.677 ms  2.518 ms  2.414 ms  2.251 ms  2.502 ms  2.493 ms  2.688 ms  4.757 ms  4.690 ms
    10  202.158.160.53 (202.158.160.53)  6.992 ms  6.995 ms  5.883 ms  6.503 ms  7.750 ms  3.935 ms  3.917 ms  3.908 ms  2.515 ms  2.328 ms
    11  58.246.1.229 (58.246.1.229)  4.897 ms  5.032 ms  5.357 ms  5.096 ms  5.110 ms  5.776 ms  5.696 ms  5.480 ms  5.095 ms  5.858 ms
    12  58.247.220.45 (58.247.220.45)  42.856 ms  42.821 ms * * 58.247.220.45 (58.247.220.45)  40.399 ms  198.869 ms  198.863 ms * 58.247.220.45 (58.247.220.45)  29.883 ms  29.874 ms
    13  112.64.243.185 (112.64.243.185)  4.274 ms  5.098 ms  4.120 ms  4.002 ms  3.177 ms  4.702 ms  3.890 ms  3.068 ms  4.070 ms  4.045 ms
    14  112.64.243.85 (112.64.243.85)  4.443 ms  4.183 ms * 112.64.243.85 (112.64.243.85)  4.125 ms  5.132 ms  4.199 ms  5.477 ms  4.119 ms  4.285 ms  4.836 ms
    15  219.158.9.209 (219.158.9.209)  6.264 ms  5.278 ms  5.537 ms  4.940 ms  4.843 ms  3.585 ms  4.685 ms  4.268 ms  4.416 ms  4.215 ms
    16  219.158.5.122 (219.158.5.122)  123.126 ms  122.064 ms * 219.158.5.122 (219.158.5.122)   * 219.158.5.122 (219.158.5.122)  134.160 msms  134.176 ms
    17  219.158.33.154 (219.158.33.154)  325.422 ms * 219.158.33.154 (219.158.33.154)  325.421 ms  325.434 ms  325.481 ms  325.558 ms  326.464 ms  326.467 ms  325.580 ms  326.494 ms
    18  ae-1.r21.tokyjp01.jp.bb.gin.ntt.net (129.250.5.150)  309.010 ms  296.425 ms  296.190 ms  296.329 ms  296.237 ms  296.615 ms  297.199 ms  296.587 ms  296.713 ms  297.168 ms
    19  * * * * * * * * * *
    20  * * * * * * * * * *
    21  * * * * * * * * * *
    22  27.0.0.148 (27.0.0.148)  320.494 ms  320.446 ms 27.0.0.156 (27.0.0.156)  309.880 ms 27.0.0.148 (27.0.0.148)  320.477 ms 27.0.0.156 (27.0.0.156)  310.273 ms 27.0.0.148 (27.0.0.148)  320.546 ms 27.0.0.162 (27.0.0.162)  321.226 ms  321.255 ms 27.0.0.156 (27.0.0.156)  310.541 ms  310.594 ms
    23  27.0.0.148 (27.0.0.148)  319.249 ms !X 27.0.0.156 (27.0.0.156)  308.196 ms !X * * * * 27.0.0.162 (27.0.0.162)  323.241 ms !X * * 27.0.0.148 (27.0.0.148)  324.850 ms !X
    the jump list ends here, maybe blocked by router as it send too much icmp packet?
    

    It appear that the packet is lost between NTT America, Inc. 129.250.0.0 - 129.250.255.255 .

  4. Log in to comment