Routes and Locations

Global routes and locations

VPN31's international network covers 100+ countries and 230+ routes. The table below groups the main cities by Asia Pacific, North America, Europe and Oceania, with the route type and streaming support for each. Latency and load depend on your local network and the time of day, so no fixed numbers are shown here; once connected, the client displays live results for your current route.

100+ countries 230+ routes Unlimited devices 14-day money-back guarantee

First Month Free View Plans

Route list

Main routes by region

The list below is a sample, not the full inventory. There are three route types: IEPL dedicated, relay and direct. The Streaming column shows how well each route handles the major platforms; Partial means the catalogue is incomplete, and actual playback is what counts. One city may offer more than one route type — just pick by what you need.

Asia Pacific

The nearest entry point for most users, covering Japan, Hong Kong, Singapore and the main Southeast Asian cities — the group people choose most often for everyday use. Shorter cross-border paths mean less waiting for pages to open and video to start.

Country / Region	City	Route type	Streaming
Japan	Tokyo	IEPL dedicated	Supported
Japan	Osaka	Relay	Supported
Hong Kong	Hong Kong	IEPL dedicated	Supported
Hong Kong	Hong Kong	Relay	Supported
Singapore	Singapore	Direct	Supported
Thailand	Bangkok	Direct	Partial

North America

Trans-Pacific paths landing on the US West and East coasts, with three Canadian cities as a supplement. When you use a service hosted in North America, pick a landing on the same side as the target.

Country / Region	City	Route type	Streaming
United States	Los Angeles	IEPL dedicated	Supported
United States	San Jose	Direct	Supported
United States	Seattle	Relay	Supported
United States	Dallas	Direct	Partial
United States	New York	Relay	Supported
Canada	Toronto	Direct	Supported
Canada	Vancouver	Relay	Supported
Canada	Montreal	Direct	Partial

Europe

Landings are concentrated in Germany, France and the Netherlands, covering the main Western European data centres, with Poland as a Central and Eastern European supplement. For European services, a landing in the target country is the simplest choice.

Country / Region	City	Route type	Streaming
Germany	Frankfurt	Relay	Supported
Germany	Berlin	Direct	Partial
Germany	Munich	Direct	Partial
France	Paris	Relay	Supported
Netherlands	Amsterdam	Direct	Supported
Poland	Warsaw	Direct	Partial

Oceania

Three Australian cities: Sydney and Melbourne run on relay, Perth on direct. Cross-continent paths are long, so it pays to settle on one route for the long term instead of switching back and forth.

Country / Region	City	Route type	Streaming
Australia	Sydney	Direct	Supported
Australia	Melbourne	Relay	Supported
Australia	Perth	Direct	Partial

Route type

How the three types differ

All three are international routes, but the path they take changes both cost and experience. The notes below cover how each one works, where it fits and what it costs — read the ones that match your use, there is no need to memorise them all.

IEPL dedicated

How it works Traffic enters a dedicated channel at the local entry point and runs straight to the overseas landing, skipping the congested nodes of the public internet. The path is fixed and maintained jointly by the provider and the carrier.

Best for Long video calls, cross-border remote work, large file transfers and 4K streaming at peak hours — anything that cannot afford a dropped connection.

Cost Dedicated bandwidth is bought by capacity, so the unit cost is higher than relay or direct; that is why it is only deployed in a handful of core cities.

Relay

How it works Traffic first goes to an intermediate node, usually in Hong Kong or Japan, which forwards it to the target landing. The middle leg runs on an optimised path; the landing leg is still the public internet.

Best for Cities with no direct or dedicated route but a good relay node nearby. This covers most common needs within Asia.

Cost Between dedicated and direct. The quality of the intermediate node sets the ceiling, so when choosing, node location matters more than node count.

Direct

How it works A direct connection from the local exit to the overseas data centre, with no extra hops. Shortest path, simplest setup and the widest city coverage.

Best for Everyday browsing and lookups where latency is not critical and a stable exit is all you need — also a good backup alongside your main route.

Cost The lowest of the three. The trade-off is that fluctuations on the cross-border public path show up directly in your experience, most noticeably at peak hours.

Route picks

Choosing a route by use case

The same group of routes behaves differently depending on what you do with it. Below are five common scenarios with a suggested order of choice — start with the default rule, then fine-tune it against what you actually see.

Everyday browsing and lookups: Start with the nearest direct or relay node. Web pages and search requests are not latency-sensitive, so stability beats speed; fix your usual node in place instead of switching by hand each time. If one site will not load, try another route in the same region before jumping to another continent.
Streaming video: Choose routes marked Supported, preferring IEPL dedicated and good relay nodes. 4K playback depends on sustained bandwidth rather than peak speed, so avoid crowded public landings at peak hours. Catalogues are tied to the region of your account, so confirm which region a target catalogue belongs to before switching.
AI tools: Chat tools are sensitive to connection stability — a long answer that drops halfway has to start over. Fix one low-jitter route instead of switching nodes often. If you hit a login error, try another route in the same region first; most of the time it is local link jitter rather than your account.
Gaming: Games care about round-trip latency and jitter, not bandwidth. Pick a route with a short physical distance and few hops, and keep the landing in the same region as the game server; dedicated routes usually jitter less at peak hours, so favour them for competitive matches.
Remote work and file transfers: For long online meetings and large uploads, use an IEPL dedicated route: the path is fixed and stays up. Uploads need headroom too, so while you are in a meeting, keep other devices on the same account from running downloads or system updates.

FAQ

Common route questions

Why are latency and load not shown on the page?

Latency depends on your local network, your carrier's exit and the time of day; a fixed number on a page would be useless to everyone. The client shows live measurements for the current route once connected. The page keeps only information that does not change with conditions — city, route type and streaming support all fall into that category.

What if the city I need is not in the table?

The table is a sample; the network actually covers 100+ countries and 230+ routes. Sign in to the client to filter by region and see the full list. If your target city is missing, pick the nearest city geographically — usually steadier than a cross-continent route. If you only need one specific service, you can also try a landing in a nearby country first.

What does Partial mean in the Streaming column?

It means part of a major platform's catalogue is available on that route, not all of it. Catalogues and licensing regions change, so actual playback is what counts. If you need reliable access, prefer routes marked Supported and stay on them — constant switching leads to repeated logins and extra verification prompts.

Can routes switch automatically?

The client supports manual selection and rule-based automatic selection. Automatic suits everyday browsing; for live streams, long meetings or large transfers where an interruption is costly, fix one route manually to avoid reconnects and waiting.

Is IEPL always faster than direct?

No. A dedicated route solves fixed paths and congestion detours; if your local network is unstable, it cannot fix that. The test is simple: connect to the dedicated and the direct route at the same time of day, do the same tasks, and keep whichever is steadier — the route type alone proves nothing.