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 think of Cloudflare as the Mos Eisley of the Internet. Cloudflare has made the decision that getting paid for hosting abuse (spammers, spamvertized content, etc.) is preferable to turning that business away to other providers...because let's face it, if Cloudflare doesn't host the content, someone else will get paid to host it. Also, I find it amusing that Cloudflare appears to be hosting someone/something that presumably is sending spam masquerading as *.googleusercontent.com. googleusercontent.com (i.e. Google Cloud) seems to have a serious spammer infestation that they either can't or won't do anything about. Initially, I thought it might be an exploit of some commonly used software across different customers, but I've seen enough now to hop to the conclusion that it's just a spammer abusing random 3rd party domains in their from addresses. i.e. spams claiming to be from support@amazon.com, support@linux.org, support@wikipedia.org. Coincidentally, I got tired of seeing their spam today and wrote a custom Spamassassin rule to start blocking it at SMTP time. ---------------------------------------------------------------------- Jon Lewis, MCP :) | I route Blue Stream Fiber, Sr. Neteng | therefore you are _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________