Slashdot Mirror

← Back to Stories (view on slashdot.org)

CloudFlare Puts Pirate Sites on New IP Addresses, Avoids Cogent Blockade (torrentfreak.com)

Posted by msmash on from the fighting-back dept.

Earlier this month, several users worldwide reported that they were unable to access pirate websites including the Pirate Bay. It was because the internet backbone network of Cogent Communications had blackholed the CloudFlare IP-address of pirate websites. Less than a week later, CloudFlare is fighting back. From a report on TorrentFreak: The Pirate Bay and dozens of other pirate sites that were blocked by Cogent's Internet backbone are now accessible again. CloudFlare appears to have moved the sites in question to a new pair of IP-addresses, effectively bypassing Cogent's blackhole. [...] As of yesterday, the sites in question have been assigned the IP-addresses 104.31.16.3 and 104.31.17.3, still grouped together. Most, if not all of the sites, are blocked by court order in the UK so this is presumably done to prevent ISP overblocking of 'regular' CloudFlare subscribers.

4 of 88 comments (clear)

  1. Re:For their next trick... by DontBeAMoran · · Score: 4, Insightful

    Redirect all UK government websites to this address instead.

    --
    #DeleteFacebook
  2. Someone Revoke Cogent's Common Carrier Status by Anonymous Coward · · Score: 1, Insightful

    Fuck those greedy nI-ggers

  3. Re:The solution is unfortunately national segregat by torkus · · Score: 4, Insightful

    Not true.

    It's a game of diminishing returns but there's never an absolute winner.

    You can make it nearly impossible to circumvent, and then someone can build a complex circumvention...and so on. Remember when 'hacking' was dumping the plaintext password database after booting off a floppy?

    You can make censorship difficult enough to circumvent that people will find something else to do...but the cost (implementation and maint) in that is very high.

    --
    You can get rich if you own a politician, but you have to be rich to buy one in the first place.
  4. Re: For their next trick... by gnick · · Score: 3, Insightful

    You did say URI. You could have said URL. It was, after all, a URL. This page gives a good description of the difference as well as a guide for responding to the statement, "Actually, that’s called a URI, not a URL"

    The response to this correction can range from quietly thinking this person needs to get out more, to agreeing indifferently via shoulder shrug, to removing the safety clasp on a Katana.

    --
    He's getting rather old, but he's a good mouse.