May 6, 2026 at 1:24 pm
We suffered a SPAM attack from May 1-6, which unfortunately corresponded with time off for lots of IT staff, including a Monday holiday. We declared an incident early on 6 May and started working on the problems. We have taken the following actions, which may disrupt some legitimate users, but hopefully few:
We will be continuing to try and add some defenses agaisnt this and clean up SPAM As we find it.
Our apologies for any interruption and hopefully we have minimized the problem
May 6, 2026 at 2:26 pm
One way or another, they're still at it

May 7, 2026 at 1:15 pm
I reported one as SPAM this morning, as well.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2026 at 2:19 pm
The system just got rapid fire blasted by mulitiple (didn't count them) spams.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2026 at 7:07 pm
Yeah, there have been multiple attacks. I got over 200 spam article submissions as well that I had to delete.
We're working to identify some patterns, like WGET/CURL posts and block them. I was told we are also standing up an AWS WAF (firewall) that can do some packet inspection for patterns and block things before the web/db servers have to see them
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply