Yes. For me, I found that I changed my DNS server to Cloudflare with the AdGuard software installed on MacOS a while back (AdGuard > Preferences > DNS), and changing this to a different server fixed it.

I also used the command `sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder` on Terminal (double-check this command before using) to flush the DNS cache, so the change would immediately take effect with the archive websites.

This is a separate issue from the previous Cloudflare issue and it manifests differently.

Getting Captcha'd happens with non-cloudflare resolvers as well, tho not universally nor consistently.

I forced all of Archive domains to query against Quad9 and started getting unskipable Captchas months ago - when I was local(US).

When I placeshifted to overseas, Quad9 resolved to different IPs and those were usable.

The technical reasons behind it are that the archive.today guy wants any takedown notices to be cross-border, so he wants to know what country you are in so he can redirect you to a server outside it.

Cloudflare doesn't support a DNS extension that allows this (eDNS maybe?) and so it fails.

Captcha pages are being served at IPs that don't come from CloudFlare. ex: Users who exclusively resolve thru Quad9 are getting Captcha pages.

Any inference that the Captcha issue is limited to CloudFlare users is incorrect.