Does it give a reason for the block? I know ISPs in a couple of countries⁰ (China for one) block it, as do many corporate networks that subscribe to certain blocklists¹, but I've not heard of the site itself blocking specific groups of connection attempts.
Unwall might be a useful resource, though it appears small so I wonder how long it will last. The source code links are dead ends (his profile still exists on github, but that repository does not and a quick search doesn't find evidence that it has move elsewhere) - this could imply that take-down orders have already started flying and are having an effect.
--------
[0] Because it gives access to content otherwise blocked
[1] Because it gives access to content otherwise blocked, or because of the DDoS and other arseholery² in Jan 2026, or both
[2] including altering archived pages that make reference to, or altering them to make reference to, the target of that DDoS
Some ISPs in Finland have blocked it from resolving for copyright issues, but even if you get it to resolve by changing DNS servers, it goes into a Cloudlare CAPTCHA loop. I assume it's still about the spat with a Finnish blogger.
For us banned by archive.is: https://unwall.app/www.nytimes.com/2026/08/13/travel/solar-e...
Does it give a reason for the block? I know ISPs in a couple of countries⁰ (China for one) block it, as do many corporate networks that subscribe to certain blocklists¹, but I've not heard of the site itself blocking specific groups of connection attempts.
Unwall might be a useful resource, though it appears small so I wonder how long it will last. The source code links are dead ends (his profile still exists on github, but that repository does not and a quick search doesn't find evidence that it has move elsewhere) - this could imply that take-down orders have already started flying and are having an effect.
--------
[0] Because it gives access to content otherwise blocked
[1] Because it gives access to content otherwise blocked, or because of the DDoS and other arseholery² in Jan 2026, or both
[2] including altering archived pages that make reference to, or altering them to make reference to, the target of that DDoS
Some ISPs in Finland have blocked it from resolving for copyright issues, but even if you get it to resolve by changing DNS servers, it goes into a Cloudlare CAPTCHA loop. I assume it's still about the spat with a Finnish blogger.