Live data from Hacker News

Archive.today is directing a DDoS attack against my blog

gyrovague.com

21–30 of 187 posts

Re: Archive.today is directing a DDoS attack against my blog

#21
post #19

Earlier quoted context omitted.

I don't think there's any dispute on what the story is. The blog post here contains the facts, and a rather clumsy attempt by Gyrovague to justify his bid to dox the operator of archive.today. > Archive.is has more money, resources and ASN's than Akamai I assume this is a joke, but Archive.is is a shoestring operation funded through donations.

I assume this is a joke, but Archive.is is a shoestring operation funded through donations. I am certain they would like people to think that. They have more IPv4 addresses under more ASN's than Akamai control which anyone who has tried to block them would know. Their controlling ASN's are in the Russian Federation which they make no attempt to hide at least for now and why I must assume they are fine with people dis…

Yes, it's apparently hosted behind some fastflux setup. That's neither new nor special, nor is it particularly expensive. Such setups are offered on various forums starting from a few hundred dollars a month.

> Their nodes both in Russia and spread all around the world would not be permitted by Russia to mirror random sites without authorization to do so.

This is simply not true. You can absolutely run a website like this in Russia without any authorization. Who would you even ask? The whole idea is bizarre.

Re: Archive.today is directing a DDoS attack against my blog

#22
post #19

Earlier quoted context omitted.

I assume this is a joke, but Archive.is is a shoestring operation funded through donations. I am certain they would like people to think that. They have more IPv4 addresses under more ASN's than Akamai control which anyone who has tried to block them would know. Their controlling ASN's are in the Russian Federation which they make no attempt to hide at least for now and why I must assume they are fine with people dis…

Yes, it's apparently hosted behind some fastflux setup. That's neither new nor special, nor is it particularly expensive. Such setups are offered on various forums starting from a few hundred dollars a month. > Their nodes both in Russia and spread all around the world would not be permitted by Russia to mirror random sites without authorization to do so. This is simply not true. You can absolutely run a website like…

You can take what I said out of context. Apparently OSINT are on it, not my problem.

Re: Archive.today is directing a DDoS attack against my blog

#24

previously https://news.ycombinator.com/item?id=46624740

Macroexpanded: Ask HN: Weird archive.today behavior? - https://news.ycombinator.com/item?id=46624740 - Jan 2026 (69 comments)

I cannot make head or tail of this but it's more fascinating than the usual internecine bloodbath.

Re: Archive.today is directing a DDoS attack against my blog

#25

Why is this flagged? Given the content, I find this suspicious.

I looked at the flags and they seem to be legit flags from legit users. My guess is that they thought this was below-the-radar drama that wasn't on topic for HN. (I could make a "people who flagged X also flagged" list a la https://news.ycombinator.com/item?id=46771900 to support the point, but it's a time-consuming pain so I'd rather not!)

Edit: after looking at this more closely, I have a counterintuitive (to me at least) take: I think this is interesting enough to transcend the usual categories. That is, we'd normally downweight this kind of post off the frontpage - but in this case there are so many unusual variables that the usual rules don't apply.

I say this despite having zero clue what's going on here. We do have a nose for what the HN community might find interesting (we'd bloody well better after doing this job for so long), so let's override the flags and see what happens.

But without relitigating WWII please.

Re: Archive.today is directing a DDoS attack against my blog

#26
post #17

Earlier quoted context omitted.

Like I said, I can't tell who is attacking who. Archive.is has more money, resources and ASN's than Akamai so surely they can mitigate anything anyone can throw at them. A little forum trying to respond in kind can't really be much of a threat. Archive could just tell their controlling nodes to ignore any requests to mirror the forum which means there is a lot more to this than any of us are seeing. That is why I wou…

I don't think there's any dispute on what the story is. The blog post here contains the facts, and a rather clumsy attempt by Gyrovague to justify his bid to dox the operator of archive.today. > Archive.is has more money, resources and ASN's than Akamai I assume this is a joke, but Archive.is is a shoestring operation funded through donations.

Hey guys - you both obviously know a ton more about this than I do, but this is the point at which the thread went off the rails. I get that you disagree with each other and that's fine, but please stay within the site guidelines while doing so: https://news.ycombinator.com/newsguidelines.html.

Re: Archive.today is directing a DDoS attack against my blog

#27
post #25

Why is this flagged? Given the content, I find this suspicious.

I looked at the flags and they seem to be legit flags from legit users. My guess is that they thought this was below-the-radar drama that wasn't on topic for HN. (I could make a "people who flagged X also flagged" list a la https://news.ycombinator.com/item?id=46771900 to support the point, but it's a time-consuming pain so I'd rather not!) Edit: after looking at this more closely, I have a counterintuitive (to me at…

This is definitely interesting and HN-worthy. If nothing else, archive.today links are posted on tons of HN submissions, so it's topical.

Re: Archive.today is directing a DDoS attack against my blog

#28
It is academically very interesting to think about this in light of their long-standing dispute with Cloudflare (https://community.cloudflare.com/t/archive-is-error-1001/182...) over EDNS, which could have privacy implications attached.

I think no matter how you slice it though, it's unethical and reprehensible to coordinate (even a shoddy) DDoS leveraging your visitors as middlemen. This is effectively coordinating a botnet, and we shouldn't condone this behavior as a community.

Post reply on HN