Domain: serioustubes.org
Stories and comments across the archive that link to serioustubes.org.
Comments · 7
-
Re:Hahaha have some crow
Actually, according to Serious Tubes Network (the ISP in question), Comcast did _not_ help them:
http://serioustubes.org/Important news:
Comcast did not help us fix The Pirate Bay. The problem was GBLX using reverse path filtering. We shut down one of our transits because it was flapping. The result was that all outgoing traffic to GBLX got filtered even though the packets took the same path as before. The Pirate Bay is using different paths for incoming and outgoing traffic to avoid beeing traced. We don’t even know where their servers are. We resolved the issue by activating our other transit again.
-
Not sure I believe it yet....I am not sure that we have the entire story yet, on either side. From the Serious Tubes website:
Important news:
Comcast did not help us fix The Pirate Bay. The problem was GBLX using reverse path filtering. We shut down one of our transits because it was flapping. The result was that all outgoing traffic to GBLX got filtered even though the packets took the same path as before. The Pirate Bay is using different paths for incoming and outgoing traffic to avoid beeing traced. We don’t even know where their servers are. We resolved the issue by activating our other transit again. -
Comcast did not help
According to Serious Tubes Networks, http://serioustubes.org/:
Comcast did not help us fix The Pirate Bay. The problem was GBLX using reverse path filtering. We shut down one of our transits because it was flapping. The result was that all outgoing traffic to GBLX got filtered even though the packets took the same path as before. The Pirate Bay is using different paths for incoming and outgoing traffic to avoid beeing traced. We don’t even know where their servers are. We resolved the issue by activating our other transit again.
-
Comcast didn't help Pirate Bay
From the Serious Tubes Network
Comcast did not help us fix The Pirate Bay. The problem was GBLX using reverse path filtering. We shut down one of our transits because it was flapping. The result was that all outgoing traffic to GBLX got filtered even though the packets took the same path as before. The Pirate Bay is using different paths for incoming and outgoing traffic to avoid beeing traced. We don’t even know where their servers are. We resolved the issue by activating our other transit again.
-
Serious Tubes says Comcast didn't fix itAccording to their homepage:
Important news:
Comcast did not help us fix The Pirate Bay. The problem was GBLX using reverse path filtering. We shut down one of our transits because it was flapping. The result was that all outgoing traffic to GBLX got filtered even though the packets took the same path as before. The Pirate Bay is using different paths for incoming and outgoing traffic to avoid beeing traced. We don’t even know where their servers are. We resolved the issue by activating our other transit again. -
Re:Seriously?
If they optimize their network as well as they optimize the images on their website, I can see why they ran into trouble.
(For those who are capped and can't afford the bandwidth anymore, that's a ~350kb, 250x400 image)
-
Re:Seriously?
"Serious Tubes Networks"? What is it, an ISP run by
/b/tards?Looks that way! http://serioustubes.org/