Your traceroutes appear to indicate Orcon aren't nullrouting TPB and are passing along packets just fine. At the moment I can access TPB from an Orcon LLU connection without issues, my traceroute looks similar to yours.
traceroute to thepiratebay.se (194.71.107.15), 64 hops max, 52 byte packets 1 172.16.1.1 (172.16.1.1) 9.229 ms 5.517 ms 2.616 ms 2 192.168.1.1 (192.168.1.1) 3.300 ms 1.750 ms 1.327 ms 3 llu.bng1.tvc.orcon.net.nz (60.234.8.4) 13.472 ms 13.491 ms 10.221 ms 4 xe-3-3-0.cre1.sky.orcon.net.nz (121.98.9.72) 10.153 ms 12.082 ms 13.150 ms 5 ge-0-1-5-0.cre1.nct.orcon.net.nz (121.98.9.9) 10.668 ms 14.038 ms 10.063 ms 6 121.99.12.0 (121.99.12.0) 13.494 ms 12.742 ms 13.301 ms 7 te4-4.ccr01.lax05.atlas.cogentco.com (38.104.84.29) 258.173 ms 151.383 ms 149.105 ms 8 te1-7.ccr02.lax05.atlas.cogentco.com (154.54.87.162) 176.268 ms te1-8.ccr02.lax05.atlas.cogentco.com (154.54.82.58) 176.688 ms te4-1.ccr02.lax05.atlas.cogentco.com (154.54.28.70) 150.634 ms 9 telia.lax05.atlas.cogentco.com (154.54.10.10) 173.110 ms 182.622 ms telia.lax05.atlas.cogentco.com (154.54.12.218) 147.665 ms 10 nyk-bb2-link.telia.net (80.91.252.166) 230.092 ms nyk-bb2-link.telia.net (80.91.246.227) 368.857 ms nyk-bb2-link.telia.net (80.91.252.166) 234.857 ms 11 kbn-bb2-link.telia.net (213.155.134.53) 343.213 ms 613.966 ms 347.070 ms 12 s-bb2-link.telia.net (213.155.134.142) 574.413 ms 339.499 ms 377.246 ms 13 s-b2-link.telia.net (213.155.133.143) 360.170 ms 324.869 ms 325.392 ms 14 * * * 15 * * * 16 * * * 17 * *^C
apparently portlane.se, thepiratebay's primary provider get ddosed a lot. not just from hosting the pirate bay. they host efnet server, wikileaks etc too.
although your traceroutes look similar, it could be that the reverse path is having issues, or that traffic is being filtered due to ddos attacks.
Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly
to your computer or smartphone by using a feed reader.