Ask HN: What's Up with Archive.today?

Archive.[today|is|ph|il|md|etc.] has been unresponsive for the last few days.

I've searched around a bit but haven't seen any reporting as to what's up with the site(s).

Does anyone have any information about this? Speculation? Wild rumors?

4 points | by nobody9999 9 hours ago

4 comments

  • cpach 1 hour ago
    Works fine for me. (Sweden, tried on my smartphone using LTE connection.)
  • gnabgib 7 hours ago
    Looks fine (bonus, you have your own Archive page)

    https://archive.is/93mjz

  • al_borland 8 hours ago
    I used .ph earlier today and it worked.
  • nobody9999 9 hours ago
    I'd add that every so often I get a "Welcome to nginx" page instead of just a time out.
    [-]
    • Bender 8 hours ago
      Who are you using for DNS? If Cloudflare there is a long running squabble between Archive's admins and CF as CF refuses to forward EDNS Client Subnet information and so they return bogus information to Cloudflares servers. Their admin has accounts here but they rarely interact and seem to keep creating new accounts.

      It responds fine for me but I am using my own DNS server that talk directly to the root/tld servers.

      Here are some other public DNS servers. [1] ...not my site

      Alternatively use 107.189.8.227 in your hosts file for each of those names for now though it does change.

      [1] - https://dnschecker.org/public-dns

      [-]
      • nobody9999 7 hours ago
        >Who are you using for DNS? If Cloudflare there is a long running squabble between Archive's admins and CF as CF refuses to forward EDNS Client Subnet information and so they return bogus information to Cloudflares servers. Their admin has accounts here but they rarely interact and seem to keep creating new accounts.

        DNS resolution is not the issue. Like you, I use my own recursive resolver and the various archive.[today|il|is|ph|etc] sites all resolve without issue, but weirdly MXToolbox[0] resolves those hosts to a different IP address.

        I suppose my ISP could be intercepting my recursive queries, but that seems unlikely as I've never detected a dns proxy before.

        I'll do some more investigating and, if it is my ISP, I've been looking for a reason to dump them anyway.

        [0] https://mxtoolbox.com/DNSLookup.aspx

        [-]
        • Bender 7 hours ago
          The IP will be different depending on where you are making the query from. Try adding that IP I listed to hosts and see if it starts working. It could be one or more of their nodes are down.