The Address Your Phone Never Gave Them
You're on holiday. You tap something you watch every week at home, and a grey screen appears with a message about content not being available in your region. The service has no idea where you physically are. It made a guess, and the guess was good enough to block you.
That's the whole trick. Geo-blocking isn't surveillance. It's inference, built from a single piece of information you hand over automatically every time you connect to anything online, cross-referenced against a commercial database that's been accumulating for decades. No GPS required. No passport scan. Just your IP address and a very large spreadsheet.
The Postcode Your Internet Connection Carries
Every device connecting to the internet gets an IP address assigned by whoever provides that connection: your home broadband supplier, a hotel's Wi-Fi, a mobile network. That address isn't random. Internet Service Providers receive blocks of IP addresses from regional registries, and those registries keep records of which blocks went to which company in which country.
Commercial services like MaxMind and IP2Location then aggregate those registry records, cross-reference them with user reports, Wi-Fi positioning data, and latency measurements, and sell the result as a lookup database. A streaming platform pays for API access. Your IP hits their server, the API returns "Netherlands, Amsterdam, ISP: KPN," and the Dutch content library loads. The whole handshake takes milliseconds.
Accuracy varies. Country-level guesses are right roughly 95 to 99 percent of the time. City-level drops to somewhere around 50 to 80 percent depending on the region, and a rural IP belonging to a regional ISP headquartered three counties away might consistently place you in the wrong city. The platform doesn't care about the city. It cares about the country, because that's where the licensing contracts draw the line.
Why the Contracts Exist at All
This part most explainers skip, so here it is. Geo-blocking isn't platforms being awkward. It's the direct result of how content rights are sold, and the distinction actually matters.
A studio makes a film. It licenses broadcast rights territory by territory, sometimes to different buyers. One streaming service might have bought UK rights. A rival service, or a local broadcaster, might have bought French rights. The studio sold each deal separately, probably at different prices, probably with different exclusivity windows. The platform that bought UK rights is contractually obligated to prevent French users from watching it, because a French company paid separately for that privilege.
So the platform enforces a border it didn't invent. Its tool is the IP lookup. Blunt, imperfect, and everyone in the industry knows it. But it's cheap and it's defensible: if a rights holder audits them, they can point to the system and say they made a reasonable technical effort.
What a VPN Actually Does to This System
A VPN routes your traffic through a server somewhere else before it reaches the streaming platform. The platform sees the IP address of that server, not yours. If the server sits in a US data centre, the lookup returns "United States" and the US content library loads.
Simple in theory. In practice, streaming services have spent years building secondary blocklists targeting known VPN and data-centre IP ranges, and this is where the whole thing starts to resemble an arms race between stubborn parties who will never actually stop.
When you connect through a consumer VPN, you're often sharing that exit IP with thousands of other users. That concentration is a flag. A residential IP in Ohio doesn't generate ten thousand simultaneous Netflix sessions. A data-centre IP in Virginia might. Services like Netflix maintain their own lists of data-centre IP ranges and cross-reference them against session data. If an IP looks like a data centre and isn't registered to a known ISP serving residential customers, it gets flagged. Some platforms block it outright. Others let it through but serve a reduced library, a kind of silent downgrade.
VPN providers cycle through new IP addresses. Platforms update their blocklists. Some VPN services now route traffic through residential IPs, which are much harder to distinguish from genuine users. That raises its own ethical questions about whose connection you're borrowing, but it explains why some VPNs work better than others for streaming specifically.
Where the System Gets It Genuinely Wrong
Here's the wrinkle that should bother you even if you never touch a VPN.
Consider two people: Marta, who lives in Berlin and connects via her home broadband, and James, who also lives in Berlin but works for a company whose corporate network routes all traffic through a London proxy. Marta gets the German library. James gets the UK library. Neither of them chose this. James might not even know it's happening.
Or consider mobile. When you switch from home Wi-Fi to your mobile data, your IP changes. Your carrier might assign you an IP that resolves to a city you've never visited, because that IP block belongs to a regional hub. One user was consistently placed in Lyon by a major streaming service despite living in Paris, because her mobile carrier's Paris traffic exits through a Lyon gateway. She couldn't watch a French-exclusive live broadcast on her phone. No error message explained why. The grey screen just appeared.
The system works well enough at scale. It fails at the edges in ways that feel arbitrary and confusing to the person caught in them, and there's no appeals process.
The One Thing You Can Actually Check
If you want to see what location streaming services think you're coming from, search for "what is my IP" and paste that address into a free lookup tool like MaxMind's demo page. It'll show you the country, region, and city the database associates with your connection.
Is the location obviously wrong? That explains any geo-blocking quirks you've hit. On mobile and placed somewhere strange? Switching to home Wi-Fi often fixes it, because home broadband IP blocks tend to be more precisely mapped than mobile carrier blocks.
The broader point is this. Platforms aren't tracking your movements. They're making a probabilistic guess from a single data point, enforcing a contract that predates streaming entirely, and hoping the guess holds. Most of the time it does. When it doesn't, the system has no graceful way to explain itself, because explaining the mechanics would also explain exactly how to route around them.
The grey screen doesn't know where you are. It knows where your internet connection probably is. That's a smaller thing than it looks, and a considerably more fragile one than the platforms would ever want you to notice.