Archive.today is having problems

[Nicholas II of Russia]

When I was working on the thread about Doobus Goobus, I noticed something weird. When I tried to archive some of the tweets that I garnered by looking up his Twitter account, I realized that all the links in Archive.today didn't work, I thought that the site was down for a couple of days. But then one of the mods reached out to me and told me that the page was working, and then someone else gave me all the other alternative links for the site and I tried all of them, and nothing worked, the connection just closes without a second thought.

The only one that worked was the Tor site, but only the homepage was available, because when I tried archiving, it got stuck on a loading loop. I had to use Ghostarchive to finish up the archiving part of the thread.

When investigating the issue, I read in some place on Reddit that the site got shut down by Cloudflare or something like that, not accepting the site, but that was in July of this year. And from what I recall the site worked perfectly fine since then, but only now it just refuses to work on my computer.

What is happening to the page? Is someone else having the same problem? Is there a way to solve this? I only hope that this is just happening to me and that it can be solved. Feel free to move this to the Spergatory if this is a stupid question.

 

[Seafarer]

Was it just the Twitter stuff that wouldn’t work?

I think someone in another thread mentioned a similar issue and iirc it’s something to do with some fuckery Musk is up to.

 

[Nicholas II of Russia]

Was it just the Twitter stuff that wouldn’t work?

I think someone in another thread mentioned a similar issue and iirc it’s something to do with some fuckery Musk is up to.

No, is not the Twitter stuff. My browser just refuses to connect to archive.today in its entirety. And I tried in other browsers and got the same result. I don't know what's causing it because the site worked just fine a couple of days ago.

 

[ToroidalBoat]

What if it is SJWs trying to sabotage it?

(because any incriminating stuff on them)

 

[BlueSpark]

You can't trust these archive sites anyhow: they routinely remove things upon request.

 

[Pee Cola]

When investigating the issue, I read in some place on Reddit that the site got shut down by Cloudflare or something like that, not accepting the site, but that was in July of this year. And from what I recall the site worked perfectly fine since then, but only now it just refuses to work on my computer.

I knew there was the distinctive smell of crotch rot in the air when archive.today started having problems about a month or so ago. I wouldn't be surprised if LFJ got in touch with Cloudflare and told them that archive.today is as much an "imminent threat to human" life as KF allegedly is.

Null should reach out and offer KiwiFlare to the archive.today guy.

You can't trust these archive sites anyhow: they routinely remove things upon request.

IIRC, the archive.today guy is a based Eastern European. You're thinking of the Wayback Machine, which was started by someone related to (((Taylor Lorenz))).

 

[Saddam Hussain Obama]

we need a backup of archive today asap

 

[Bitcoin Henchman]

No, is not the Twitter stuff. My browser just refuses to connect to archive.today in its entirety. And I tried in other browsers and got the same result. I don't know what's causing it because the site worked just fine a couple of days ago.

I can connect to the homepage and search through their archives just fine, maybe its something fucky with your dns or isp?

 

[Nicholas II of Russia]

I can connect to the homepage and search through their archives just fine, maybe its something fucky with your dns or isp?

That's what I thought too, if everyone is having archive.today without problems, then it's a personal issue I have with the site. I need to know if there is a solution somewhere, I can't find anything on Reddit or Google.

 

[Lone Wandering Courier]

I too often have issues with archive.today and I have no clue why.

 

[WhiteNight]

I've had problems connecting to archive.today such as getting into infinite captcha loops. What fixes it for me is refreshing DNS (either clearing cache or switching servers). Apparently some IP addresses are "bad" (or at least bad for some people).

Discussion on Hacker News:

https://news.ycombinator.com/item?id=37077049

 

[Faceless Whore]

I encountered a "Too many requests" error the other day which I thought was odd, but it's working for me again today. I always use Tor and haven't had problems with it except for this:

I've had problems connecting to archive.today such as getting into infinite captcha loops.

Happens to me too. When it does I use a different address, like archive.md or .ph and one of those has always worked.

 

[Lone Wandering Courier]

It doesn't matter which suffix I try, all captcha loops.

 

[Woodchipper]

It redirects to archive.ph for me. Working fine.
Edit:
Changing IPs redirected me to archive.md
Either way, I think we're gonna make it

 

[Geranium]

When investigating the issue, I read in some place on Reddit that the site got shut down by Cloudflare or something like that, not accepting the site, but that was in July of this year. And from what I recall the site worked perfectly fine since then, but only now it just refuses to work on my computer.

My browser just refuses to connect to archive.today in its entirety. And I tried in other browsers and got the same result. I don't know what's causing it because the site worked just fine a couple of days ago.

