4chan blocked?

[#1]

I can't access 4chan.org, the page times out and I get the good old firefox "Problem loading page" Its been like this for a day or so.
I can access the site through a proxy and the site isn't having any problems, so does anyone know what could be the issue? are plusnet blocking me access to the site?
Thanks in advance.

[#2]

very possibly because of reported child pornography
From Google

Quote

hc/ is 4chan's imageboard for the posting of tasteful hardcore ...

[#3]

See these threads:
No access to forum
Do Some Gateways Block Certain Sites?
A workaround is to disconnect and reconnect from your router's web interface and hope you end up on one of the "pcl" gateways.
[tt]traceroute -T -p 80 4chan.org
traceroute to 4chan.org (141.101.124.244), 30 hops max, 60 byte packets
1  192.168.0.1 (192.168.0.1)  2.448 ms  3.253 ms  3.649 ms
2  lo0-central4.ptw-ag01.plus.net (195.166.130.109)  23.187 ms  24.975 ms  26.379 ms
3  84.93.253.99 (84.93.253.99)  30.201 ms  30.877 ms  32.530 ms
4  po4.ptw-gw01.plus.net (212.159.1.134)  76.705 ms  77.189 ms  78.542 ms
5  ae4.ptw-cr01.plus.net (195.166.129.36)  44.160 ms  44.987 ms  45.537 ms
6  te9-4.ptn-gw01.plus.net (195.166.129.33)  46.020 ms  20.603 ms  22.300 ms
7  tun0.ptn-gw01.plus.net (212.159.2.101)  24.051 ms  25.664 ms  27.570 ms
8  vl69.ptw-gw02.plus.net (212.159.3.253)  90.966 ms  48.523 ms  49.433 ms
9  po4.ptn-gw01.plus.net (212.159.1.138)  24.105 ms  26.451 ms  28.192 ms
10  tun0.ptn-gw01.plus.net (212.159.2.101)  29.898 ms  32.157 ms  34.391 ms
11  vl69.ptw-gw02.plus.net (212.159.3.253)  49.596 ms  50.053 ms  50.974 ms
12  po4.ptn-gw01.plus.net (212.159.1.138)  40.602 ms  37.172 ms  39.317 ms
13  tun0.ptn-gw01.plus.net (212.159.2.101)  40.521 ms  27.957 ms  26.845 ms
14  vl69.ptw-gw02.plus.net (212.159.3.253)  142.631 ms  141.464 ms  139.632 ms
15  po4.ptn-gw01.plus.net (212.159.1.138)  23.845 ms  19.921 ms  20.481 ms[/tt]

[#4]

Alternative workaround: https://www.4chan.org/

[#5]

Quote from: ejs

Alternative workaround: https://www.4chan.org/

This works! Thanks.
I reset the router but it didn't help, the page still wouldn't load.
So is plusnet blocking this site, or is just me? 

[#6]

It is probably being blocked by mistake otherwise the https version would be blocked as well
Running a tracert gives this but I still can't access it
Tracing route to 4chan.org [199.27.135.243]
over a maximum of 30 hops:
 1    <1 ms    <1 ms    <1 ms  192.168.0.1
 2    35 ms    32 ms    32 ms  lo0-central2.ptw-ag02.plus.net [195.166.128.230]
 3    33 ms    32 ms    32 ms  gi1-14-221.ptw-gw01.plus.net [84.92.6.200]
 4    32 ms    32 ms    32 ms  ae4.ptw-cr01.plus.net [195.166.129.36]
 5    31 ms    31 ms    33 ms  te9-4.ptn-gw01.plus.net [195.166.129.33]
 6    33 ms    32 ms    33 ms  tun0.ptn-gw01.plus.net [212.159.2.101]
 7    53 ms    32 ms    31 ms  195.99.126.144
 8    43 ms    35 ms    34 ms  core1-te0-3-0-12.ilford.ukcore.bt.net [109.159.254.125]
 9    41 ms    35 ms    35 ms  62.172.103.189
10    87 ms    33 ms    32 ms  mgre.customer.bt.net [194.72.9.2]
11    34 ms    33 ms    33 ms  t2c3-xe-9-2-0.uk-eal.eu.bt.net [166.49.168.25]
12    33 ms    33 ms    33 ms  t2c1-ge8-0-0.uk-eal.eu.bt.net [166.49.237.17]
13    33 ms    32 ms    33 ms  t2c2-p3-0-1.uk-lon1.eu.bt.net [166.49.208.110]
14    34 ms    34 ms    33 ms  t2a1-ge7-0-0.uk-lon1.eu.bt.net [166.49.135.49]
15    37 ms    35 ms    36 ms  xe-3-0-0.cr1.lhr1.uk.nlayer.net [195.66.236.37]
16    33 ms    33 ms    33 ms  ae2-70g.cr1.lhr1.uk.nlayer.net [69.22.139.62]
17    41 ms    41 ms    42 ms  xe-0-0-0.cr1.cdg1.fr.nlayer.net [69.22.142.66]
18    42 ms    41 ms    42 ms  as13335.xe-0-0-1-302.cr1.cdg1.fr.nlayer.net [63.141.223.18]
19    42 ms    44 ms    41 ms  cf-199-27-135-243.cloudflare.com [199.27.135.243]
Trace complete.

[#7]

Thanks for the help. Cloudflare could be having issues as 4chan have recently updated to a new html/css layout. I'm not knowledgeable in this area but could this be causing the issues?
jim:quote

[#8]

Quote from: Oldjim

very possibly because of reported child pornography

whilst 4chan is distasteful, the do not allow child pornography and is actively policed (about the only thing that is)

[#9]

The original link to the site works fine for me as well as the https version.

[#10]

Quote from: Chris

The original link to the site works fine for me as well as the https version.

Hmm... a few of us can't access the standard link but can the https
That is rather odd 

[#11]

Quote from: Oldjim

It is probably being blocked by mistake otherwise the https version would be blocked as well

Or the blocking is poorly designed. Or someone has decided to implement it strictly to the letter, so that if the list of stuff to block contains http://example.com/whatever then that's what they'll block, just that, not https://example.com/whatever nor http://example.com:8080/whatever etc.
If the IP address is on a list, IIRC then it is supposed to go to a second level of checks to examine the whole URL, but that's not really going to work with https because the URL and everything else is encrypted and can't be seen by something in the middle.
@Chris Pettit - have you read my earlier post - the only thing that's odd is that this problem keeps on re-occurring.

[#12]

/b is down.
They have done some upgrades over the past couple weeks (infrastructure and new HTML5 enabled bits) not sure if that is related, but am sure moot is on it.

[#13]

As has been mentioned it's most likely that the site has ended up on the IWF watch list (the traceroute earlier in the thread shows this too).
We'll get an internal problem raised to look at this shorty.

[#14]

Thanks, I've not been able to access the site without using Https:// for a couple of days now.
adie:quote

[#15]

Quote from: Chris

As has been mentioned it's most likely that the site has ended up on the IWF watch list (the traceroute earlier in the thread shows this too).

Out of interest, which entry in the traceroute shows this?  I'm having trouble with another site that seems a likely candidate to have ended up on the IWF list (they host user-uploaded content and aren't very reactive at removing it if people complain), and would like to be able to check if this is the actual cause.  If so, is there any way to disable the block?  It really *shouldn't* be operating on a per-domain basis when only a very small minority of pages on these sites are likely to be offending.