Hacker News new | ask | show | jobs
by berg01 2515 days ago
Seems like archive.is is using DNS-based load-balancing/fail-over. My best guess is that the person/group that's running archive.is is having some operational issues right now and you caught that issue.

For the record: from GCP (using default resolvers, e.g. Google) region europe-north1-a... archive.is resolves to 46.45.185.30.