"Having to do" is not so direct here.
Absence of EDNS and massive mismatch (not only on AS/Country, but even on the continent level) of where DNS and related HTTP requests come from causes so many troubles so I consider EDNS-less requests from Cloudflare as invalid.
taking some sort of philosophical stand, so rather than wait for that, I just created a static entry on local DNS resolver. "54.36.225.114 http://archive.is" You could add to your hosts file instead if you don't have local DNS.
This seems odd - you're blocking a massive amount of users from accessing the site with no explanation of why it may be breaking. Not even a redirect to an http explainer page on http://archive.is. Took me a while to figure this out and I'm technical. Most people: no hope
This deliberate decision on your part is concerning. Is there are problem that arises when you are unable to route some users to the nearest edge? I'm failing to see why this warrants such an extreme retaliation.
Extremely disappointed that Cloudflare DNS users continue to be blocked from http://archive.is - hopefully you guys will get a less stubborn competitor soon!
Hey it's been almost two years and this is still an issue. No other site I've encountered refuses to provide failover in this situation. You seem to be quite alone on this.
What are the troubles specifically? I would like to help patch a more graceful approach if possible.