A quick look at our web-analytics further revealed a bump in people searching Google for “thepiratebay down”.

The majority of these people showed up as Comcast subscribers, which led us to conclude that something is up with the connection between The Pirate Bay and the Comcast network.

This morning we wrote an article on the issue, mentioning that The Pirate Bay was trying to find the origin of the problem.

The report didn’t go unnoticed by Comcast either. In a response to the issue Jason Livingood, Executive Director Internet Systems Engineering at Comcast, told TorrentFreak: “Please note that we do not block websites and we are NOT blocking The Pirate Bay.”

As stated in the original article, we never suspected an intentional blockade, but something was clearly wrong. Luckily, Comcast is there to help The Pirate Bay get back on track.

Comcast has reached out to The Pirate Bay and set aside resources in case the BitTorrent site needs it. “I can have our engineers work directly with them to assist,” Jason Livingood told TorrentFreak.

Initially The Pirate Bay team suspected that Comcast might be filtering PMTU responses, but Comcast looked into this and ruled it out. At the moment The Pirate Bay team is looking at other possibilities, but Comcast is confident that they’re not causing the problem.

The Pirate Bay team prefers to keep the exact location of their core hardware somewhat of a mystery, and some of this network magic may conflict with Comcast at the moment. It’s expected that, with or without help from Comcast, the issues will be resolved soon.

Update: Right before we finished this article, Comcast users were able to connect to The Pirate Bay again. The issue was reverse path filtering in a Tier1 network Comcast traffic went through.

Comcast reached out to Serious Tubes Networks, who deliver transit to The Pirate Bay, and they were able to correct the issue.

“Comcast emailed our NOC about their users complaining about not reaching The Pirate Bay. We resolved the issue and TPB can now be reached from ComCast,” the CEO of Serious Tubes Networks told TorrentFreak.

Indeed, Comcast Cares, but the problem was fixed without their direct help.

Source: Comcast Offers Help to The Pirate Bay, Problems Fixed

Although downtime is nothing new for users of the popular BitTorrent site, this time around the connectivity issues appear to be affecting only a select group.

Several tests and numerous user reports reveal that Comcast subscribers from all across the United States are unable to connect to The Pirate Bay. The traceroute from Comcast connections stops at thepiratebay.piratpartiet.se, as it’s supposed to, but The Pirate Bay website does not appear.

Further tests show that the blockade is not DNS related. What is actually causing the issue is uncertain at this point.

Although there’s been a lot of talk about censorship lately, it seems doubtful that this is an intentional blockade on Comcast’s part. That said, there is clearly a mismatch between the Comcast network and The Pirate Bay site which leaves access to the rest of the Internet unaffected.

TorrentFreak spoke to The Pirate Bay team who confirmed that there’s a significant drop in visitors from the U.S. They are currently investigating the issue to see if there’s anything they can do on their end.

When it comes to BitTorrent blocking, Comcast already has quite a reputation. In 2007 TorrentFreak broke the news that Comcast was actively blocking BitTorrent traffic. Comcast initially denied, but later admitted its wrongdoings.

Comcast’s BitTorrent blocking fueled the Net Neutrality debates and eventually resulted in an FCC investigation and various lawsuits. A class action lawsuit was settled by the ISP who reserved a $16 million fund for affected subscribers.

In the light of all the previous legal issues it therefore seems unlikely that Comcast has ventured out on its own to block The Pirate Bay website.

When there’s more information available on the current issues we’ll update this article. In the meantime Comcast users can access the site through Anonymouse and other proxies.

Update: It appears that a subset of Rogers users in Canada have problems accessing the site as well, same with some Optus users in Australia. However, this doesn’t appear to be as widespread as with Comcast.

Update: Jason Livingood, Executive Director Internet Systems Engineering at Comcast told TorrentFreak: “Please note that we do not block websites and we are NOT blocking The Pirate Bay.”

Update: After affecting only Comcast users for about 15 hours, The Pirate Bay seems to be inaccessible pretty much everywhere now. The Pirate Bay team is looking into it. (Update: one webserver died, should be back for most people who are not on Comcast now).

Source: Comcast Users Blocked From The Pirate Bay

The whole Comcast debacle ignited a discussion about Net Neutrality and eventually led to the FCC’s national broadband plan which was released last month. Today, the Court of Appeals overruled FCC’s decision in the Comcast case, with three judges stating that the commission doesn’t have the authority to require ISPs to keep their network neutral.

After appealing FCC’s decision in favor of BitTorrent users, Comcast has finally got the verdict (pdf) it wanted. Although it seems unlikely that the ISP will pick up its old habit of preventing BitTorrent users to seed files, it could in theory do so.

The Court of Appeals ruling states that the FCC did not have the power to regulate ISPs network managing practices, which leaves the commission with two options. It could appeal at the Supreme Court, or it could ask Congress to give it the powers it wants and/or needs.

The latter option will pose potential problems for the likes of Comcast, with the FCC potentially asking not only for powers to deal with this particular case, but for greatly increased powers to regulate the entire sector.

For BitTorrent users on Comcast and other US Internet providers there are uncertain times ahead.

Article from: TorrentFreak.

It therefore came as a surprise when we found out that three major US ISPs – Comcast, Cox and Warner Cable – have been funding research which aims to help copyright holders track down and gather evidence against BitTorrent pirates more efficiently.

