Originally Posted by
HDQDD
I actually sent FT feedback on that a few years ago. They were nice about it, basically said it's their hosting provider who does that. They offered to try to work with me to whitelist the address I was coming from, but it was one of the large VPN providers, so as I explained to them: there's no way to reliably do that since they have hundreds, if not thousands of endpoints.
I do find it a bit ironical that a *travel* website blocks known VPNs.

For many of us, a VPN is a must when using public wifi.
Given Cloudflare’s use by some larger and smaller sites haven’t been rejecting what FT rejected/rejects at the same time as Cloudflare’s use on this site, there seems to be something about FT that comes with more VPN blocking than typical for Cloudflare-using sites.