The Complete Streaming Handbook

How platforms work out your region

Regional restrictions on every streaming platform really come down to the same question: where is this request coming from, and where does this account belong? Only once both are answered does a platform decide which library to show you and whether to allow playback. Here is how the signals it uses break down.

Signal 1: Where the exit address is registered

Every request carries a source address. The platform looks that address up in ownership databases to find where it is registered — country, city, carrier, autonomous system type. This is the most basic layer, and also the one most prone to mismatch: the same block may be registered in Singapore while its traffic actually exits in the US, and different databases may label the same block differently.

Major platforms rarely rely on a single database; they layer their own historical behaviour records on top — has this block been shared by a large number of accounts, has it been flagged as a proxy source. That is why the same exit can be treated as a datacenter block by Netflix yet play fine on Disney+. It is not that one is more lenient; the two use different data sources and different weighting.

Signal 2: Where DNS resolution happens

The second signal is where DNS lookups originate. If the exit shows Singapore but resolution goes through a local recursive resolver, the two region labels no longer match. This kind of cross-check is more common in a browser than in a standalone client — browsers follow the system's DNS configuration, while standalone clients usually bring their own resolution logic, so the path stays consistent.

That also explains why the same account on the same route errors out in a browser but works in the app. If you suspect DNS, point your system resolver at an address in the same region as your exit, then reload the page.

Signal 3: Account region and subscription status

The exit decides where you appear to be; the account region decides which region your account belongs to. These are two independent variables, and platforms lean on them to different degrees.

Netflix's library follows your viewing region, while the account region mainly affects billing and some content. Disney+'s library is tied to the account region — change the exit but not the account region and you still see your original library. YouTube Premium benefits and pricing follow the account region. Prime Video follows the Amazon storefront your account belongs to. How to change an account region and what limits apply is covered in chapter 7 of this page.

How the seven platforms differ

When the checks happen

A region check is not a one-off at page load. A typical flow has three checkpoints: a basic region check when the home page loads, a playback licence check when you press play, and periodic re-checks while the stream runs.

The third checkpoint is the one people overlook. If a stream suddenly errors out halfway through, it is usually a mid-playback re-check catching a changed exit — the route reconnected in the background, or the client picked a different landing node. That is also why switching routes manually while watching is a bad idea: the switch itself may not break anything immediately, but it will fail the next re-check. For ways to confirm your exit really is where you think it is, see the checks in Exit and DNS verification.

What unlocking actually gets you

The word "unlocking" sounds like a single flip of a switch, but it actually has three levels, each with its own bar and its own troubleshooting path. Telling them apart is the first step in fixing anything.

Level 1: You can connect

DNS resolves, the page loads, sign-in goes through. This level only needs an exit address the platform has not outright blocked — the lowest bar of the three. Plenty of people treat "the home page opens" as success when they have not even finished level one.

Level 2: It actually plays

You press play and video really appears, instead of a spinner followed by an error code. This level requires an exit address that is not on the platform's proxy list and a playback licence API that answers normally. The home page is static content; it is the playback API that runs the full region and source checks — which explains a very common pattern: the site opens fine, then errors the moment you press play.

Level 3: The picture quality is right

You get the highest quality that account, device and connection can support, rather than being quietly dropped to SD. This level is a completely different problem from the first two: it depends on sustained bandwidth stability, the device's content protection level and how much the route jitters — not much to do with whether you were flagged as a proxy source.

Only when all three pass is it genuinely watchable. When troubleshooting, first work out which level you are stuck at, then decide which variable to change: level one means DNS, level two means the exit, level three means the route or the device.

Three common false positives

• The home page loads, playback errors. The exit sits in a datacenter block the platform has already flagged. Static pages are not checked, the playback API is — so it looks like "the site opens but nothing plays". The fix is a different route or a different exit region, not reinstalling the app.
• It plays, but only in SD. The route has enough peak speed, but jitter and packet loss are high, so the platform's adaptive bitrate algorithm drops quality to keep the stream smooth. A speed test may show tens of Mbps while the picture stays blurry. The fix is a route with a steadier path.
• It plays, but the library is wrong. The exit landed somewhere that is neither your target region nor your home region, so the platform serves that region's catalogue. It shows up as "it works, but the show I want is not there". The fix is to pin the exit to the target region, then check whether the account region also needs changing.

Unlocking is not the same as changing your account region

This is the most commonly confused point. The exit decides where you are watching from; the account region decides which region your account belongs to. Changing the exit does not change the account region, and changing the account region does not change the exit.

