Unlock Support Overview
The table below lists support status and recommended routes for popular platform-region combinations. Status is based on the location and type of each route's exit IP; streaming platforms adjust their risk controls and regional licensing at any time, so actual playback depends on what happens when you connect.
| Platform | Region | Status | Recommended Route | Notes |
|---|---|---|---|---|
| Netflix | United States | Supported | US · Direct | Largest content library; native IP routes recommended |
| Netflix | Japan | Supported | Japan · Relay | Exclusive anime and J-drama library |
| Netflix | Italy | Test First | Italy · Direct | Smaller library; sensitive to IP quality |
| Disney+ | United States | Supported | US · Direct | The most complete content library |
| Disney+ | Hong Kong | Supported | Hong Kong · IEPL | Includes localized dubs and some exclusive titles |
| HBO Max | United States | Supported | US · Direct | The platform primarily serves the US region |
| Hulu | United States | Supported | US · Direct | US only; sensitive to IP type |
| YouTube Premium | United States | Supported | US · Direct | Benefits are tied to your account's home region |
| Prime Video | United States | Supported | US · Direct | Some titles are licensed per region |
| Prime Video | Singapore | Test First | Singapore · Direct | Licensed content differs notably from the US library |
| BBC iPlayer | United Kingdom | Supported | UK · Relay | Requires a UK IP; residential-type routes recommended |
For the full route list, route types and covered cities in each region, see the route list page.
What "Unlocking" Actually Unlocks
Before every playback session, a streaming platform answers one question: which region is this viewer in? The verdict is based mainly on the geographic location of the exit IP, plus secondary signals like the account's registration country, interface language and system time zone. Once decided, the platform shows the matching regional library and determines what can be played.
"Unlocking" simply means making the platform see an available exit IP in the target region during that check, so you land in the matching library — it doesn't alter the platform itself and has nothing to do with cracking copyrighted content. In essence, it's about being recognized as a regular viewer from the target region. In practice, three factors usually decide the outcome:
- IP location: the exit IP must be registered in the target region — the most basic requirement. If it isn't, the library switches to another region or you get a region-restriction message outright.
- IP quality: even within the same region, an IP's "background" determines how it's treated. Datacenter ranges are easily flagged as proxy traffic, while native and residential types look much more like ordinary home viewers.
- Environment consistency: when your DNS exit, system time zone, browser language and IP location contradict each other, some platforms flag the connection as proxy traffic. Using your client's global mode usually resolves DNS inconsistencies at the same time.
Native IP vs. Broadcast IP vs. Residential IP
A "native IP" is registered in the same region as its datacenter; a "broadcast IP" (also called non-native) is registered somewhere other than where it's actually used; a "residential IP" is registered to a home broadband subscriber. The three carry different levels of trust in streaming platforms' risk-control systems:
| IP Type | Definition | Streaming Performance |
|---|---|---|
| Native IP | Registered in the same region as the datacenter | Recognized as a normal local visitor by major platforms — ideal for strict services like Netflix and HBO Max |
| Broadcast IP | Registered in a different region from where it's used | Some platforms flag it as proxy traffic, with higher error rates — fine for casual browsing and other lenient use cases |
| Residential IP | Registered to a home broadband subscriber | Closest to a real viewer profile — especially effective for strict platforms like BBC iPlayer |
You can check each route's IP type by region on the route list page. For platforms strict about IP location, try routes labeled native or residential first. Sensitivity to IP type also varies between regions of the same platform — for combinations marked "test first," switch routes before drawing conclusions.
4K and Dolby Vision: Real-World Bandwidth Needs
These are the officially recommended bandwidth figures from Netflix and other major platforms — the minimum downstream bandwidth needed for stable playback at each quality tier:
Bandwidth gets you in the door, but stability is what decides the viewing experience. Packet loss and jitter on cross-border links make platforms drop quality tiers or buffer repeatedly — even with plenty of spare bandwidth. During evening peak hours, prefer relay and IEPL routes; for bandwidth-heavy, latency-tolerant binge-watching, direct routes are usually enough.
Data usage scales with quality and viewing time. Monthly plans come in 60GB / 250GB / 500GB tiers, with data resetting on your billing day each month. If your viewing schedule is irregular, data packs are an alternative — usable until exhausted and never expiring. See the plans page for pricing.
Common Error Codes and How to Fix Them
Most playback errors come down to two causes: the platform's risk control flagged your current exit IP, or the route quality fluctuated. Here are the most common errors and the order to tackle them:
The platform's risk control flagged your exit IP. Fix: switch to another route in the same region in your client; clear your browser cookies; retry in another browser or an incognito window.
Usually caused by packet loss on the route. Fix: switch to a relay or IEPL route; avoid evening peak hours; also check that your local network is working normally.
The IP location doesn't match the selected region. Fix: make sure the route region matches your account's region; for location-strict titles, prefer native IP routes.
Hulu serves the US region only. Fix: choose a US direct route; clear your browser's location permission and reload the page.
This platform is very sensitive to IP type. Fix: choose a UK residential or native route; clear cookies and retry, and make sure your browser's location permission is off.
First, confirm your client is connected; then verify your exit IP location with our IP check page; next, switch to another route in the same region; finally, clear browser cookies or use an incognito window. Most errors can be traced at step two.