Unlike most of the ‘passive’ BitTorrent tracking tools that are in fashion today, BitStalker uses an ‘active’ method through which they can actually prove that the BitTorrent client associated with an IP-address is sharing files. Where the passive methods wrongfully accuse 1 in 10 downloaders, BitStalker promises to avoid such false positives.

The researchers who developed BitStalker further claim (pdf) that their tool is much more effective than the current competition, as it would allow copyright holders to get information on 20 million BitTorrent users for a bargain price of $12.40. What remains unclear, however, is why three large ISPs are interested in funding this project.

It is no secret that the RIAA has been pushing Comcast, Cox and other ISPs to take stricter measures against copyright infringers, including the ultimate sanction of terminating customers’ Internet access. However, thus far the ISPs have largely maintained their neutral position as information carriers.

Whether the funding of BitStalker’s research is a signal that this may change is open for speculation. Another argument for ISPs to join could be that they want to protect their customers from receiving copyright infringement notices in error.

Regarding the BitStalker method of tracking BitTorrent users, we can say that it is not as revolutionary as the researchers portray it. TorrentFreak spoke to several people who are currently operating the largest BitTorrent trackers on the Internet and none of them was impressed by BitStalker’s technology.

If BitStalker is indeed implemented the large scale monitoring will have to be executed from thousands of IP-addresses. Most trackers have rules in place so that one single IP-address will be banned from the tracker if it connects to too many torrents.

Similarly, if BitStalker was put on a cloud service like the research suggests, it wouldn’t take long before these IP-ranges would appear in block-lists, rendering BitStalker useless.

If we add to this that BitStalker’s active BitTorrent tracking method will require users to be ‘connectible’, which a large percentage of users aren’t, this means that it will result in many false negatives. The researchers report that they could only connect to less than half of all available peers, which might be caused in the main by the connectability issue.

Whatever the motivations are for Comcast and the other ISPs to fund this project, the good news is that less people will be accused of uploading something they haven’t. Whether BitStalker will really be that more efficient depends on one’s definition of efficiency. For now, we doubt that it will result in a global BitTorrent crackdown.

Article from: TorrentFreak.

Their decision to prevent BitTorrent users from sharing content over their network has sparked the Net Neutrality debate, resulting in an FCC investigation and various lawsuits. One of these suits was settled last month.

Comcast agreed to put $16m into a fund to pay BitTorrent users that were affected by the ‘network management’ which made it impossible for them to share files after their downloads had completed.

Each of the affected users can now claim their $16 in damages, but those who do are required to state to the Court, under penalty of perjury, that their use of BitTorrent “was for lawful purpose consistent with applicable copyright and other laws.” This required statement came as an unpleasant surprise to many affected Comcast users.

“Am I supposed to be able to remember everything I downloaded during that period, and be cognizant of the copyright status of those items not only then, but now?” one worried Comcast user told TorrentFreak. “I certainly do not think that sixteen dollars is enough incentive to possibly suffer the penalties of committing unwitting federal perjury.”

Other Comcast users will have to agree with this assessment, simply because it is often not clear when one is violating copyright law. For example, there is still a large portion of BitTorrent users who think that downloading a TV-show that they could have watched for free on TV, is not a crime.

It wouldn’t surprise us if a large portion of the $16 million fund is left unclaimed because of this required statement, saving Comcast a significant amount of money.

That leads us to the question why was included in the first place. It somehow suggests that Comcast was attempting to stop copyright infringement with their throttling practices, aside from the network management purpose it served. Maybe they just want to hang on to their money.

Whatever the motivation to include this option, it is completely irrelevant to the case itself. Comcast has never used copyright infringement as a justification for stopping BitTorrent traffic, so the lawfulness of the traffic should not be an issue.

Article from: TorrentFreak, check out our new blog at FreakBits.

In one of the class action suits that were brought about from the long-running incident, Comcast has now agreed to settle, meaning those affected may be eligible for compensation.

About two and a half years ago, reports surfaced on what appeared to be the throttling of BitTorrent connections by Comcast. The throttling, first discovered by Rob Toplowski, was confirmed by TorrentFreak, and was first reported in August 2007. Other news agencies picked it up later, especially after tests by the EFF and Associated Press confirmed events and included reports that other network based activity was also affected.

Comcast long-denied any wrongdoing, but a leaked memo revealed that the company went as far as instructing its front-line staff to lie about the issue. Then the FCC got involved and things deteriorated. At a hearing at Harvard, Comcast packed the venue with people they bussed in, but it didn’t stop the BitTorrent throttling practice being termed a ‘hacker technique’.

Eventually, some assurances were made, and the FCC ordered Comcast to stop using Sandvine. Meanwhile lawsuits had been filed. One of these, Hart vs Comcast of Alameda, attained class action status, and there is now a proposed settlement.

Comcast has agreed to put $16M into a fund to pay BitTorrent users that were inconvenienced by the ‘network management’.

The downside is the size of the settlement. If you qualify, you can receive a maximum of $16, yet still Comcast refuses to accept it did anything wrong. The administrators of the settlement have set up a website to deal with questions about the case which can be found at www.p2pcongestionsettlement.com

It’s not hard to imagine that some customers will feel this doesn’t go far enough, and undoubtedly the discussion on this topic will continue. For the affected Comcast users there is still time to decide how to proceed – the deadline for claims is August 14th 2010. Meanwhile, network neutrality remains a pipe dream for most people.

Article from: TorrentFreak, check out our new blog at FreakBits.