Ouch, but maybe solvable... Confirmed from Beijing. Thought it was the internet connectivity in the office that failed, but same at home. Did a traceroute and

Ouch, but maybe solvable... Confirmed from Beijing. Thought it was the internet connectivity in the office that failed, but same at home. Did a traceroute and this reveals an expected result. It is really the DNS which returns a wrong value '59.24.3.173' instead of the expected '207.97.227.239', so it looks like a dns poisoning attempt or some other dns issue. Editing your /etc/hosts file or using opendns can help in this case. traceroute to github.com (207.97.227.239), 30 hops max, 60 byte packets 1 10.0.21.1 (10.0.21.1) 1.987 ms 2.265 ms 2.832 ms 2 123.121.64.1 (123.121.64.1) 35.160 ms 35.416 ms 35.675 ms 3 61.148.185.249 (61.148.185.249) 20.185 ms 22.808 ms 24.970 ms 4 124.65.61.173 (124.65.61.173) 33.900 ms 33.950 ms 34.056 ms 5 * * * 6 219.158.101.122 (219.158.101.122) 71.221 ms 48.915 ms 50.631 ms 7 219.158.23.6 (219.158.23.6) 70.620 ms 72.682 ms 95.149 ms 8 219.158.96.202 (219.158.96.202) 88.623 ms 90.785 ms 93.630 ms 9 219.158.29.170 (219.158.29.170) 267.972 ms 276.896 ms 277.973 ms 10 219.158.32.10 (219.158.32.10) 265.656 ms 269.840 ms 210.408 ms 11 * * * 12 67.133.246.158 (67.133.246.158) 286.678 ms 288.514 ms 291.715 ms 13 vlan905.core5.iad2.rackspace.net (72.4.122.10) 303.488 ms 307.324 ms 305.763 ms 14 aggr301a-1-core5.iad2.rackspace.net (72.4.122.121) 311.652 ms 314.041 ms 317.400 ms 15 github.com (207.97.227.239) 315.588 ms 317.580 ms 320.812 ms So with OpenDNS it loads... still some packetloss, but this is expected. In the worst case, use a VPN. Although, this means it will trouble Chinese participation and contributions to projects even more.