Conversation

Moved to a new floating IPv4 address for mail.grapheneos.org so Microsoft blacklisting the previous one is no longer an issue. It's only $2.88 CAD + 13% sales tax for each address so we're just going to park ones with bad routing or blacklisting issues for the time being.
2
7
The 3 particularly problematic IPv4 addresses we've gotten are from the same 51.222.17.0/24 block. I'm just going to retire them and get OVH to replace them with new ones because they're something seriously wrong with that IP block. Every other IP address has way saner routing.
3
6
Replying to
OVH is (used to be?) pretty relaxed about abuse reports, there is a pretty long history of abuse that lead to many of their blocks getting blacklisted in e.g. DNSBLs. Usually only individual /24s were blacklisted if repeat offenders used them.
1
Replying to
That's completely fine though because every reasonable blacklist allows you to get an individual /32 whitelisted despite them blacklisting the /24. It doesn't take much time to get all the legacy stuff cleaned up. UCEPROTECT extortionists are an exception but it doesn't matter.
1
1
Replying to and
We use a free service to monitor for IP or domain blacklisting. Never had issues with the domains and IPs were easy to keep clean for everything other than UCEPROTECT /24 and AS. Recently changed when our new VPS IP + batch of new floating IPs were all blacklisted by Microsoft.
1
Replying to and
Put substantial effort into trying to appeal the bans through their official form and the email follow-up. It was a huge hassle to even get a standard copy paste response from them saying that the IPs are not eligible for whitelisting. It's now resolved by just using new IPs.
1
2