Ask HN: What Happened to Archive.is?

5 points by camillomiller ↗ HN
Seems like it's unreachable as of today.

4 comments

[ 2.4 ms ] story [ 58.2 ms ] thread
I imagine (hope) that it's just some config hiccup, and not CloudFlare decided to yank them from the clearnet (nor something similar).

It is working on the tor network.

I'm worried it could be something like that. Try Archive.ph...

EDIT: now just giving a random "unable to reach" error. I got a cloudflare alert before.

try other DNS providers as sometimes cloud flare has been in a fight with them
> cloud flare has been in a fight with them

I take minor issue with this wording. Rather than saying CloudFlare has been in a fight with them, I'd say they've been in a fight with CloudFlare. Specifically, CloudFlare chose not to implement an optional feature of DNS that's bad for privacy (EDNS Client Subnet) in their resolver, and archive.is responded by configuring their authoritative nameserver to refuse to return correct results to such queries.