For most platforms, pointing the exit at your target region is enough to see that region's library. But on account-region-driven platforms such as Disney+ and YouTube Premium, a correct exit with the wrong account region still shows your original library. Conversely, a correct account region with the exit somewhere else can still fail the region check and block playback.

So before troubleshooting, ask yourself one question: am I adjusting the exit, or the account region? Get the direction wrong and nothing you try will work.

Why unlocking is a continuous state

Platforms keep re-checking during playback, so a mid-stream reconnect or a switch to a different landing node can fail the check. A genuinely stable viewing experience does not come from one successful check; it comes from the route holding the same exit and the same path for the whole session. That is why this page gives route stability its own chapter — it is a different question from whether you can pass the checks, and it needs to be judged separately.

Native IPs, broadcast IPs and residential IPs

When judging an exit address, platforms look beyond the country it is registered in — they also ask whether it looks like a real user's address. Two Japan exits, one a residential broadband block and one a datacenter block, face very different levels of scrutiny. Here are the common ownership types.

Four types of address ownership

How platforms classify an address

Three sources are combined: autonomous system type databases show what kind of operator the block belongs to; reverse DNS records often reveal whether it is a datacenter or a user broadband line; and historical behaviour records show whether the block has been shared by a large number of accounts. Together they produce a judgement of how much it looks like a real user.

Worth noting: there is no public standard for this judgement, and platforms weight the signals differently. The same block may pass on one platform and be blocked on another. That is normal — it does not mean one platform is stricter, and it does not mean the address itself is faulty.

What it means in practice

Residential addresses are the least likely to be blocked, because they blend in with a large pool of real household users. The trade-off is scarcity, and stability depends on the quality of that particular broadband line.

Native datacenter addresses are what most subscription services actually use; whether they work depends on how the platform has flagged that block in the past.

Broadcast addresses cause the most trouble: when registration and actual routing disagree, you get the wrong library, a rejected playback licence, or a home page that will not load at all.

Address type is not the only variable, though. A stable dedicated route with a native address usually delivers a better viewing experience than a jittery residential address — platforms block flagged blocks, while viewing quality depends on how steady the bandwidth is. Two separate things, judged separately.

How to tell which type you are on

The most direct way is to look up the ownership details of your exit address. If the carrier name is a datacenter operator, it is almost certainly a datacenter address; if it is a local broadband carrier, it may be residential or a native residential block. Then check whether the registered location matches the actual exit location: matching means native, mismatched means broadcast.

The route list on this site labels each route by type (IEPL dedicated / relay / direct), but address ownership shifts as providers adjust their blocks, so when a specific platform errors out, go by what you actually measure.

What 4K and Dolby Vision really need in bandwidth

"Is my bandwidth enough?" is the question people ask most about 4K, but the answer is not a single number in Mbps. Three things decide picture quality: bitrate, peak headroom and device certification.

Typical bitrates by quality tier

Streaming quality is not decided by resolution alone; bitrate is what actually drives bandwidth. The industry's usual recommendations are roughly: around 3 Mbps for SD, around 5 Mbps for HD, around 15 Mbps for 4K. Formats with dynamic metadata such as Dolby Vision peak higher, because they carry frame-by-frame brightness mapping information on top.

These are the recommended figures from platform help pages, not measurements taken here. Real usage moves with scene complexity: a static dialogue scene may sit at a few Mbps, while an action sequence can spike several times higher.

Peak vs average: why a fast speed test still stutters

A speed test measures peak throughput over a short burst; streaming needs sustained, steady throughput. They are not the same thing.

When you open a 4K title, the player first fills its buffer at a higher bitrate, and that burst can be more than twice the average. If your route's capacity sits right on the threshold, you get the classic pattern: sharp for the first few seconds, then down to 1080p or worse.

The other overlooked variable is jitter. When the average is fine but the speed swings widely second to second, the player's adaptive algorithm tends to drop quality conservatively. So judging whether a route suits 4K is not just about a speed test result — it is also about whether it holds up during peak evening hours, when international capacity is tightest and the differences really show.

Devices and quality certification

Bandwidth is only one of three tickets; the other two are the content protection level and the link protection protocol.

On content protection, the tiers commonly used on mobile only allow high-resolution output at the higher levels; fall short and the picture is capped at SD or HD no matter how much bandwidth you have. Desktop browsers are another common bottleneck — most cap out at 1080p because of how content protection is implemented, so 4K needs the platform's own app or a system-level player.

On link protection, the whole chain — from the playback device to the display, including the cables and any splitters in between — has to support a high version of High-bandwidth Digital Content Protection (HDCP). If any link falls short, 4K drops to 1080p or you get a black screen with audio.

