You're sitting at home, on your own wi-fi, and BBC iPlayer tells you it only works in the UK. It's a strange message to get when you haven't gone anywhere. If this is you, the good news is that it's rarely anything serious, and it's almost never actually about where you are. It's about what iPlayer thinks it can see, and those two things aren't always the same.

This guide is for two slightly different situations. The first is people who are genuinely in the UK and getting blocked anyway, which is more common than you'd expect and usually has a simple explanation. The second is people who are actually travelling and want to get back into iPlayer properly, which needs a different approach entirely. We'll cover both, but if you already know you're abroad and just want the fix, our full BBC iPlayer VPN guide walks through every step.

How iPlayer decides where you are

iPlayer doesn't know your actual physical location. No website does. What it sees is your IP address, a string of numbers assigned by whoever provides your internet connection, and it checks that address against databases that map IP ranges to countries and regions. Most of the time this works fine, because the databases are accurate and your connection behaves the way it's expected to.

The trouble starts when something sits between your device and iPlayer that changes what gets checked, or when the database itself has your address filed under the wrong country. Neither of those means you've done anything wrong. It just means the usual assumption, that your IP address reliably tells iPlayer where you are, has broken down somewhere along the way.

The most common cause if you're at home: Private Relay

If you're on an iPhone, iPad, or Mac and you've turned on iCloud Private Relay (part of an iCloud+ subscription), this is very likely your answer. Private Relay routes your Safari browsing through two separate relays so that no single party, not even Apple, can see both who you are and what you're visiting. One side effect is that your traffic can appear to be coming from a different, sometimes nearby, country.

Plenty of UK iPlayer users have been caught out by this without realising Private Relay was even switched on, because it can be enabled by default when you sign up for iCloud+.

The fix is straightforward. Go to Settings on iPhone or iPad, tap your name at the top, then iCloud > Private Relay, and turn it off, either everywhere or just for the network you're currently on. On a Mac, it's under System Settings > your Apple ID > iCloud > Private Relay. Once it's off, reload iPlayer and the error should clear immediately.

A VPN you forgot was running

This sounds obvious written down, but it's one of the most common causes we hear about. A lot of security software, antivirus suites, and even some ad blockers now bundle a VPN feature that can switch itself on automatically, sometimes after an update changes the default settings without asking you.

Check your phone, your laptop, and anything else you're streaming from for a VPN toggle you didn't put there deliberately. Browser extensions are also worth checking specifically, since some privacy or ad-blocking extensions include a proxy feature that behaves the same way. If you find one running and switch it off, iPlayer usually starts working again straight away.

Your router or ISP's IP address is mis-registered

This one is less well known but genuinely common, especially if you're on a smaller internet provider, a newer connection, satellite broadband, or you've recently switched provider. The databases that map IP addresses to countries are maintained by third parties, not by the BBC, and they're not always kept perfectly up to date.

An IP range that's actually UK-based can occasionally be filed under the wrong country, particularly if it's a newly assigned block or one that's changed hands between providers.

There isn't a setting you can flip to fix this one yourself, since it's a problem with an external database rather than your own equipment. Two things are worth trying anyway.

First, restart your router: some providers rotate the IP address assigned to your home on a restart, and a fresh address might already be correctly registered even if your old one wasn't. Second, if the problem persists, use our IP address checker to see exactly what location your connection is showing, then contact your internet provider with that information. They can sometimes get a mis-registered address corrected with the database provider, though it isn't always a quick process.

Your BBC account isn't registered with a UK postcode

Since 2022, watching iPlayer has required a free BBC account, and that account needs a UK postcode attached to it. If yours was set up with a non-UK address, or you're using an old account from before you moved, iPlayer can block you at the account level regardless of what your IP address looks like. This is worth checking even if you're confident your connection is fine, since it's a completely separate check from the location one and easy to overlook.

Sign in at bbc.co.uk/iplayer, check your account details, and update the postcode if it needs it. If the account was set up somewhere else entirely, it's usually quicker to register a fresh one with a valid UK postcode than to try to migrate an existing account.

DNS settings pointing somewhere unexpected

Most people never touch their DNS settings, but if you or someone else on your network has set up a custom DNS provider, usually for ad blocking, family filtering, or general privacy, it's worth double-checking which one. Standard DNS providers like Cloudflare or Google don't change your actual location, since DNS just handles looking up web addresses rather than routing your traffic.

But in a small number of ambiguous cases, iPlayer's detection can use secondary signals, including DNS, when the primary IP check doesn't return a clean answer, and this can occasionally tip the result the wrong way.

If you've set up custom DNS deliberately and iPlayer is misbehaving, try switching back to your router's default DNS temporarily and see whether that clears the error. If it does, you've found your cause, and it's a genuine trade-off between whatever the custom DNS was doing for you and iPlayer access.

Corporate, university, or shared network routing

If you're getting this message on an office, university, or shared building network rather than your own home connection, the network itself might be the issue rather than anything on your device. Some larger networks route all outbound traffic through a central point, sometimes in a different city or even a different country, particularly if the organisation has offices or infrastructure elsewhere.

From iPlayer's point of view, that central routing point is where your traffic appears to come from, not your actual desk. There's usually not much you can do about this yourself beyond asking whoever manages the network, though switching to mobile data as a quick test will confirm whether the network is really the cause.

If you're actually abroad

If none of the above applies and you know you're travelling outside the UK, this message is doing exactly what it's designed to do. iPlayer is a UK-only service, and a VPN connected to a UK server is the standard way to access it from elsewhere.

Our full guide to fixing BBC iPlayer with a VPN covers every fix in order, including why a VPN alone sometimes isn't enough, since iPlayer also checks your DNS requests and can pick up on leftover browser cookies from a previous UK session. If you don't already have a VPN, our tested recommendations covers the ones that hold up best against iPlayer's detection.