Another blocking of some GitHub IP addresses

    Yesterday and today, part of the IT population of our country (Russia) encountered an unexpected problem when trying to log in to GitHub, for example, to read pull-request or documentation for some library. The site was stupid for a long time, after which it loaded without styles, pictures and scripts.



    I was among this part of the population. The situation seemed familiar. Indeed, by going to the browser console, I found that all the static fell off by timeout. Ok Let's see where assets-cdn.github.com leads to:

    $ host assets-cdn.github.com
    assets-cdn.github.com is an alias for github.map.fastly.net.
    github.map.fastly.net is an alias for prod.github.map.fastlylb.net.
    prod.github.map.fastlylb.net has address 151.101.36.133
    

    OK. Let's see if this IP address is in a single registry ?



    Yes, it seems to have been introduced!

    The website of the Universal Service for checking restrictions on access to sites tells us the same thing .



    Wait a minute, June 10, 2013? What, the court decision was awaiting execution for 3 years? 0_o

    The Roskomsvoboda registry says yes:



    A little googling on this issue (and surprised that nothing had surfaced on the habraresources), I found an entry in LiveJournal with some additional details:
    Apparently, some online casino used the same CDN in 2013, and our Roskomsenzura back in 2013 decided to block not the hosts of the online casino, but with a stroke of the pen the IPv4 address of the entire CDN data center. D ..., b ...! That is, the government saved us from the fact that we did not lose the last money in the casino, at the same time blocking the unnecessary GitHub from its spiritually secure point of view.

    It turns out that GitHub is blocked throughout Russia by the Oktyabrsky District Court of Stavropol. District Court, Karl! It turns out that absolutely any district judge from any subject of the Russian Federation can now block any site throughout the Russian Federation on the DPI equipment of providers.

    Another small discussion on the VK-page of Roskomsvoboda was googled , from which you can, in particular, get to the text of the court’s decision and the page of the judge who issued it (“Very competent, considerate and friendly, WITH A THIN FEATURE OF HUMOR”).

    In the bowels of the comments to the above LJ post you can also find a solution to this problem (well, except for the obvious ones - use a proxy or ssh tunnel): Github CDNs also have an IP address 151.101.12.133 , which is not entered in the registry. Thus, you can register it in / etc / hosts and enjoy life. Well ... Only on the same CDN are avatars with different domain names distributed, and, in the very setup, someGitHub Pages At the time of this writing, my / etc / hosts were:

    151.101.12.133  assets-cdn.github.com
    151.101.12.133  avatars2.githubusercontent.com
    151.101.12.133  avatars0.githubusercontent.com
    151.101.12.133  avatars1.githubusercontent.com
    151.101.12.133  avatars3.githubusercontent.com
    151.101.12.133  google.github.io
    151.101.12.133  kangax.github.io
    151.101.12.133  eslint.org
    

    Probably, you still have to enable VPN ...

    UPD 07/13/2016:
    It looks like IP was deleted from the registry on 07/12/2016 . So Roskomnadzor, we must give them their due, not so slow.

    Only registered users can participate in the survey. Please come in.

    And you’ve been affected by _This_ GitHub lock

    • 53% yes 470
    • 46.9% no 416

    Also popular now: