Do Some Gateways Block Certain Sites?

[#1]

pcl-ag07 20CN
I can ping it, tracert below, but I can't browse to it. Has it been deliberately blocked for some reason? (Illegal p2p?)
Tracing route to turbobit.net [188.72.243.97]
over a maximum of 30 hops:
 1     1 ms     1 ms    <1 ms  RTA1335.home [192.168.1.1]
 2    36 ms    34 ms    44 ms  lo0-central1.pcl-ag07.plus.net [195.166.130.58]
 3    34 ms    34 ms    35 ms  gi7-10-711.pcl-gw01.plus.net [84.93.254.209]
 4    37 ms    34 ms    34 ms  po4.pcl-gw02.plus.net [212.159.1.129]
 5    34 ms    34 ms    34 ms  tun0.pcl-gw01.plus.net [212.159.2.105]
 6    36 ms    34 ms    34 ms  flowers2.servers.plus.net.uk [212.159.2.98]
 7    33 ms    33 ms    35 ms  xe-11-1-0.edge3.London2.Level3.net [212.187.201.209]
 8    35 ms    33 ms    34 ms  ae-0-11.edge4.London2.Level3.net [4.69.200.126]
 9    36 ms    34 ms    35 ms  ae-3-3.ebr1.London1.Level3.net [4.69.141.189]
10    37 ms    37 ms    37 ms  vlan103.ebr2.London1.Level3.net [4.69.143.94]
11    43 ms    45 ms    43 ms  ae-22-22.ebr2.Frankfurt1.Level3.net [4.69.148.190]
12    45 ms    50 ms    49 ms  ae-62-62.csw1.Frankfurt1.Level3.net [4.69.140.18]
13    43 ms    44 ms    44 ms  ae-1-60.edge4.Frankfurt1.Level3.net [4.69.154.8]
14   151 ms   215 ms   210 ms  212.162.5.234
15    45 ms    44 ms    45 ms  hosted-by.leaseweb.com [89.149.218.210]
16     *        *        *     Request timed out.
17     *        *       47 ms  turbobit.net [188.72.243.97]
Trace complete.

[#2]

I'm currently on "pcl-ag03" and CAN browse to http://turbobit.net/ OK

[#3]

The IWF detector logic suggests turbobit.net made the list:
[tt]# traceroute -T -p 80 turbobit.net
traceroute to turbobit.net (188.72.243.97), 30 hops max, 60 byte packets
1  192.168.0.1 (192.168.0.1)  2.400 ms  3.199 ms  3.602 ms
2  lo0-central3.pcl-ag05.plus.net (195.166.130.36)  30.438 ms  35.188 ms  38.524 ms
3  gi7-5-531.pcl-gw01.plus.net (84.93.254.65)  27.490 ms  29.875 ms  32.005 ms
4  po4.pcl-gw02.plus.net (212.159.1.129)  88.005 ms  89.681 ms  90.083 ms
5  tun0.pcl-gw01.plus.net (212.159.2.105)  90.590 ms  91.026 ms  91.471 ms
6  hosted-by.leaseweb.com (188.72.243.97)  44.186 ms  20.654 ms  22.491 ms[/tt]
[tt]# traceroute -T -p 81 turbobit.net
traceroute to turbobit.net (188.72.243.97), 30 hops max, 60 byte packets
1  192.168.0.1 (192.168.0.1)  2.326 ms  3.206 ms  3.622 ms
2  lo0-central3.pcl-ag05.plus.net (195.166.130.36)  23.369 ms  26.034 ms  26.609 ms
3  gi7-5-531.pcl-gw01.plus.net (84.93.254.65)  29.109 ms  30.428 ms  31.689 ms
4  po4.pcl-gw02.plus.net (212.159.1.129)  33.900 ms  35.412 ms  37.734 ms
5  tun0.pcl-gw01.plus.net (212.159.2.105)  40.131 ms  40.892 ms  43.248 ms
6  flowers2.servers.plus.net.uk (212.159.2.98)  45.644 ms  43.797 ms  45.566 ms
7  xe-11-1-0.edge3.London2.Level3.net (212.187.201.209)  47.360 ms  29.355 ms  28.661 ms
8  ae-0-11.edge4.London2.Level3.net (4.69.200.126)  31.763 ms  30.373 ms  30.939 ms
9  ae-3-3.ebr1.London1.Level3.net (4.69.141.189)  31.500 ms  29.778 ms  30.573 ms
10  vlan103.ebr2.London1.Level3.net (4.69.143.94)  31.289 ms vlan101.ebr2.London1.Level3.net (4.69.143.86)  30.078 ms  31.931 ms
11  ae-23-23.ebr2.Frankfurt1.Level3.net (4.69.148.194)  39.806 ms ae-21-21.ebr2.Frankfurt1.Level3.net (4.69.148.186)  34.445 ms  36.081 ms
12  ae-72-72.csw2.Frankfurt1.Level3.net (4.69.140.22)  38.428 ms ae-92-92.csw4.Frankfurt1.Level3.net (4.69.140.30)  30.657 ms  31.655 ms
13  ae-1-60.edge4.Frankfurt1.Level3.net (4.69.154.8)  33.857 ms  36.214 ms  37.308 ms
14  212.162.5.234 (212.162.5.234)  301.133 ms  301.502 ms  301.957 ms
15  hosted-by.leaseweb.com (89.149.218.202)  46.410 ms hosted-by.leaseweb.com (89.149.218.210)  31.707 ms hosted-by.leaseweb.com (89.149.218.202)  31.905 ms
16  * * *
17  hosted-by.leaseweb.com (188.72.243.97)  36.244 ms  33.702 ms  32.416 ms[/tt]

[#4]

This is getting daft if you have to keep jump gateways just to access different sites.
But this morning I can access turbobit.net???
I haven't changed gateways so what's going on?
I couldn't access it but websitedown said it was up and some others on different gateways could access it.

[#5]

turbobit.net woking fine here on pcl-ag08.

[#6]

It could just have been a case of turbobit itself being unable to cope with the demand last night, but is working again today when things have quietened down.

[#7]

Site is not loading here on ptn-ag03

[#8]

It's no surprise that turbobit.net suffers from the same routing loop on ptn gateways:
[tt]traceroute -T -p 80 turbobit.net
traceroute to turbobit.net (188.72.243.97), 30 hops max, 60 byte packets
1  192.168.0.1 (192.168.0.1)  2.385 ms  2.861 ms  3.754 ms
2  lo0-central7.ptn-ag04.plus.net (195.166.130.129)  37.194 ms  46.666 ms  59.127 ms
3  84.93.251.155 (84.93.251.155)  27.605 ms  28.975 ms  31.537 ms
4  po4.ptn-gw01.plus.net (212.159.1.138)  32.938 ms  35.544 ms  39.280 ms
5  tun0.ptn-gw01.plus.net (212.159.2.101)  40.330 ms  40.791 ms  42.959 ms
6  vl69.ptw-gw02.plus.net (212.159.3.253)  45.993 ms  44.200 ms  45.402 ms
7  po4.ptn-gw01.plus.net (212.159.1.138)  46.322 ms  23.662 ms  25.053 ms
8  tun0.ptn-gw01.plus.net (212.159.2.101)  24.729 ms  26.502 ms  24.272 ms
9  vl69.ptw-gw02.plus.net (212.159.3.253)  24.967 ms  24.470 ms  25.385 ms
10  po4.ptn-gw01.plus.net (212.159.1.138)  26.694 ms  26.391 ms  25.350 ms
11  tun0.ptn-gw01.plus.net (212.159.2.101)  26.330 ms  28.374 ms  28.570 ms
12  vl69.ptw-gw02.plus.net (212.159.3.253)  28.804 ms  28.187 ms  28.291 ms
13  po4.ptn-gw01.plus.net (212.159.1.138)  28.121 ms  20.644 ms  23.012 ms
14  tun0.ptn-gw01.plus.net (212.159.2.101)  24.316 ms  25.688 ms  27.997 ms
15  vl69.ptw-gw02.plus.net (212.159.3.253)  30.345 ms  31.453 ms  33.820 ms
...[/tt]

[#9]

Same Gateway 20CN pcl-ag07, same IP address and just now it worked.

[#10]

Quote from: Plusnet

Planned Network Maintenance 11th May 1.00am-7.00am What does the work involve? We're making configuration changes to some of our gateways.

If the above was supposed to fix this issue, I don't see any difference. I'm a bit surprised this has taken over a week to investigate considering it's not the first time this has happened.

[#11]

Broken via ptw-ag03:

adw@nofate:~$ tcptraceroute turbobit.net
Selected device eth0, address 10.0.1.20, port 40976 for outgoing packets
Tracing the path to turbobit.net (188.72.243.97) on TCP port 80 (www), 30 hops max
 1  10.0.1.1  0.226 ms  0.146 ms  0.156 ms
 2  lo0-central2.ptw-ag03.plus.net (195.166.128.48)  45.942 ms  21.528 ms  23.965 ms
 3  gi1-16-321.ptw-gw01.plus.net (84.92.3.216)  24.973 ms  22.342 ms  19.956 ms
 4  ae4.ptw-cr01.plus.net (195.166.129.36)  20.003 ms  29.333 ms  23.964 ms
 5  te9-4.ptn-gw01.plus.net (195.166.129.33)  23.944 ms  22.410 ms  19.973 ms
 6  tun0.ptn-gw01.plus.net (212.159.2.101)  20.966 ms  48.482 ms  19.918 ms
 7  vl69.ptw-gw02.plus.net (212.159.3.253)  19.967 ms  22.098 ms  23.966 ms
 8  po4.ptn-gw01.plus.net (212.159.1.138)  19.982 ms  21.665 ms  20.963 ms
 9  tun0.ptn-gw01.plus.net (212.159.2.101)  24.975 ms  23.399 ms  22.969 ms
10  vl69.ptw-gw02.plus.net (212.159.3.253)  19.977 ms  22.941 ms  19.975 ms
11  po4.ptn-gw01.plus.net (212.159.1.138)  19.976 ms  22.129 ms  19.961 ms
12  tun0.ptn-gw01.plus.net (212.159.2.101)  19.981 ms  22.629 ms  19.989 ms
13  vl69.ptw-gw02.plus.net (212.159.3.253)  21.948 ms  22.720 ms  23.960 ms
14  po4.ptn-gw01.plus.net (212.159.1.138)  24.974 ms  22.823 ms  24.972 ms
15  tun0.ptn-gw01.plus.net (212.159.2.101)  23.964 ms  22.642 ms  19.962 ms
16  vl69.ptw-gw02.plus.net (212.159.3.253)  20.992 ms  21.519 ms  20.983 ms
17  po4.ptn-gw01.plus.net (212.159.1.138)  24.968 ms  22.511 ms  23.963 ms
18  tun0.ptn-gw01.plus.net (212.159.2.101)  19.979 ms  22.746 ms  20.973 ms
19  vl69.ptw-gw02.plus.net (212.159.3.253)  23.977 ms  22.370 ms  20.967 ms
20  po4.ptn-gw01.plus.net (212.159.1.138)  23.973 ms  23.222 ms  23.973 ms
21  tun0.ptn-gw01.plus.net (212.159.2.101)  20.002 ms  22.405 ms  20.964 ms
22  vl69.ptw-gw02.plus.net (212.159.3.253)  23.974 ms  23.398 ms  23.974 ms
23  po4.ptn-gw01.plus.net (212.159.1.138)  20.981 ms  22.478 ms  24.995 ms
24  tun0.ptn-gw01.plus.net (212.159.2.101)  23.955 ms  23.552 ms  23.980 ms
25  vl69.ptw-gw02.plus.net (212.159.3.253)  19.936 ms  23.026 ms  24.959 ms
26  po4.ptn-gw01.plus.net (212.159.1.138)  24.975 ms  22.679 ms  25.986 ms
27  tun0.ptn-gw01.plus.net (212.159.2.101)  23.970 ms  22.896 ms  23.967 ms
28  vl69.ptw-gw02.plus.net (212.159.3.253)  20.976 ms  21.838 ms  20.969 ms
29  po4.ptn-gw01.plus.net (212.159.1.138)  23.978 ms  23.436 ms  23.962 ms
30  tun0.ptn-gw01.plus.net (212.159.2.101)  20.960 ms  21.414 ms  19.952 ms
Destination not reached

[#12]

Quote

If the above was supposed to fix this issue, I don't see any difference.

No, that was unrelated.
BTW the issue in hand that was raised with networks is still being worked on and we anticipate that this should be resolved some time next week.
I've set myself a reminder to chase this up again for you guys.

[#13]

FYI, just letting you know that I'm chasing this up again right now...

[#14]

Afternoon folks.
This has now passed through our change control process and are just awaiting a window in which to complete the required work.

[#15]

The changes have been pushed out to our live platform. There is some further work, but nothing that prevents operation.
Can you let us know if you are still seeing issues?