2 ms·
Who was to blame again? I think I remember a cloudflare rep comment that they had tried to get this resolved with the site owner.
by Gigachad 5y ago
Who was to blame again? I think I remember a cloudflare rep comment that they had tried to get this resolved with the site owner.
- 22c 5y agoIt's explained here: https://community.cloudflare.com/t/archive-is-not-accessible/240133 https://community.cloudflare.com/t/archive-is-not-accessible... and here: https://news.ycombinator.com/item?id=19828317 https://news.ycombinator.com/item?id=19828317 Who is to "blame" is up to you, but the archive.is operator is (was?) specifically not responding to CloudFlare DNS requests. It is intentionally "broken" on the archive.is side.