What's Been Going on with Archive.today?

Question

It&rsquo;s been months and I&rsquo;m still confused what&rsquo;s going on with it.It often used to redirect to other TLD (ph, is&hellip;).More recently it seems to be not-happy with iCloud Relay connections and it either cannot be reached or gets in a reCAPTCHA loop.

WarOnPrivacy · Accepted Answer

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.

bombcar · Answer

The operator wants to ensure that all archives occur across a country boundary, so that any takedowns have to be an international affair.And as such cloudflare DNS doesn&rsquo;t work with it for some reason

biglyburrito · Answer

Yep, I was unable to use it for at least a month due to reCAPTCHA infinite loops, so I stopped using it.

KomoD · Answer

> More recently it seems to be not-happy with iCloud Relay connections and it either cannot be reached or gets in a reCAPTCHA loop.iCloud Relay might be using Cloudflare's DNS, which is why it won't work.

Skotyanets · Answer

as I can grasp its blacklisted, at least such spin was present even earlier in various countries, but now the western realm is mids vast agitprop psyop thus having service where every content member can archive its work its guess risk for the a.i. bots in chase for deepfake overrun of unpleasant news for the euroatlantic realm!?, one can save even archive.org links in archive.is so guess that is additional motivation for the blacklisting!anyway I can still reach it through TOR Browser with some push pull with the captcha (asks for patience) lets hope euroatlantic authorities will drop their fears and reopen the doors, yet knowing that the war in the fifth realm for them is huge issue so not sure whether that will happen soon!?, pity coz in effect there is no other service where one can get address string for the quoted part in some page i.e. its useful for fast footnoted communication of various quotes and links in same post ...

josephcsible · Answer

The operator of that service seems to be opposed to privacy. Those failures are intentionally caused when it detects certain privacy-respecting configurations, e.g., use of a DNS resolver that doesn't send EDNS Client Subnet information.

What's Been Going on with Archive.today?

It’s been months and I’m still confused what’s going on with it.
It often used to redirect to other TLD (ph, is…).
More recently it seems to be not-happy with iCloud Relay connections and it either cannot be reached or gets in a reCAPTCHA loop.

The operator wants to ensure that all archives occur across a country boundary, so that any takedowns have to be an international affair.
And as such cloudflare DNS doesn’t work with it for some reason

Yep, I was unable to use it for at least a month due to reCAPTCHA infinite loops, so I stopped using it.

> More recently it seems to be not-happy with iCloud Relay connections and it either cannot be reached or gets in a reCAPTCHA loop.
iCloud Relay might be using Cloudflare's DNS, which is why it won't work.

The operator of that service seems to be opposed to privacy. Those failures are intentionally caused when it detects certain privacy-respecting configurations, e.g., use of a DNS resolver that doesn't send EDNS Client Subnet information.