5 ms·
I'm sick of it too. In 2023-01 alone I have had 9,000 different IPs from Microsoft's ASN8075 crawling one of my sites with these "normal looking" user agents. P
by aorth 4y ago
I'm sick of it too. In 2023-01 alone I have had 9,000 different IPs from Microsoft's ASN8075 crawling one of my sites with these "normal looking" user agents. Poring over the logs to see why your server is on fire takes non-trivial amounts of time. If I didn't have a ton of other stuff to do I'd say it was kinda fun, but I'm freaking fed up.
Just yesterday I put all their networks into an nginx geo map:
geo $limit_bots_ip {
# requests with an empty key are not evaluated by limit_req
# see: http://nginx.org/en/docs/http/ngx_http_limit_req_module.html
default '';
157.55.39.0/24 'bot';
207.46.13.0/24 'bot';
40.77.167.0/24 'bot';
13.66.139.0/24 'bot';
...
}
Any request from these networks gets classified as a bot, which is then used as the key for a rate limit
limit_req_zone $limit_bots_ip zone=badbots_ip:1m rate=1r/m;
It's incredible the amount of resources these companies have. I'm just one guy trying to keep a few dozen web servers up.
- gggggg5 4y agoWouldn't it be easier to fix whatever issue is causing your server to be on fire than spending non-trivial amounts of time poring over logs?
- adammarples 4y agoGood idea, debug it without looking at the logs, to save time
- gggggg5 4y agoIt's one thing if your server is on fire because of a bot crawling your websites at 1000rps, another if it's on fire because of a bot crawling it at less than 10rps.
- taskforcegemini 4y agothink of it as a ddos. how do you fix a ddos in your application?
- gggggg5 4y agoThe request rates being discussed here are nothing like a DDoS.