True, that's a good point. Has it been confirmed that they're just blanket-blocking VPN IPs rather than specifically blocking cases of a customer's region shifting/not matching their registration details?
If the VPN node's public IP matches the country in the subscriber's registration details, then it seems pretty unfair that they'd still restrict their account when accessed from that VPN IP. But I suppose from a technical standpoint it's probably far simpler for them to just find VPN IPs/subnets, add them to a database, and restrict content for any account accessed from any of those IPs, regardless of the account, IP, or content regions.
If the VPN node's public IP matches the country in the subscriber's registration details, then it seems pretty unfair that they'd still restrict their account when accessed from that VPN IP. But I suppose from a technical standpoint it's probably far simpler for them to just find VPN IPs/subnets, add them to a database, and restrict content for any account accessed from any of those IPs, regardless of the account, IP, or content regions.