imgur.com been slow all week now unreachable

[#1]

As the title says it's been really slow all week now it doesn't load at all
It's just you. http://imgur.com is up.
http://www.downforeveryoneorjustme.com/imgur.com

[#2]

I can access the site but get timeouts when trying to open any image.

[#3]

it's slow across multiple vpn's - so it's not a PN issue.

[#4]

pretty instant here (no longer with plusnet)
still slow for everyone?

[#5]

Yep  
I've asked a friend who isn't on plusnet and he says it's fine for him
Then I found this on reddit
https://www.reddit.com/r/AskUK/comments/42npo1/imgur_loading_very_slowly_with_plusnet/
Edit  it's suddenly working fine did somebody at Plusnet plug something back in 

[#6]

This link is working https://imgur.com 

[#7]

imgur is loading fine for me, but www.blu-ray.com is not responding at all, even though the site is up and pinging the site is also fine.
Currently on ptn-bng01.

[#8]

imgur extremely slow and now not loading unless you change the http to https, which is no use from tablets, phones etc.
Can we have some input on this plusnet please because at them moment i can't fully enjoy my internet package that i pay you for.
oh yeah and i'm on adsl not fibre......

[#9]

Quote from: BillyHunt

Edit  it's suddenly working fine did somebody at Plusnet plug something back in

Started to work for me at the same time but has since died again.

[#10]

yes it has very briefly come back to life a few times throughout the day.. it's no use at all tbh

[#11]

Okay as it seems that only https works, from what I can gather.
This sounds like a DNS server issue, so I would recommend you to change to google DNS.
Or open DNS and make sure you run ipconfig /flushdns under cmd in windows.
Also clear your cache, cookies etc, just to be on the safe side.
Hope this helps.

[#12]

That doesn't make any sense, it's not a DNS issue, the same IP address is used for http and https.
It's most likely to be a Plusnet IWF filter (proxy) issue.

[#13]

Actually it does, if the host doesn't resolve properly.
Issues like this occur, I've had this issue with Virgin in the past.
It got to the point that I could download, upload and play games.
But browsing was broken, quick dns switch and flush.
And all was well.
A proxy filter wouldn't cause this, as it would block http and https in most cases.
You've to understand about data propagation with dns servers but you can google that.
If you're interested.
I tend to always use google dns, so I never get these issues.

[#14]

This was not a DNS issue. The IP address of imgur.com has not changed. There was no problem resolving the IP address. OK now I've noticed it's got two IP addresses, 185.31.18.193 and 185.31.19.193. You will get one or other of those IP addresses regardless of if you use Plusnet's DNS servers or Google DNS.
Here is a traceroute to TCP port 80 at the time it was working badly, fortunately it had not scrolled off the top of my terminal:
[tt]# traceroute -q 1 -N 1 -T -p 80 imgur.com
traceroute to imgur.com (185.31.19.193), 30 hops max, 52 byte packets
1  gateway (192.168.0.1)  4.347 ms
2  195.166.130.221 (195.166.130.221)  23.178 ms
3  link10-central10.pcl-gw02.plus.net (84.93.249.210)  23.245 ms
4  te9-4.ptn-gw01.plus.net (195.166.129.33)  29.794 ms
5  ae1.pcl-cr02.plus.net (195.166.129.3)  24.754 ms
6  tun0.pcl-gw01.plus.net (212.159.2.105)  26.404 ms
7  tun0.pcl-gw01.plus.net (212.159.2.105)  24.136 ms
8  *
9  *
10  *
11  *
12  *
13  *
14  *
15  *
...
[/tt]
The tun0 in that traceroute is a giveaway sign that it's going through Plusnet's IWF filter, or at least trying to but failing.
Actually, at the moment, it looks like one of the IP addresses goes through the filter and the other doesn't.
[tt]# traceroute -q 1 -N 1 -T -p 80 185.31.18.193
traceroute to 185.31.18.193 (185.31.18.193), 30 hops max, 52 byte packets
1  gateway (192.168.0.1)  1.772 ms
2  195.166.130.221 (195.166.130.221)  22.960 ms
3  link10-central10.pcl-gw02.plus.net (84.93.249.210)  22.763 ms
4  ae1.pcl-cr02.plus.net (195.166.129.3)  24.058 ms
5  te9-4.ptn-gw01.plus.net (195.166.129.33)  22.319 ms
6  tun0.ptn-gw01.plus.net (212.159.2.101)  22.716 ms
7  185.31.18.193 (185.31.18.193)  23.281 ms
# traceroute -q 1 -N 1 -T -p 80 185.31.19.193
traceroute to 185.31.19.193 (185.31.19.193), 30 hops max, 52 byte packets
1  gateway (192.168.0.1)  2.535 ms
2  195.166.130.221 (195.166.130.221)  22.978 ms
3  link10-central10.pcl-gw02.plus.net (84.93.249.210)  23.509 ms
4  195.99.126.182 (195.99.126.182)  27.012 ms
5  core1-te0-3-0-12.ilford.ukcore.bt.net (109.159.254.125)  27.623 ms
6  peer5-te0-10-0-11.telehouse.ukcore.bt.net (109.159.255.89)  26.256 ms
7  *
8  ldn-b3-link.telia.net (213.248.67.97)  24.943 ms
9  185.31.19.193 (185.31.19.193)  24.435 ms[/tt]

[#15]

Thanks for doing some of the legwork ejs. Hopefully we can get some official word on this issue. I think it's effecting other websites too such as http://www.nexusmods.com/