Try manually setting your computer’s DNS servers to 8.8.8.8 and 8.8.4.4 (Google public DNS).

Difficult to diagnose at a distance, but it sounds to me like you’re perhaps relying on your ISP for DNS resolution (which is typical if your machine or your router hasn’t had its DNS addresses set manually), and your ISP has switched to using Cloudflare as its resolver.

Archive.today returns bad results for DNS queries from Cloudflare, because the Cloudflare DNS servers strip out some (potentially identifying) information from your DNS query when they, in turn, query the archive.today nameservers.

 

[gateway]

I wouldn't be surprised if LFJ got in touch with Cloudflare and told them that archive.today is as much an "imminent threat to human" life as KF allegedly is.

What? Cloudflare has nothing to do with Archive.today. They have, in the past, blocked them from their DNS servers, but that's basically it.

Archive.today simply doesn't have the funds needed to cope with the volume of data, DDoS attacks, and regular traffic they encounter.

 

[Billy Stinkwater]

Archive has messed with cuckflare's 1.1.1.1 dns on and off for years because they strip out identifying EDNS subnet info.





The CEO of cuckflare had to put out a statement to say it's not our dns it's archive playing stupid games.

Cloudflare statement

We don’t block archive.is or any other domain via 1.1.1.1. Doing so, we believe, would violate the integrity of DNS and the privacy and security promises we made to our users when we launched the service.
Archive.is’s authoritative DNS servers return bad results to 1.1.1.1 when we query them. I’ve proposed we just fix it on our end but our team, quite rightly, said that too would violate the integrity of DNS and the privacy and security promises we made to our users when we launched the service.
The archive.is owner has explained that he returns bad results to us because we don’t pass along the EDNS subnet information. This information leaks information about a requester’s IP and, in turn, sacrifices the privacy of users. This is especially problematic as we work to encrypt more DNS traffic since the request from Resolver to Authoritative DNS is typically unencrypted. We’re aware of real world examples where nationstate actors have monitored EDNS subnet information to track individuals, which was part of the motivation for the privacy and security policies of 1.1.1.1.
EDNS IP subsets can be used to better geolocate responses for services that use DNS-based load balancing. However, 1.1.1.1 is delivered across Cloudflare’s entire network that today spans 180 cities. We publish the geolocation information of the IPs that we query from. That allows any network with less density than we have to properly return DNS-targeted results. For a relatively small operator like archive.is, there would be no loss in geo load balancing fidelity relying on the location of the Cloudflare PoP in lieu of EDNS IP subnets.
We are working with the small number of networks with a higher network/ISP density than Cloudflare (e.g., Netflix, Facebook, Google/YouTube) to come up with an EDNS IP Subnet alternative that gets them the information they need for geolocation targeting without risking user privacy and security. Those conversations have been productive and are ongoing. If archive.is has suggestions along these lines, we’d be happy to consider them.

 

[⠠⠠⠅⠑⠋⠋⠁⠇⠎ ⠠⠠⠊⠎ ⠠⠠⠁ ⠠⠠⠋⠁⠛]

The CEO of cuckflare had to put out a statement to say it's not our dns it's archive playing stupid games.

They're not 'stupid games'.

Cloudflare are cunts. They're proven cunts a hundred times over.

It is GOOD that people are harassing Cloudflare support to ask them why their DNS doesn't work, because they're cunts. Even if you know why Archive.today doesn't work with Cloudflare DNS, you should harass Cloudflare as to why their shitty DNS service is broken.

 

[AgendaPoster]

Some security suites seem to be blocking the sites. I tested in a VM. Dunno why and it doesn't show in the app reports, but I'd get a "the site closed connection" error with the av installed, no av, works OK.

 

[StyxHexenHamster1350]

They're not 'stupid games'.

Cloudflare are cunts. They're proven cunts a hundred times over.

It is GOOD that people are harassing Cloudflare support to ask them why their DNS doesn't work, because they're cunts. Even if you know why Archive.today doesn't work with Cloudflare DNS, you should harass Cloudflare as to why their shitty DNS service is broken.

And to make matters worse, whoever configured Archive's Tor address (http://archiveiya74codqgiixo33q62qlrqtkgmcitqx5u2oeqnmn5bpcbiyd.onion/) pointed it at the cloudflare frontend, which is completely wrong, and causes all the Tor visits to first go through cloudflare, which typically tries to block Tor users.

Tor addresses should ALWAYS point at the actual server IP, bypassing clownflare.

Pointing a Tor address to cloudflare breaks things.