Routes in major cities are listed by region, each labelled with its route type and the streaming services it suits. IEPL dedicated, relay and direct routes are explained below, with the use cases each one fits.
Regions are grouped by the geographic location of each exit. The table below shows a sample of routes; the full list is the one in the client.
Asia Pacific routes
Exits cluster in Tokyo, Osaka, Seoul, Singapore and Hong Kong — the most-used group for international sites and Asian streaming.
Country / Region
City
Route type
Streaming support
Japan
Tokyo
IEPL Dedicated
Netflix / YouTube / Disney+
Japan
Osaka
Relay
YouTube / Abema
South Korea
Seoul
Relay
Netflix / YouTube
Singapore
Singapore
Direct
Netflix / Disney+ / YouTube
Hong Kong
Hong Kong
IEPL Dedicated
Netflix / YouTube / HBO
Thailand
Bangkok
Direct
YouTube / Netflix
Malaysia
Kuala Lumpur
Relay
Netflix / YouTube
Vietnam
Ho Chi Minh City
Direct
YouTube
India
Mumbai
Relay
Netflix / YouTube
Indonesia
Jakarta
Direct
Netflix / YouTube
Philippines
Manila
Direct
Netflix / YouTube
North America routes
Los Angeles and San Jose carry most trans-Pacific traffic; Toronto and Vancouver suit Canadian content.
Country / Region
City
Route type
Streaming support
United States
Los Angeles
IEPL Dedicated
Netflix / Disney+ / HBO / Hulu
United States
San Jose
Relay
Netflix / YouTube
United States
Seattle
Direct
Netflix / YouTube
Canada
Toronto
Relay
Netflix / Disney+
Canada
Vancouver
Direct
Netflix / YouTube
Mexico
Mexico City
Direct
Netflix
Europe routes
London and Frankfurt are the main entry points into Europe; Amsterdam and Zurich suit tasks that need a European exit.
Country / Region
City
Route type
Streaming support
United Kingdom
London
IEPL Dedicated
Netflix / BBC iPlayer
Germany
Frankfurt
Relay
Netflix / YouTube
France
Paris
Relay
Netflix / Disney+
Netherlands
Amsterdam
Direct
Netflix / YouTube
Switzerland
Zurich
Relay
Netflix
Sweden
Stockholm
Direct
Netflix / YouTube
Spain
Madrid
Direct
Netflix / Disney+
Italy
Milan
Direct
Netflix
Poland
Warsaw
Direct
Netflix / YouTube
Turkey
Istanbul
Direct
Netflix / YouTube
Other regions
Exits in Oceania, South America, the Middle East and Africa are mostly direct and relay combinations, suited to local sites and region-specific content.
Country / Region
City
Route type
Streaming support
Australia
Sydney
Relay
Netflix / Stan / YouTube
Australia
Melbourne
Direct
Netflix / YouTube
New Zealand
Auckland
Direct
Netflix
Brazil
São Paulo
Direct
Netflix / YouTube
United Arab Emirates
Dubai
Relay
Netflix / YouTube
Argentina
Buenos Aires
Direct
Netflix
Chile
Santiago
Direct
Netflix
Egypt
Cairo
Direct
Netflix
Route types explained
Every route looks the same in the app, but the underlying structure differs a lot. Understand the three types first, then decide which one to keep as your default.
Dedicated
IEPL Dedicated
End-to-end dedicated channel, routed over the backbone
A dedicated line provides an exclusive channel between two data centres. Traffic never crosses the public internet's international gateways, the path is fixed and bandwidth is not shared with other users. These routes usually terminate in core facilities such as Tokyo, Hong Kong and Los Angeles, and are limited in number.
Best for 4K streaming, cross-border video calls and any task that needs to keep the same exit for hours. Set a dedicated node as your default route to avoid switching mid-session.
Most stable at peak hours
Fixed path, good for long-lived connections
Highest cost per unit of bandwidth
Cost: High
Relay
Relay routes
Two legs optimised separately, widest coverage
A relay splits one long path into two: the client connects to an entry node (often in Hong Kong or Singapore), which forwards traffic to the target exit. Each leg can be optimised on its own, so relays reach regions where no dedicated line exists.
Relay routes are the most numerous and suit less common regions or tasks that switch between several locations. Peak-hour performance depends on how busy the entry node is at the time; if it feels congested, switch to another entry.
Widest regional coverage
Entry and exit can be combined freely
Mid-range cost, most routes
Cost: Medium
Direct
Direct routes
Simplest structure, shortest path
Direct is the simplest setup: the client connects straight to the exit node with no extra hops, so the path is short and overhead is low. These routes are the most numerous and cover the most regions — ideal for everyday browsing, 1080p streaming and downloads.
For cross-continent traffic, direct routes are less stable than dedicated lines. If your target is on another continent, or you need a connection that stays up for hours, prefer a dedicated or relay route.
Most nodes available
Good for everyday browsing and downloads
Lowest cost
Cost: Low
Choosing a route by use case
Start with what you're doing, then with where the content lives — two steps narrow the list to two or three routes.
Everyday browsing: direct first, exit close by
Looking things up, reading news and checking email don't need much peak bandwidth, but they do need pages to open instantly. Pick an Asian exit that is physically close: the first packet comes back faster, and switching tabs or refreshing rarely stalls. Direct routes have the simplest structure and the fewest hops, so they're the default here.
If a site feels slow one day, don't rush to change plans — try another route in the same region from the client first. Cities usually have several exits, and switching to one of them gets around temporary congestion.
DirectSingapore / Bangkok / Kuala Lumpur — nearby exits you can leave running
RelaySeoul / Mumbai — closer to the source when visiting local sites
Streaming: start with a dedicated line, pick the exit by content region
4K playback is a steady bandwidth drain — a two-hour film never pauses, and a mid-stream slowdown is the worst outcome. Use an IEPL dedicated line here: the channel is exclusive and the path fixed, so evening peak traffic is unlikely to crowd it out. Match the exit to the content: Los Angeles for US libraries, Tokyo for Japan, London for the UK.
Connect the route before the player starts buffering, then open the page. Switching mid-stream forces the player to renegotiate and can drop the quality a notch. If you really must switch, pause playback first.
IEPL DedicatedTokyo / Hong Kong / Los Angeles / London — first choice for long viewing sessions
RelayFrankfurt / Paris / Sydney — covers European and Oceanian content
AI tools: keep long connections steady, don't switch routes often
Chat-based AI tools hold a single session open for a long time, and one drop means starting over. What matters here is connection continuity and first-packet speed, not peak bandwidth. Set one dedicated route as your default, put the exit in Tokyo or Los Angeles, and turn on auto-reconnect in the client.
If the page loads but the chat keeps spinning, check whether the route switched mid-session. Quitting the client and reconnecting to rebuild the session usually works better than refreshing the page over and over.
IEPL DedicatedTokyo / Los Angeles — first choice for long sessions
RelayFrankfurt / Amsterdam — European exits for AI tools
Gaming: stay in-region, fewer hops is better
Online games are the most sensitive to jitter, so the rule is the opposite of streaming: don't cross continents, don't take the long way round. Choose an exit in the same region as the game server so data takes the shortest path. For Asian servers, prefer Japan, South Korea and Singapore; for European servers, Frankfurt and Amsterdam.
Don't switch routes mid-game, and don't run large downloads at the same time. If you get intermittent lag, check whether something else is using your local connection before trying another route in the same region.
DirectTokyo / Seoul / Singapore — in-region and close by
RelayFrankfurt / Amsterdam — European exits for gaming
Work & meetings: stability first, keep one route
Video calls, file sync and remote desktop all suffer most from a mid-task drop. Pick one dedicated route and stay with it instead of changing exits daily. The client allows unlimited simultaneous devices, so your laptop and phone can share the same route and you switch less.
Connecting ten minutes before a meeting and running a quick connectivity check is far calmer than fixing a problem mid-call. If corporate network access is involved, check your organisation's network usage policy first.
IEPL DedicatedHong Kong / Tokyo / Los Angeles — first choice for meetings and sync
RelayLondon / Sydney — exits for cross-time-zone collaboration
Coverage and route maintenance
VPNBu currently offers 100+ countries / 240+ routes. Country and region counts are based on the geographic location of each exit; route counts are based on independently selectable exit entries, so a single country or region may have several routes with different types and purposes.
The table above lists individual routes, not the full set. The complete list lives in the client, grouped by region and updated automatically with your subscription — new routes need no extra purchase, and closing and reopening the client refreshes the list. If a route is temporarily missing from the client, the carrier is usually adjusting the facility; it normally comes back on its own.
How to read the streaming support column
The streaming column notes the services commonly available in that route's region. Providers change their availability and regional policies without notice, so the column is a guide for choosing a route, not a long-term promise. If a service won't open, try another route in the same region before switching regions.
Do routes change?
Yes. International routes are provided by carriers, and facilities, bandwidth and routing are adjusted from time to time — which is why the route list needs ongoing maintenance. VPNBu checks route availability weekly, removes entries that have been unavailable for a long period and adds new ones; a route may also be upgraded from direct to dedicated, or the other way round.
Route availability depends on carriers and your local network. This page describes route structure and purpose and makes no promise of specific speeds or latency figures. You can use it free before buying to see how your usual routes perform on your own connection.
Three steps to picking a route
Start with the use case
Long sessions such as streaming, meetings and gaming call for a dedicated line; everyday browsing and downloads are fine on direct. The use case sets the minimum route type.
Then the region
Match the exit region to where the content lives: Los Angeles for US libraries, Tokyo for Japan, London or Frankfurt for European sites.
Finally, compare routes in the same region
A single region often has several routes — try them in turn and set the smoothest one as your default. The client allows unlimited simultaneous devices, so your phone and computer can each keep one.