OK, so I finally found the bug that caused the crash in ckdb about a week ago.
I'll do a restart of CKDB in about 50minutes with that bug update.
As usual, no miners will be affected by the ckdb restart.
I'll do it at the first shift summarisation after 07:00 UTC (which should be around 07:20 UTC)

This will mean that I'll actually make the web event blocking code more active also after I've done the update.
Due to the fact that it could crash when I checked the events, I've only enabled a few 'major' event blocking items.
After this I'll enable the more noticeable event blocks - like too many access to certain pages and many others that have been disabled.
However, after the first time when I manages to lock out a lot of users, I'll use the info I worked out then to minimise that happening.

Sigh, greater than 500% ... ok lets see if a ckdb restart can help