On Thu, 17 Sep 2026, Seth Mattinen via NANOG wrote:
On 9/17/26 14:08, Jon Lewis wrote:
On Thu, 17 Sep 2026, Seth Mattinen via NANOG wrote:
Cloudflare has IP ranges all the way up on the Spamhaus DROP list. Cloudflare says they cannot control this.
172.70.206.0/23 (Spamhaus SBL687772) 512 addresses 172.70.214.0/23 (Spamhaus SBL687314) 512 addresses
Is Cloudflare in a "might makes right" position, or should someone be working to resolve the issues causing the SBL?
These are your only complaints with Cloudflare hosting?
I don't have a complaint. A customer brought this issue up, so I am just curious how everyone feels about things like this today. The customer feels one way since they pay Cloudflare (it's not me).
I'm in the middle because I've used the DROP list for well over two decades as a border filter, before companies like Cloudflare were founded, but over time if the DROP list ends up full of "too big to care" listings, then that makes its utility less than what it once was.
Ah, so you and Cloudflare have a mutual customer being impacted by their use of a Cloudflare IP in one of those ranges? Have you suggested that they complain to Cloudflare and suggest to Cloudflare that they "clean up their network" and reputation? Assuming the listings are legitimate, I don't see how the IP space belonging to a "too big to care" network makes DROP any less relevant. Would you really want Spamhaus to make exceptions and turn a blind eye to abuse hosting for the top hosting providers? That seems like it'd make DROP less effective/useful. But that's only if the listings are legit. ---------------------------------------------------------------------- Jon Lewis, MCP :) | I route Blue Stream Fiber, Sr. Neteng | therefore you are _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________