I want to clarify that the Captcha problem isn't the the earlier CloudFlare DNS issue, the one where Cloudflare DNS was returning IPs that didn't work. (IPs tha

I want to clarify that the Captcha problem isn't the the earlier CloudFlare DNS issue, the one where Cloudflare DNS was returning IPs that didn't work. (IPs that Archive supplied, btw). This issue is different. People are getting unsolvable Captcha pages from Archive. A lot. It might be due to DNS again. If so, it's lots of DNS providers and not just CloudFlare. Back in August, whether you got Captcha depended on which IP you got for archive.is/.today/.ph/etc. Example, if you queried for archive.is and got 198.23.187.186 you got Captcha'd. If you got 89.253.237.217 you didn't. I haven't tracked the issue this closely since Aug, however. A below poster is having success by statically assigning IPs for Archive requests. I did that too back in Aug. It worked for a while. What I'm seeing today is get Captcha'd no matter what upstream DNS service I use. What matters is what ISP I use - almost certainly because DNS servers vary their response by location. The only consistent thing is that whatever solution worked, it stopped working eventually.