Working out simultaneous streams

This service's subscriptions do not limit the number of devices, but bandwidth is shared. Two devices each streaming 4K roughly doubles the usage of a single stream; with three devices, one on 4K and two on HD, the total is the sum of each stream's bitrate.

As a rule of thumb, budget around 15 Mbps per 4K stream and around 5 Mbps per HD stream, then leave about 30% headroom for peaks. Knowing how many streams will run at once before you start is far more useful than complaining about buffering afterwards. Monthly plans come in three tiers — ¥9.9 with 60GB, ¥18 with 250GB and ¥28 with 500GB — with data resetting each month on the activation date; if you only watch occasionally, a ¥158 data pack with 300GB that never expires is another option. For a side-by-side comparison, see the pricing page.

How to check your actual bitrate

Netflix shows an info overlay via a keyboard shortcut during playback, listing the current resolution and live bitrate. On platforms without that, fall back to your system's live network usage: while playing 4K, sustained usage should sit clearly above HD levels; if it hovers around one or two Mbps, you are actually getting a low quality stream, and the cause is more likely the route or device certification than "not enough bandwidth".

Common error codes, explained and fixed

Error codes look like a jumble, but they fall into five categories by cause. Working out which category you are in before you start fixing is far faster than trying things one by one.

Category 1: Source detection

The classic example is Netflix's M7111-5059. The meaning is blunt: the platform considers your exit part of a blocked proxy or datacenter block. The order of operations is to switch exit region, or switch to another route within the same region — platforms usually block specific address blocks, not an entire region.

Disney+ does not always give a code for the same problem; it may just say the content is not available in your region. Hulu and BBC iPlayer are blunter still: a region mismatch blocks the whole page, and you do not even get the catalogue.

Category 2: Region mismatch

Disney+'s Error Code 73 and Prime Video's 5505 belong here: the exit region and the account region disagree, or the account has no playback licence in that region. The fix is not a different route but checking the account region — ten different routes will change nothing.

Category 3: Network-layer interruptions

Netflix's NSES-500 and the browser's ERR_NETWORK_CHANGED are network-layer: the connection was interrupted or rebuilt mid-playback. Typical triggers are a route reconnect caused by jitter, switching between Wi-Fi and cellular, or the client re-selecting an exit node in the background. The fix is to retry on the same route and make sure you do not change networks while watching.

Category 4: Devices and content protection

It shows up as audio with a black picture, subtitles rendering over a blank screen, or a message that the device is unsupported. These have nothing to do with the exit address and a different route will not fix them. What to check: whether the playback device's content protection level meets the requirement, whether the display chain supports the required version of HDCP, and whether you are trying to watch 4K in a desktop browser.

Category 5: Account and payment

You get a rejected payment method or a message that the account is not available in that region. This usually comes from a billing region that does not match the account region. The fix is to check the payment method on the account, not to adjust the route.

A five-step troubleshooting order

1. Categorise first. Decide which of the categories above the error belongs to — region, network, device or account. Get that wrong and everything after it is wasted.
2. Change the exit region. Try another route within the same region first, to avoid a flagged address block. Changing region is a last resort, not the first choice.
3. Quit the app completely. Not just closing the tab — end the process and reopen, so the DNS cache and connection state reset together.
4. Test on another device. Try once on a different device and a different network; that quickly separates an account problem from a local one.
5. Check the account region and payment method. If the first four steps are clean and it still errors, the problem is almost certainly on the account side, not the route.

Choosing a route for how you watch

Both count as "working", but live events and series box sets ask completely different things of a route. This chapter maps route types to viewing scenarios and gives you a choice you can follow directly.

The three route types compared

Matching routes to scenarios

Why peak hours stutter

International capacity is tightest between 8 and 11 p.m., a reality every cross-border route faces. In that window, direct routes over the public internet feel congestion first, showing up as falling speeds and rising jitter; dedicated lines and optimised relays are affected less, because their paths do not compete with ordinary traffic for the same exit.

To tell a route problem from a platform problem, run a simple comparison: same time, same device, try an unrelated cross-border site. If only streaming stutters and other sites are fine, the problem is more likely on the platform or account side; if everything cross-border has slowed down, it is the route or the exit.

When to change route, when to change region

When the error points at a region, change region; when it plays but looks soft, stutters or drops, change route. The two actions solve different problems, and mixing them only muddles the diagnosis. If nothing changes after the swap, you picked the wrong variable — go back to the categories in the previous chapter.

Routes and nodes

