Re:You don’t want to be on Cloudflare’s naughty list
by judge2020 on Tuesday September 20, 2022 @11:09AM
(#32912757)
The point is that Cloudflare does not beam IP reputation data to Google. If Google and CF are blocking this IP separately, what's the chance there's some malicious device or hacked IoT device on the network, participating in DDOS attacks or unauthorized vulnerability scanning of random websites?
[ Parent
| on HN ]
Re:You don’t want to be on Cloudflare’s naughty list
by pessimizer on Tuesday September 20, 2022 @01:01PM
(#32914625)
According to another comment, it's a wrong point: https://blog.cloudflare.com/cleaning-up-bad-bots/
> Once enabled, when we detect a bad bot, we will do three things: (1) we’re going to disincentivize the bot maker economically by tarpitting them, including requiring them to solve a computationally intensive challenge that will require more of their bot’s CPU; (2) for Bandwidth Alliance partners, we’re going to hand the IP of the bot to the partner and get the bot kicked offline; and (3) we’re going to plant trees to make up for the bot’s carbon cost.
Re:You don’t want to be on Cloudflare’s naughty list
by judge2020 on Tuesday September 20, 2022 @01:22PM
(#32914905)
I'm pretty sure this was for a situation like Digitalocean themselves hosting a bot, but such IP sharing very well might be currently (ab)used by partners, if it's happening here.
Re:You don’t want to be on Cloudflare’s naughty list
by jgrahamc on Tuesday September 20, 2022 @01:06PM
(#32914680)
Yeah. I'm looking into that.
Re:You don’t want to be on Cloudflare’s naughty list
by zinekeller on Tuesday September 20, 2022 @11:22AM
(#32912974)
Yeah, if for example Spamhaus (which both Cloudflare and Google consult) has detected that a subnet is bad then that could be the cause.
Still, it doesn't excuse Cloudflare that there's no redress if you are caught on a block or even a clue on what you can do to reduce it (especially that Spamhaus do have redress procedures).