//Route overview · 2026

Global route and node distribution

VPNQF covers 90+ countries and 220+ routes. This page lists sample routes across four regions — Asia Pacific, North America, Europe and the rest — explains how IEPL dedicated, relay and direct lines differ, and suggests which to pick for five common uses: everyday browsing, streaming, AI tools, gaming and work. The table lists static facts only, with no latency or load figures.

90+Countries covered
220+Routes in total
UnlimitedDevices online at once
60 daysNo-questions refund

//Route list

Route samples grouped by region

The table below groups routes by region and lists representative lines in each. Line type determines how stable a route stays at peak hours: IEPL dedicated lines run on a private channel, relay routes hand off through optimised nodes, and direct routes land straight in the local data centre. The streaming column shows how each route performs on the listed platforms; whether 4K actually plays also depends on your account region and the title itself.

// Route samples · grouped by region
Country / Region City Line type Streaming support
Asia Pacific
Hong Kong SARHong KongIEPL dedicatedNetflix / Disney+ / HBO Max
JapanTokyoIEPL dedicatedNetflix / Disney+
JapanOsakaRelayNetflix
SingaporeSingaporeIEPL dedicatedNetflix / Disney+
South KoreaSeoulRelayNetflix
TaiwanTaipeiDirectNetflix / Disney+
MalaysiaKuala LumpurDirect—
ThailandBangkokDirectNetflix
North America
United StatesLos AngelesIEPL dedicatedNetflix / Disney+ / HBO Max
United StatesSan JoseRelayNetflix / Disney+
United StatesSeattleRelayNetflix
United StatesNew YorkIEPL dedicatedNetflix / HBO Max
CanadaTorontoRelayNetflix
CanadaVancouverDirectNetflix
Europe
NetherlandsAmsterdamIEPL dedicatedNetflix / Disney+
United KingdomLondonIEPL dedicatedNetflix / BBC iPlayer
GermanyFrankfurtRelayNetflix
FranceParisRelayNetflix / Disney+
ItalyMilanDirectNetflix
SpainMadridDirectNetflix
SwedenStockholmDirectNetflix
Other regions
AustraliaSydneyRelayNetflix / Disney+
IndiaMumbaiDirectNetflix
BrazilSão PauloDirectNetflix
United Arab EmiratesDubaiDirect—
South AfricaJohannesburgDirect—

//Line types

The three line types: how they work and how they differ

All three are cross-border routes, but IEPL dedicated, relay and direct lines run over completely different physical paths — which is also where most of the price and stability gap comes from. The three sections below cover how each works, when to use it, and why the cost differs. Understanding those differences is more useful than memorising city names.

01

IEPL dedicated lines

Top pick

IEPL stands for International Ethernet Private Line: a point-to-point Layer 2 channel from a local carrier facility to an overseas landing facility, with no public-internet routing in between and no sharing that bandwidth with other users. Traffic enters the line at the ingress and goes straight to the egress, so the hop count is fixed and the path is predictable — which is why the speed curve stays flatter at peak hours than on the public internet.

Best for
4K streaming, long video calls, sustained AI tool sessions and file uploads, and real-time work in cross-border store back offices.
Why it costs more
Dedicated lines are billed by bandwidth at several times the unit cost of ordinary internet, so they are only deployed to popular landing points such as Japan, Hong Kong, the US West Coast, Singapore and the Netherlands.
02

Relay routes

Widest coverage

Relay routes first push traffic over an optimised public-internet link to a relay node — usually at a backbone egress or a facility closer to the user — and the relay node then hands it on to the final landing point. It is effectively splitting one long public-internet hop into two shorter ones, sidestepping the segment most prone to congestion.

Best for
For cases where direct routes clearly slow down at peak hours but a dedicated line is overkill: web browsing, 1080p video, file sync, ordinary AI chat.
Why it costs more
Relay nodes are servers too, and their cost sits between dedicated and direct, which is why this type usually makes up the largest share of the list.
03

Direct routes

Most regions

Direct routes connect from the landing facility straight to the local carrier, taking the shortest path with no extra relay hop. Latency and stability depend entirely on the quality of the public internet between your local egress and that facility, which makes them the most sensitive to your own network.

Best for
Less popular regions — South America, the Middle East, Africa, South Asia — are mostly served by direct routes; in popular regions, direct routes are also perfectly good outside peak hours.
Why it costs more
Lowest cost, hence the widest regional coverage, and the best fit for backup duty and for filling in less common destinations.