A region usually maps to several routes, and the node's city, the route type and the node's current load all affect real-world performance. Choose in this order: pick the region, then the route type within it, and if the experience is still poor, switch to another node in the same region — do not start by jumping between regions, or you will not even be able to tell whether the region was the problem.

This site currently covers 120+ countries and 180+ routes, supports Windows / macOS / iOS / Android / Linux, and a single subscription allows unlimited simultaneous devices. To browse the route list region by region, see the route list.

Account region, payment region and viewing region

These three "regions" are often treated as one thing, when they are really three independent variables. Knowing which variable maps to which problem saves a lot of pointless attempts.

What each variable means

Account region: chosen at sign-up. Most platforms limit how often it can be changed, and some require you to use the account in the original region for a period first.

Payment region: the country that issued the payment method, or the region of the billing address.

Viewing region: where your current exit address is registered — the variable the earlier chapters have been discussing throughout.

When all three agree, life is easy. When they do not, you get a variety of baffling errors, and the message usually just says the content is unavailable in your region without telling you which region is the mismatch.

How each platform ties them together

• Netflix: the account region affects billing and some content, while the library mainly follows the viewing region. For Netflix, the exit address is the variable that matters most.
• Disney+: the library mainly follows the account region. Change the exit but not the account region and you still see your original library.
• HBO Max: driven mainly by the exit address, with the account region mattering less.
• Hulu: requires a US exit and also has regional requirements for the payment method — both conditions have to be met.
• YouTube Premium: benefits and pricing follow the account region, while the exit affects the availability of some content.
• Prime Video: follows the Amazon storefront your account belongs to — wherever the account sits, the catalogue follows.
• BBC iPlayer: requires a UK exit, plus a declaration that you are in the UK and a valid TV licence.

The limits of cross-region viewing

A few things need to be spelled out.

First, this service provides cross-border routes only. It does not supply accounts for any platform, and does not register or pay on your behalf. The account and subscription relationship is something you establish with the platform yourself.

Second, switching account regions frequently can trigger a platform's risk controls. Most platforms limit how often, or how soon, an account region can be changed — read their documentation before you do it.

Third, a payment method that does not match the account region can fail on renewal. Paying for an account in one region with a payment method from another is commonly rejected, and it often only surfaces at renewal time, which can interrupt the subscription.

Fourth, each platform writes its own terms of service. Whether cross-region viewing is permitted, and under what conditions, is governed by those terms. This page covers the technical detection mechanisms and troubleshooting methods; it is not an interpretation of any platform's terms.

A practical approach

If you mostly watch one region of one platform, pin your exit to that region and keep the account region aligned with your payment method, without changing either often. That gives you the fewest problems and the simplest troubleshooting — fewer variables means faster diagnosis.

Conversely, if you switch between several regions regularly, give each viewing need its own fixed exit instead of re-testing every time. Once that becomes a habit, "it worked last time and not now" problems drop sharply.

Full self-check flow and common questions

The earlier chapters condensed into a sequence you can follow. Work through it in order and do not skip steps — the time you save skipping usually comes back doubled later.

The five-step self-check

1. Confirm the exit. Look up where your current exit address is registered and check it is in the region you want. If the exit is wrong, the later steps are pointless.
2. Confirm DNS. Check that resolution follows the same region as your exit. When the exit is overseas but resolution still goes through a local recursive resolver, platforms with strict region checks will refuse to play.
3. Confirm the account. Compare the account region, the payment method and the current viewing region, and see which one does not match.
4. Confirm the device. Try once on another device and another network to separate a local problem from an account problem.
5. Confirm route stability. Watch for reconnects during playback. If the route switches landing nodes mid-stream, the re-check fails.

When to contact support

Account and payment issues have to go to the platform's own support — a route provider cannot fix them. For routes that will not connect, reconnect constantly or show persistently abnormal speeds, open a ticket with the error code, the time it happened, the exit region and your device details; that makes diagnosis much faster.

A ticket that just says "it does not work" takes three or four rounds of back-and-forth before troubleshooting can even start. Give all three pieces of information at once and one round is usually enough to point at the cause.

Write down what you find

Each time something goes wrong, note three things: the error code or the exact message, the time it happened, and the exit region at that moment. With all three, whether you are reviewing it yourself or filing a ticket, you skip a lot of back-and-forth. Many people only remember "it did not work", with no time or region, so the problem cannot be reproduced — and cannot be diagnosed.

If the same symptom keeps coming back over a period, put the records side by side and a pattern usually appears — always at peak hours, always on one route, or always in one region of one platform.

FAQ