Thank you @matteocontrini @tankerkiller125.
This was going to be my next question, around Vodafone being part of the problem, but I didn't want to take the Blomstra thread further off track (I've attempted to build a DNS service myself once to compare geoDNS and AnyCast DNS so I have some basic idea about how this works).
But to go back to the original concern from @matteocontrini, let me clarify Blomstra's use of Cloudflare (or any other provider for that matter).
We primarily use it only as a CDN to host static assets - so avatars, etc. which go on an S3 bucket would sit behind a CDN.
If a customer chooses to use a vanity name on one of our domains for their community, like blomstra.community (so, for example - somename.blomstra.community), we would route that via Cloudflare by default, but can turn it off should the customer be averse to using Cloudflare.
If a customer chooses to use an external hostname of their choice, like www.somecommunity.org, they will simply be pointing that domain at our load balancer(s).
So Cloudflare is not necessarily part of the architecture, and WAF like capability is not something we are adding to the mix for the time being.