To test if your ISP is affected, you can try opening anything from imgur.com over HTTPS.
With a DNS redirection to the filter, running this in Command Prompt (with the IP being your modem's internal IP, assuming it's a DNS relay server):
nslookup i.imgur.com 192.168.1.1
returns an IP from the ISP's network rather than an imgur one. When it gives me the iwffilter proxy IP, I know already that HTTPS connections to the site are going to fail.
My results at the moment:
1.
https://imgur.com/BAfsJ3j - Loads but without images (which are served from i.imgur.com)
2.
https://i.imgur.com/BAfsJ3j.gif - Certificate error
3.
http://imgur.com/BAfsJ3j - Loads
4.
http://i.imgur.com/BAfsJ3j.gif - Loads
I can find past reports from several ISPs having overload issues with their IWF proxy (for instance
Wired in 2014 about TalkTalk), but HTTPS makes the whole idea of a filtering proxy a technical impossibility, and I haven't seen much about that (this!) yet.