The archive.today website is certainly a webapp. Questions about quirks, bugs and peculiarities in gmail, facebook, youtube, twitter, google-search, github, dropbox, reddit, and many other websites, are all on-topic here (per my understanding — please correct me if I'm wrong), so, it's unclear what makes you judge archive.today any differently, and why its unavailability with Cloudflare dns is somehow offtopic. In fact, we even already have archive.org tag with 24 questions, as early as early as 2010 (due to incoming migrations). How's archive.is any different?!
Likewise, it can also be argued that 220.127.116.11 itself is a webapp as well (this is where we get a bit of an intersection with some other sites on SE network), however, this question is very specific about archive.today, and doesn't go into the whole performance and other reasons around 18.104.22.168, so, it's definitely on the WebApps side.
And which exact agenda is being advanced? What exactly are you alleging here? Are you doubting that StackExchange voting is fair and balanced, in this very specific case, but in no other cases?
If anyone disagrees with the question or the answer, they're free to downvote. The number of upvotes greatly exceeds the number of downvotes; even with alternative answers available, which haven't gotten quite as many votes even after being posted around the same time, and I think this proves that my original question and answer pair are neutral enough.
The issue of archive.is not resolving through Cloudflare comes up every now and then, without any good answers. I had a genuine desire to explain and document in a neutral way what it's all about. Hence the QA. (As has been pointed out, StackExchange encourages you to ask and answer a question in one go — in fact, you can provide an answer to your own question right away before even publishing the question itself, e.g., publish a QA as an atomic pair.) I believe this question is most on-topic at WebApps, and IS, in fact, actually fully ontopic here, too, because the primary subject and usecase being a web-app — archive.is. I am not affiliated with archive.today in any way, either, although I do think it's a pretty cool service.