I'd add that every so often I get a "Welcome to nginx" page instead of just a time out.

Qision 10 minutes ago | parent | next [-]

I'm facing the same problem with my normal internet access but I just tried through Tor and it works fine. Hope this helps!

Edit: I just noticed that the Tor browser indicates a .onion version of the website is available and it works perfectly.

▲

Bender 12 hours ago | parent | prev [-]

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 11 hours ago | parent [-]

>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

	▲	10 hours ago \| parent \| next [-]
		[deleted]
	▲	Bender 10 hours ago \| parent \| prev [-]
		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.