I usually use Chrome. My PC was having issues but later on my laptop I had no issues. Both have been updated recently for Chrome. I haven't had a chance to check the PC again.

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:147.0) Gecko/20100101 Firefox/147.0

I'm on Opera (v95.0.4635.90) on my old Windows 7 laptop - Opera stopped Windows 7 updates some years back so it's fossilised. Have had no real problems today - some sluggishness but no more than what can happen whenever for whatever reason.

IF you still have the error, try closing your browser and opening it again. It probably has put in your session the info that you are a bot

Crap, it seems that my new filter is a little too wide
- What browser do you use?
- What identifier is returned when you visit this page: http://ksle1.antp.be/user-agent.php ?

I first blocked all what contained "Safari/537.36" but it seems that even if this is an outdated version of Safari, actually many Chrome-based browsers report that info.
So I widened it to those containing ".0.0.0 Safari/537.36" and ".0.0.0 Mobile Safari/537.36" but at least Edge seems to have that.
So I need your input.

Blocking this should be safe, I hope:
'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/11',
'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/10',

I'm getting the "Bots/crawling message" on any page except the main page

Guessed I spend too much time on site today? :(((

One page said:
This page is not available for bots/crawling. Please follow the robots.txt file. Contact us at contact@imcdb.org for more information.

The other page said:
The server is too loaded for the moment, please come back later. Contact us at contact@imcdb.org for more information.

There was a new bot not identifying as a bot that was scraping the site, causing slowdowns in the last hour.
It is using fake browser user agent, with old version numbers.
For now I blocked it (and for a few minutes maybe most of the non-Firefox browsers, sorry )

Probably more bots than usual indeed. I'll check the logs tomorrow.

Seems to be working, so there must have been a nasty bot running at the time.