&&
Not sure of the reason why .IS is not recommended, probably something to do with geo-political baggage.
As far as I know, the reason some people don't want to host there is that ISNIC is known to revoke domains when a site violates the law.
https://en.wikipedia.org/wiki/Help:Using_archive.today#Archi...
"The owner of archive.today requests Wikipedia always use archive.today - it is a gateway that redirects to one of the final destinations (.is, .li, .fo, .ph, .vn and .md) based on load and availability. It provides archive.today flexibility to dynamically redirect traffic to other domains/servers."
So I'd go with archive.today until the site owner specifies something different. I'm not totally sure why the domain is necessary for load balancing, but if OP is having trouble with queue depth, maybe try archive.today
https://en.wikipedia.org/wiki/Archive.today#History
https://twitter.com/archiveis/status/1081276424781287427
They started deprecating archive.is in 2019.
While I'm sure some abuse the service, the long queue could be just a side effect of them being more popular now than they used to be. I find myself using them, archive.org, and Google cache more now because of geo blocks and/or pages that are hard to view.
I've assumed that the root cause is the Russian aggression/war/invasion.
https://blog.archive.today/ is perhaps are good place to ask that question.
(I've somehow gotten the impression the person running this service is either in Russia or at least russian.)
From what I read, this attempt to erase history was cited by one of the financial backers who was supposedly not a fan of KF, but was less of a fan of censorship from utilities such as archive.org.
As John Gilmore famously said "The Net interprets censorship as damage and routes around it."
12ft.io (or whatever it is) stopped working too. Probably to not get sued.
This whole thing feels like a sign that a new tech solution could solve this once and for all. Distributed hash tables have been a thing since the 90’s. Making it work well for bypassing paywalls would be hard to stop.
The real problem is account walls. Because a good micropayment system hasn't been adopted yet, every goddamn news outlet insists that I sign up for an account, give them my credit card, and commit to a monthly payment. There's too much good content on competing outlets and platforms to deal with all that paid account management. I'll read maybe half a dozen NYT articles a year, and similar from dozens of other outlets. Let me just pay for what I want to read without signing a long term contract.
This isn't just a problem with news outlets. Every kind of digital content is like this. I don't want a dozen different paid accounts on all the different streaming services. Let me pay a quarter for each show I watch and stop this "gym economics" crap of relying on the very low use customers to subsidize the high use customers.
I suppose if a singular NYT article dropped that took the effort and expense of writing a full book, and there was enough chatter about it to vouch for the quality, then sure, I would be fairly likely to pay that much, if and only if it was a one time exchange and did not require setting up a long term subscription relationship.
tl;dr - queue position is meaningless if you don’t know the throughput
*not the exact number - it was in the 2700s, but that’s all I recall