Live data from Hacker News

Some Users Unable to Reach The Pirate Bay

torrentfreak.com

21–30 of 56 posts

Re: Some Users Unable to Reach The Pirate Bay

#22

I'm on AT&T and it's not loading for me, right now.

Maybe we were too quick to place blame on Comcast/Xfinity? Then again they could have a peering agreement with at&t? Chicago nap is run by ameritech, MAE east no idea, NY nap is sprint, SF nap pac bell, but who runs MAE west? Curiouser and curiouser.

Still working on Speakeasy and a local open wi-fi that seems to be on Verizon on my end.

Re: Some Users Unable to Reach The Pirate Bay

#24
post #5
post #2

I'm on Comcast, so I can confirm that not even a ping is getting through. And I'm using OpenDNS, so it's not DNS-level blocking. But after the mess Comcast has been in for this stuff before, I kind of can't believe they'd try it again. I'm in a chat with a Comcast rep now, who claims that if they were blocking the page there would be a branded error message. There's just nothing. Maybe (hopefully!) this isn't what it…

thepiratebay.org doesn't respond to pings from any network as far as I can tell, which is a typical firewall configuration. Judging by the comments on the article it's not Comcast blocking, but some kind of network configuration issue, as multiple ISPs are impacted (though they could in theory be using Comcast as a carrier).

I'm on Rogers in Canada and I can't get through either.

Re: Some Users Unable to Reach The Pirate Bay

#27
post #2

I'm on Comcast, so I can confirm that not even a ping is getting through. And I'm using OpenDNS, so it's not DNS-level blocking. But after the mess Comcast has been in for this stuff before, I kind of can't believe they'd try it again. I'm in a chat with a Comcast rep now, who claims that if they were blocking the page there would be a branded error message. There's just nothing. Maybe (hopefully!) this isn't what it…

Confirmed no access at 06:51 PDT, but was able to get through via a proxy server.

By the way – the web experience is just that the page hangs. There's no 404, or 'server can't connect' or any other warning message. This type block is indicative of someone throttling the connection to the server. Likely Comcast hasn't outright blocked the site, they've just made the pipe so small that no one can get to it.

Re: Some Users Unable to Reach The Pirate Bay

#28
I guess its been established that this is not a DNS issue. But I just wanted to point out that using Speakesy, no matter what DNS I use, speakeasy's own or OpenDNS, I CAN reach TPB.

I'm not entirely sure if this makes a difference. I just wanted to add that information since I had not mentioned it before. This information may or may not be helpful. In case it is, here it is.

Re: Some Users Unable to Reach The Pirate Bay

#29
post #28

I guess its been established that this is not a DNS issue. But I just wanted to point out that using Speakesy, no matter what DNS I use, speakeasy's own or OpenDNS, I CAN reach TPB. I'm not entirely sure if this makes a difference. I just wanted to add that information since I had not mentioned it before. This information may or may not be helpful. In case it is, here it is.

Same here. I'm on Comcast and I use OpenDNS and TPB is not reachable. While I've had my issues with Comcast, I've been more or less happy with them ever since I switched to their business class service (faster speeds and no hard set bandwidth limits for them to complain to me over). If they're blocking TPB, they're blocking other things. I don't want my utility service to block how I use the utility.

Re: Some Users Unable to Reach The Pirate Bay

#30

I'm on Comcast and also can't access TPB. Doing a tracert, the packets are lost in inside of TPB network. Thepiratebay.piratpartiet.se is as far as I can reach.

How do you know that Comcast isn't just allowing ICMP and blocking TCP?

If they're intentionally blocking TPB traceroute data cannot be trusted.

Post reply on HN