Today, for the first time, I couldn't use iplayer. As usual, I switched country to UK, cleared browsing data, deleted everything from temp app data file before going there. Was using Firefox. Tried same procedure with Epic browser. Same result. Chatted with Nord support. They wanted screenshots of results from dnsleaktest dot com. Tech said wait while they checked it out. After a little while, chat terminated. Created a ticket via email.
It's called the dark web and unfortunately they went WAYYY past Black Jack and hookers. I think you can go on there and buy a person...that ended up being the FBI the whole time.
@riley0 Your other comment hasn’t federated to my server so I can’t reply directly. Replying here instead.
Tailscale isn’t a VPN in the same way Nord is, where it directs all your traffic through an external server. Rather, it’s a system for creating a “tailnet” of all the machines you install it on. It creates a personal little clique.
For example, if installed on your phone and home PC, they can connect to each other anywhere in the world as if they are on the same network.
In addition, you can designate any machine in your tailnet as an “exit node”, and optionally route all your traffic through it. This way, when out and about on 4G/5G, you can appear to be coming from home.
Now I have machines in two countries. One happens to be the UK. By setting the AppleTV in the UK as my exit node, I look like I’m coming from my home ISP there. It’s resistant to VPN blocking precisely because it isn’t like Nord: it’s literally just my home IP address.
So iPlayer works, Netflix login sharing works, and all that good stuff, because everything looks to be coming from one site.
But that’s MY exit node, uniquely part of MY tailnet. If you don’t have a suitable exit node located, Tailscale won’t help you.
Now Tailscale has just partnered with a traditional VPN provider to give you public exit nodes, Nord-style, but that’s susceptible to the same sort of traffic analysis and blocking that they’re using to target Nord, AIUI.
Nord is still useful for torrenting, but for directly accessing geo restricted services, it seems to be losing the arms race.
BBC could ID a VPN IP address based on usage and concurrent sessions, but honestly most companies that block VPNs just purchase IP address lists from any number of vendors. Pixalate and DoubleVerify are two that I've worked with in the past that both provide that data to clients. They rarely ever block entire IP blocks though, so you might just try reconnecting from a different location/server within the UK until you land on one that works (if any).
It used to be that they didn't throw me out before I got to a program's page. Today, upon login, they redirected me to BBC's main page. Google tells me this: "In addition to the measures listed above, the BBC is also reportedly working on a new anti-VPN measure that uses machine learning to identify and block VPN traffic. This measure is still under development, but it has the potential to be more effective than the BBC's current anti-VPN measures."
I'm pretty sure ML is how Pixalate and DoubleVerify were building their lists, too. The difference is they were footing the bill in terms of resources and time spent to develop a solution. Training ML isn't hard, its just really time consuming.
What VPN type are you using? Wireguard is fastest, so modern VPNs will usually prefer that, but if you're trying to avoid detection from your own network, you could use OpenConnect on port 443 so it looks like normal HTTPS traffic, or OpenVPN + stunnel over port 443