Anybody on this list have any insights on the reports of Pirate Bay
unreachability?
http://torrentfreak.com/comcast-blocked-the-pirate-bay-110512/
http://www.fastcompany.com/1752986/why-is-comcast-blocking-the-pirate-bay
http://www.engadget.com/2011/05/12/is-comcast-blocking-the-pirate-bay/
Comcast customer care via twitter specifically stated they aren't blocking
twitter (@comcastcares).
On May 12, 2011 12:00 PM, Steve Schultze s...@princeton.edu wrote:
Anybody on this list have any insights on the reports of Pirate Bay
unreachability?
2nd Twitter instance should've read The Pirate Bay. Apologies.
On May 12, 2011 12:03 PM, Brandon Galbraith brandon.galbra...@gmail.com
wrote:
Comcast customer care via twitter specifically stated they aren't blocking
twitter (@comcastcares).
On May 12, 2011 12:00 PM, Steve Schultze
FWIW, most speculation can be eliminated with a simple traceroute:
6 te-0-2-0-0-cr01.miami.fl.ibone.comcast.net (68.86.93.149) 83.161
ms 25.235 ms 22.264 ms
7 xe-10-1-0.edge2.Miami1.Level3.net (64.156.8.9) 25.455 ms 31.254
ms 39.878 ms
8 ae-31-51.ebr1.Miami1.Level3.net (4.69.138.94)
Anybody on this list have any insights on the reports of Pirate Bay
unreachability?
TPB is constantly on the move .. my traceroute shows this hop
13 vlan102.ge-0-3.sth3-core-1.srstubes.net (194.68.0.158) 205.131 ms
212.424 ms 212.400 ms
Their website :
We welcome [..] free speech
Confirmed on 3 VPS servers in California, Chicago and Scranton:
All the packets die at piratpartiet.se
On 5/12/11, Michael Holstein michael.holst...@csuohio.edu wrote:
My guess would be routing problems, probably Comcast's. If some of the
whiners would post traceroutes maybe help could be
Confirmed on 3 VPS servers in California, Chicago and Scranton:
All the packets die at piratpartiet.se
You're assuming that the webserver permits ICMP. Try traceroute -T -p
80 thepiratebay.org
10 as40475.ge-0-2-1.cr1.sfo1.us.nlayer.net (69.22.153.90) 97.411 ms
97.049 ms 97.207 ms
11
# traceroute -T -p 80 thepiratebay.org
Chicago:
3 r1.chi1.us.as5580.net (78.152.63.85) 0.346 ms 0.400 ms 1.383 ms
4 r1.ash1.us.as5580.net (80.94.64.217) 29.253 ms
r1.nyc1.us.as5580.net (80.94.64.213) 22.749 ms 22.772 ms
5 r1.ams1.nl.as5580.net (80.94.64.149) 115.317 ms
Portland OR:
3 sjc1-pr1-xe-0-0-0-0.us.twtelecom.net (66.192.251.170) 15.584 ms
15.674 ms 15.580 ms
4 ae2-20g.cr1.sfo1.us.nlayer.net (69.22.143.162) 16.651 ms 16.810
ms 16.900 ms
5 as40475.ge-0-2-1.cr1.sfo1.us.nlayer.net (69.22.153.90) 16.837 ms
17.037 ms 16.812 ms
6
11 thepiratebay.piratpartiet.se (194.14.56.29) 197.033 ms 199.376
ms 197.917 ms
12 * * *
At this point, my guess would be that they're doing some sort of DDOS
protection in there somewhere, and haven't gotten it tuned up quite right.
13 * * *
~Mike.
From Amsterdam :
traceroute -T -p 80 thepiratebay.org
traceroute to thepiratebay.org (194.71.107.15), 30 hops max, 60 byte packets
1 core1-vlan1011.a2b-internet.com (178.249.153.17) 3.401 ms 3.428 ms
3.464 ms
2 core3-vlan102.a2b-internet.com (178.249.152.35) 1.262 ms 1.320 ms
1.315 ms
11 matches
Mail list logo
