It’s been a while since I’ve made these type of posts but there’ll be a server maintenance that will (hopefully) address the recent Lemmy-UI problems.
edit: I’m going to cancel this because the problem has been solved by blocking excessive crawling/scraping bots. No more crashing and zombie processes.
Whoa. Was there anything else going down in that time frame? I’d be interested to have some profile on the attacker. Do you have any information about where the majority of ani.social’s traffic came from before that?
Nothing else went down. After blocking the ASN, I found out that they’ve been scraping the site from Hong Kong too but not as aggressively with Singapore. Or rather, the Hong Kong servers are more consistent but not as
frequentbursty (I don’t know how best to describe it lol). The only info I have is the ASN which points to the Alibaba Group. It also doesn’t disclose what it is other than “Microsoft Edge Windows” which is not very nice in my opinion.Cloudflare only gives me logs for the past 24 hours but most of ani.social’s traffic comes from other instances federating in (unsurprisingly, Lemmy.World is #1).
Some graphs if you're interested:
The green line is Singapore. This happened a few hours after the crash the other night.
This is a closer look of the spike. The lines are 5 of their IP addresses. You can see that they’re dormant then suddenly they start hammering the instance with requests.
These are the top countries for the past 6 hours that use GET after filtering out Alibaba. United States is high because they have a lot of web crawlers/scrapers like Open AI (at least they’re honest) but I might block the AI ones too.
I’d almost be concerned that it’s a nation state at that point.