Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
court ordered blocked sites
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Plusnet Community
- :
- Forum
- :
- Help with my Plusnet services
- :
- Broadband
- :
- Re: court ordered blocked sites
court ordered blocked sites
12-01-2014 8:34 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
do plusnet supply a list of the sites they have blocked due to court orders?
sky do - http://help.sky.com/security/privacy/our-approach-to-protecting-copyright/
so do plusnet do the same?
if not, why not?
sky do - http://help.sky.com/security/privacy/our-approach-to-protecting-copyright/
so do plusnet do the same?
if not, why not?
Message 1 of 9
(2,848 Views)
8 REPLIES 8
Re: court ordered blocked sites
12-01-2014 8:39 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Because Plusnet aren't covered by those court orders and as far as I know haven't received any others
Message 2 of 9
(1,139 Views)
Re: court ordered blocked sites
12-01-2014 8:57 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
they are currently blocking TPB as far as i am aware.
Message 3 of 9
(1,139 Views)
Re: court ordered blocked sites
12-01-2014 8:58 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
No they aren't - if you read here you will see that it is a peering problem http://community.plus.net/forum/index.php/topic,117175.0.html
Message 4 of 9
(1,139 Views)
Re: court ordered blocked sites
12-01-2014 9:00 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
an 8 day peering problem?
are we getting the real reason here or is this a cover story?
are we getting the real reason here or is this a cover story?
Message 5 of 9
(1,139 Views)
Re: court ordered blocked sites
12-01-2014 9:43 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Well the fact that a tracert transits onto the BT retail network and hits their filter would suggest that it's due to something of this nature because Plusnet operates independently to BT retail or should do , the exact same thing has happened previously last year, iirc the last time it took them several weeks to sort it out, TBH though it should of been configured so it never re-occurred again IMO ,Maybe this time they will configure this properly if that's at all possible
Message 6 of 9
(1,139 Views)
Re: court ordered blocked sites
12-01-2014 9:47 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
@ deathtrap
It fails from all the major peers - so it is nothing to do with BT. Try their 'looking glasses' and see. Every traceroute is failing inside ntt's network (including BT) so is either a problem with the site hosting tpb or a peering issue with ntt.
Edit: Just to back up with it not being a BT problem...
Traceroute results from London, England (2)
to 194.71.107.27(194.71.107.27)
1 ae-15-15.edge3.London2.Level3.net (4.69.200.85) 0 msec 0 msec 0 msec
2 ae-3-3.ebr1.Paris1.Level3.net (4.69.141.86) 8 msec 8 msec 8 msec
3 ae-91-91.csw4.Paris1.Level3.net (4.69.161.90) 8 msec
ae-61-61.csw1.Paris1.Level3.net (4.69.161.78) 8 msec
ae-81-81.csw3.Paris1.Level3.net (4.69.161.86) 8 msec
4 4.69.168.199 8 msec
4.69.168.135 8 msec
4.69.168.199 8 msec
5 NTT-level3-2x10G.Paris.Level3.net (4.68.63.118) 8 msec 8 msec 8 msec
6 ae-2.r21.parsfr01.fr.bb.gin.ntt.net (129.250.2.218) [AS2914 {NTTC-GIN-AS}] 4 msec 8 msec 8 msec
7 as-4.r22.amstnl02.nl.bb.gin.ntt.net (129.250.3.84) [AS2914 {NTTC-GIN-AS}] 16 msec 12 msec 16 msec
8 ae-1.r02.amstnl02.nl.bb.gin.ntt.net (129.250.2.113) [AS2914 {NTTC-GIN-AS}] 20 msec 20 msec 20 msec
9 xe-4-1.r02.dsdfge01.de.bb.gin.ntt.net (129.250.2.65) [AS2914 {NTTC-GIN-AS}] 24 msec 24 msec 20 msec
10 *
xe-3-4.r00.dsdfge02.de.bb.gin.ntt.net (129.250.5.173) [AS2914 {NTTC-GIN-AS}] 20 msec 24 msec
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * timeout !
Tracing the route to thepiratebay.se (194.71.107.27)
1 if-1-3-1-0.tcore1.LDN-London.as6453.net (80.231.76.86) 0 msec
if-2-3-1-0.tcore1.LDN-London.as6453.net (80.231.76.122) 0 msec
if-1-3-1-0.tcore1.LDN-London.as6453.net (80.231.76.86) 4 msec
2 195.219.83.186 0 msec 4 msec 0 msec
3 ae-4.r22.londen03.uk.bb.gin.ntt.net (129.250.5.24) [AS 2914] [MPLS: Label 463568 Exp 0] 0 msec 0 msec 0 msec
4 ae-3.r21.frnkge03.de.bb.gin.ntt.net (129.250.3.138) [AS 2914] [MPLS: Label 300032 Exp 0] 16 msec 32 msec 32 msec
5 ae-1.r02.frnkge03.de.bb.gin.ntt.net (129.250.4.163) [AS 2914] [MPLS: Label 16051 Exp 0] 20 msec 28 msec 16 msec
6 xe-3-2.r00.dsdfge02.de.bb.gin.ntt.net (129.250.5.61) [AS 2914] 24 msec 44 msec 48 msec
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
traceroute to 194.71.107.27 (194.71.107.27), 30 hops max, 40 byte packets
1 ae-0.r22.londen03.uk.bb.gin.ntt.net (129.250.4.85) 28.755 ms 0.576 ms 0.540 ms
MPLS Label=778726 CoS=0 TTL=1 S=0
MPLS Label=300032 CoS=0 TTL=1 S=1
2 ae-3.r21.frnkge03.de.bb.gin.ntt.net (129.250.3.138) 18.313 ms 11.943 ms 12.992 ms
MPLS Label=300032 CoS=0 TTL=1 S=1
3 ae-1.r02.frnkge03.de.bb.gin.ntt.net (129.250.4.163) 25.861 ms 24.843 ms 24.113 ms
MPLS Label=16051 CoS=0 TTL=255 S=1
4 xe-3-2.r00.dsdfge02.de.bb.gin.ntt.net (129.250.5.61) 17.353 ms 14.626 ms 20.607 ms
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
Tracing the route to 194.71.107.27
1 t2c4-xe-1-3-1-0.uk-lon1.eu.bt.net (166.49.135.16) 0 msec 0 msec 0 msec
2 82.112.101.73 [AS 2914] 0 msec 4 msec 0 msec
3 ae-6.r22.londen03.uk.bb.gin.ntt.net (129.250.4.20) [AS 2914] [MPLS: Label 463568 Exp 0] 0 msec
0 msec 0 msec
4 ae-3.r21.frnkge03.de.bb.gin.ntt.net (129.250.3.138) [AS 2914] [MPLS: Label 300032 Exp 0] 12
msec 12 msec 20 msec
5 ae-1.r02.frnkge03.de.bb.gin.ntt.net (129.250.4.163) [AS 2914] [MPLS: Label 16051 Exp 0] 20 msec
12 msec 16 msec
6 xe-3-2.r00.dsdfge02.de.bb.gin.ntt.net (129.250.5.61) [AS 2914] 12 msec 16 msec 16 msec
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
It fails from all the major peers - so it is nothing to do with BT. Try their 'looking glasses' and see. Every traceroute is failing inside ntt's network (including BT) so is either a problem with the site hosting tpb or a peering issue with ntt.
Edit: Just to back up with it not being a BT problem...
Traceroute results from London, England (2)
to 194.71.107.27(194.71.107.27)
1 ae-15-15.edge3.London2.Level3.net (4.69.200.85) 0 msec 0 msec 0 msec
2 ae-3-3.ebr1.Paris1.Level3.net (4.69.141.86) 8 msec 8 msec 8 msec
3 ae-91-91.csw4.Paris1.Level3.net (4.69.161.90) 8 msec
ae-61-61.csw1.Paris1.Level3.net (4.69.161.78) 8 msec
ae-81-81.csw3.Paris1.Level3.net (4.69.161.86) 8 msec
4 4.69.168.199 8 msec
4.69.168.135 8 msec
4.69.168.199 8 msec
5 NTT-level3-2x10G.Paris.Level3.net (4.68.63.118) 8 msec 8 msec 8 msec
6 ae-2.r21.parsfr01.fr.bb.gin.ntt.net (129.250.2.218) [AS2914 {NTTC-GIN-AS}] 4 msec 8 msec 8 msec
7 as-4.r22.amstnl02.nl.bb.gin.ntt.net (129.250.3.84) [AS2914 {NTTC-GIN-AS}] 16 msec 12 msec 16 msec
8 ae-1.r02.amstnl02.nl.bb.gin.ntt.net (129.250.2.113) [AS2914 {NTTC-GIN-AS}] 20 msec 20 msec 20 msec
9 xe-4-1.r02.dsdfge01.de.bb.gin.ntt.net (129.250.2.65) [AS2914 {NTTC-GIN-AS}] 24 msec 24 msec 20 msec
10 *
xe-3-4.r00.dsdfge02.de.bb.gin.ntt.net (129.250.5.173) [AS2914 {NTTC-GIN-AS}] 20 msec 24 msec
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * timeout !
Tracing the route to thepiratebay.se (194.71.107.27)
1 if-1-3-1-0.tcore1.LDN-London.as6453.net (80.231.76.86) 0 msec
if-2-3-1-0.tcore1.LDN-London.as6453.net (80.231.76.122) 0 msec
if-1-3-1-0.tcore1.LDN-London.as6453.net (80.231.76.86) 4 msec
2 195.219.83.186 0 msec 4 msec 0 msec
3 ae-4.r22.londen03.uk.bb.gin.ntt.net (129.250.5.24) [AS 2914] [MPLS: Label 463568 Exp 0] 0 msec 0 msec 0 msec
4 ae-3.r21.frnkge03.de.bb.gin.ntt.net (129.250.3.138) [AS 2914] [MPLS: Label 300032 Exp 0] 16 msec 32 msec 32 msec
5 ae-1.r02.frnkge03.de.bb.gin.ntt.net (129.250.4.163) [AS 2914] [MPLS: Label 16051 Exp 0] 20 msec 28 msec 16 msec
6 xe-3-2.r00.dsdfge02.de.bb.gin.ntt.net (129.250.5.61) [AS 2914] 24 msec 44 msec 48 msec
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
traceroute to 194.71.107.27 (194.71.107.27), 30 hops max, 40 byte packets
1 ae-0.r22.londen03.uk.bb.gin.ntt.net (129.250.4.85) 28.755 ms 0.576 ms 0.540 ms
MPLS Label=778726 CoS=0 TTL=1 S=0
MPLS Label=300032 CoS=0 TTL=1 S=1
2 ae-3.r21.frnkge03.de.bb.gin.ntt.net (129.250.3.138) 18.313 ms 11.943 ms 12.992 ms
MPLS Label=300032 CoS=0 TTL=1 S=1
3 ae-1.r02.frnkge03.de.bb.gin.ntt.net (129.250.4.163) 25.861 ms 24.843 ms 24.113 ms
MPLS Label=16051 CoS=0 TTL=255 S=1
4 xe-3-2.r00.dsdfge02.de.bb.gin.ntt.net (129.250.5.61) 17.353 ms 14.626 ms 20.607 ms
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
Tracing the route to 194.71.107.27
1 t2c4-xe-1-3-1-0.uk-lon1.eu.bt.net (166.49.135.16) 0 msec 0 msec 0 msec
2 82.112.101.73 [AS 2914] 0 msec 4 msec 0 msec
3 ae-6.r22.londen03.uk.bb.gin.ntt.net (129.250.4.20) [AS 2914] [MPLS: Label 463568 Exp 0] 0 msec
0 msec 0 msec
4 ae-3.r21.frnkge03.de.bb.gin.ntt.net (129.250.3.138) [AS 2914] [MPLS: Label 300032 Exp 0] 12
msec 12 msec 20 msec
5 ae-1.r02.frnkge03.de.bb.gin.ntt.net (129.250.4.163) [AS 2914] [MPLS: Label 16051 Exp 0] 20 msec
12 msec 16 msec
6 xe-3-2.r00.dsdfge02.de.bb.gin.ntt.net (129.250.5.61) [AS 2914] 12 msec 16 msec 16 msec
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Message 7 of 9
(1,139 Views)
Re: court ordered blocked sites
12-01-2014 10:03 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Well the last time a similar issue occured we got the same Tracert results peering onto BT retails platform???
Message 8 of 9
(1,139 Views)
Re: court ordered blocked sites
12-01-2014 10:21 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Our traceroute's from Plusnet don't appear to get anywhere near ntt.net. Perhaps thepiratebay.se doesn't respond to pings so every traceroute from anywhere using ICMP will fail before reaching the destination even when the site is accessible.
Message 9 of 9
(1,139 Views)
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Plusnet Community
- :
- Forum
- :
- Help with my Plusnet services
- :
- Broadband
- :
- Re: court ordered blocked sites