@aeva
Yeah, I don't suspect a standard route would be affected by this kind of block. This is explicitly tied to VPN routing checks, and the reason I find this so odd.
I can only assume someone has put in a rule set somewhere that filters against a list of known IP's, or browser signatures, or similar, but the question then seems to be... why, and why specifically that site...?