//Choosing a route

Five tips for picking a route by use case

No route is universally better — only better matched to a use case. Below are recommendations for five common needs, each with the reasoning behind it. In practice, keep one dedicated line and one direct route on hand: the dedicated line for your main work, the direct route as backup and for less common regions.

// 01 Everyday browsing

Land nearby, cut the round trips

Looking things up, reading docs, opening a dashboard — these don't need much peak bandwidth, but they are sensitive to time to first byte. A page load involves several round trips, so every step you shave off the physical distance is clearly noticeable.

First choice Relay or direct routes in Hong Kong, Singapore or Japan

// 02 Streaming

A fixed egress, no buffering

4K playback needs sustained, steady bandwidth: the player keeps pulling the stream, and a single hiccup triggers buffering. A dedicated line's fixed path avoids peak-hour congestion on the public internet. Check the catalogue region first — Netflix, Disney+ and HBO Max libraries differ by region — so decide which region carries the title you want, then pick the matching landing point.

First choice IEPL dedicated lines in Japan, Los Angeles, Hong Kong or Amsterdam

// 03 AI tools

Long connections first

Services like ChatGPT, Claude and Gemini need a session that stays up, not peak bandwidth. If a conversation drops mid-way, the page errors out and you start over; Midjourney runs inside Discord, where uploading reference images and waiting for renders are both long tasks. Prefer a dedicated line with a fixed path so the egress doesn't switch mid-session and kill the conversation.

First choice Dedicated or relay routes in Los Angeles, San Jose, Tokyo or Singapore

// 04 Gaming

Land in the same region, shorten the path

Games are latency-sensitive and bandwidth-light. The logic is to find out which region the game servers sit in, then pick a landing point in that same region — the shorter the physical distance, the better. Logging in across regions adds a detour that usually isn't worth it.

First choice A dedicated or relay route in the same region as the game servers

// 05 Work

Stability first, many devices at once

Cross-border work is about stability: email, online documents, video meetings, back-office systems — any dropped connection interrupts the flow. One subscription allows unlimited devices online at the same time, so laptops, desktops and mobile devices can all stay connected without a separate plan for each.

First choice Dedicated lines in Hong Kong, Japan or Singapore, with a US route as backup

//Coverage

Coverage and popular routes

90+ countries and 220+ routes means most common destinations have a landing point. Below are the regions that appear most often in the route list; the full list is whatever your client shows.

  • Japan
  • Hong Kong SAR
  • United States
  • Singapore
  • Netherlands
  • Italy
  • United Kingdom
  • Germany
  • France
  • Canada
  • Australia
  • South Korea
  • Taiwan
  • Malaysia
  • Thailand
  • Vietnam
  • Philippines
  • Spain
  • Sweden
  • Turkey
  • Brazil
  • India
  • United Arab Emirates
  • South Africa

Popular regions usually offer both dedicated and relay lines; less common ones are mostly direct. When choosing, don't chase the biggest route count — check which region your target service sits in and whether that route stays available over time.

How the route list syncs with your subscription

A subscription link is a tokenised URL; each time the client updates the subscription it re-pulls the route list. When nodes are added or retired on the server side, one client update is enough to see the change — no reinstall and no signing in again.

Routes being retired and replaced is normal. Data-centre maintenance, upstream carrier changes, or a landing address in some region being blocked by a target platform all trigger adjustments. So the test of a healthy subscription isn't a node count that only ever grows, but whether your usual regions always have a working route.

Two ways to choose in the client

  • Automatic: the client picks whichever route its own speed test rates fastest right now — fine for everyday browsing and one-off use.
  • Manual: pin a specific route, which suits streaming, AI tools and anything else that needs a stable egress.

If a route has been unusable for several days, update the subscription in your client first; if it still fails, open a ticket with the route name, your region and a screenshot of the error. The full troubleshooting order is on the troubleshooting page, from a total failure to connect down to a single app not going through the proxy. New here? Start with the getting-started guide and work through the four steps — create an account, grab the subscription, import it into your client, verify the connection; pricing and data tiers are laid out in full on the plans and pricing page.

City names in the route table are samples only; the usable list is whatever your subscription delivers. One subscription can run on several devices at once — unlimited devices online at the same time — so a laptop, phone, tablet and desktop can share a single subscription.