It worked for me up until I changed my ISP. Captchas usually use the IP address to determine how difficult to make the challenge. Abusive ip ranges get worse experiences than others.
All I have to base that on is when I click on the checkbox sometimes no images load and it checks and then unchecks. Sometimes I seem to get the "hard set" though I think I missed part of the boat or something. I've been able to run through enough fails that I'd expect to get the hard set but don't. Which makes me think it isn't actually working right...
I'm calling the "hard set" those images they give you that are super extra grainy.
I'm almost curious enough to see what I can divine from inspecting their network requests but I have a hunch they have a vested interest in making that annoying.
Or maybe there are way more CAPTCHAs to click through than I'm thinking. To anyone: What is the highest number of CAPTCHAs you've clicked through and actually got a site, any site, to load at the end? I'm legit curious at this point.
So I'm thinking messed up cookies or extensions and IP reputation stuff are probably the root of this.
Edit:
cookies or extensions based on testing with chrome normal vs incognito on the same host
IP reputation based on testing with VPN using the same browser
That IP you're using is being shared with bots and other malware to attack sites. So instead of trying to filter out all the potential attacks through things like fail2ban, etc. what archive.is is doing is to just block entire ip address ranges.
It makes me yearn even more for IPv6 now.
From what I can tell though I'm able to get to a webserver running on my local machine and hosted off my public IP through a paid VPN. That indicates to me I am not behind CGNAT from what I understood of the wikipedia.
I probably missed something : )