This may be picking up a problematic pace.
Have seen what I suspect is Ai enabled Bot traffic that was closing in on DDOS level disruption as the discourse service was starting to complain.
Not a highly powered setup but for expected normal demand there is some headroom, normally.
This time it showed up as huge anonymous traffic and other.
This mapped perfectly to the increased server CPU, Load and Disk I/O stats.
As a user here I got a lot of flak and many (temp) bans for de-crying the wildly enthusiatic adoption of Ai, which is now well and truly coming back to bite in so many ways (like job losses, but and now this, which may be a continuum of the OP and is nothing but the latest AI enabled web bot traffic making itself known, oh boy.
Back then my view was it was (also) the time to be thinking about all strategies to mitigate for the customer/end user, not simply joining the arms race as a sub partner, that Musk style of logic is if you can’t beat ‘em join is in this instance, easy to say, but not the correct option and the call for regulation nieve.
Stand back?
Maybe too late now.
The AI traffic may come in more human-like: technically I do not know how that works (but i know how we got here) other than it probably passes itself off as human traffic more easily and presents a more un-detectable traffic that also looks desirable from google point of view, but oh dear, this may be a bigger new problem.
Nothing is ever FREE I dunno how many (again) got so blindsided by this and did not apply human level caution and choose a stand back option.
Right now that traffic still comes in from very specific regions and even ASN block are enough to surgically take out the heat.
For how long?