Still working fine here.

I see you have noticed this has happened before, I did recall the same when I saw this ... the bottom post talks about too many requests - if not your many visits, probably shared IP pool or something.

It always gave me a sketchy vibe, I try to rely on the Internet Archive whenever possible.

(Some publishers whitelist their bot, since it is used for scholarly citations -- I'm not clear how a reviewer would review to an archive.is link and despite having been out of academia for a decade, old habits die hard.)

Also, how are you accessing the site? Are you sure the error stems from the destination?

I've never had what you describe happen but I have had some... interesting... errors pop up when doing OSINT in Tor.

(Ex: a SSL_ERROR_UNSAFE_NEGOTIATION when attempting to access the copy of a search warrant that was served on a state senator from a government website specifically set up to make such documents available.)

archive.today's DNS is unreliable garbage.

They take issue with Cloudflare not sending EDNS Client Subnet and lately I've noticed they've taken issue with NextDNS' anonymized EDNS.

Gives shady data-collection vibes.

I remember reading this may be a rate limiter or DDoS protection behaviour

works for me, would be interesting to see what IP addresses it is redirecting for you, hopefully you are not using a malicious/compromised DNS server?

archive.today, archive.is, and archive.md are all working correctly for me now.