Global routes

Server Nodes and Route Coverage

VPNCZ covers 120+ countries with 180+ international routes, grouped into Asia-Pacific, North America, Europe and other regions, and split into three route types: IEPL, relay and direct. You can switch region and city right in the client, and the current exit changes immediately. This page lists a sample of routes; the full list available to you is shown in the client after logging in.

Start Free View Plans
  • 30-day money-back guarantee
  • Bank-grade encryption
  • Alipay / WeChat Pay / USDT
  • Unlimited devices
No email address required — sign up with a username and password Windows / macOS / iOS / Android / Linux
120+ Countries covered
  • 180+ Routes
  • IEPL · Relay · Direct
  • Unlimited devices
  • 30-day money-back guarantee

View Routes by Region

The table below lists a sample of routes by region, with country/region, city, route type and confirmed streaming support. You can switch between cities in the same region and compare them one by one; the client remembers the one you used last. The route list changes as data center and bandwidth resources are adjusted, so the list shown in the client after logging in is the authoritative one.

Asia-Pacific

10 sample routes
Country / RegionCityRoute typeStreaming support
Japan Tokyo IEPL NetflixDisney+AbemaTV
Japan Osaka Relay NetflixYouTube
Hong Kong Central IEPL NetflixDisney+YouTube
Hong Kong Tsuen Wan Relay YouTubeHBO Max
Singapore Singapore Direct NetflixPrime Video
South Korea Seoul IEPL NetflixTVING
Taiwan Taipei Relay NetflixmyVideo
Malaysia Kuala Lumpur Direct NetflixYouTube
Thailand Bangkok Relay NetflixYouTube
Australia Sydney IEPL NetflixStan

North America

8 sample routes
Country / RegionCityRoute typeStreaming support
United States Los Angeles IEPL NetflixHuluHBO Max
United States San Jose Direct NetflixYouTube
United States Seattle Relay NetflixPrime Video
United States Dallas Relay HuluYouTube
United States New York IEPL NetflixHBO Max
Canada Toronto Relay NetflixCrave
Canada Vancouver Direct NetflixPrime Video
Mexico Mexico City Relay NetflixDisney+

Europe

11 sample routes
Country / RegionCityRoute typeStreaming support
United Kingdom London IEPL NetflixBBC iPlayer
Germany Frankfurt IEPL NetflixDisney+
Netherlands Amsterdam Direct NetflixYouTube
France Paris Relay NetflixCanal+
France Marseille Direct NetflixYouTube
Spain Madrid Relay NetflixMovistar+
Italy Milan Direct NetflixPrime Video
Sweden Stockholm Relay NetflixYouTube
Poland Warsaw Direct NetflixPrime Video
Switzerland Zurich Relay NetflixYouTube
Ireland Dublin Direct NetflixPrime Video

Other regions

7 sample routes
Country / RegionCityRoute typeStreaming support
Turkey Istanbul Relay NetflixYouTube
United Arab Emirates Dubai Relay NetflixPrime Video
Israel Tel Aviv Direct NetflixYouTube
South Africa Johannesburg Relay NetflixShowmax
Brazil São Paulo Relay NetflixGloboplay
Indonesia Jakarta Direct NetflixVidio
New Zealand Auckland Direct NetflixNeon

The table shows a sample of routes. The full set of 180+ routes is grouped by region in the client after logging in, where you can search by city and bookmark the ones you use most. A country or region usually has several city entries, so you can switch to another one in the same area when a route is busy — the exit region stays the same.

The Difference Between the Three Route Types

Every route in the client is labeled with a type: IEPL, relay or direct. These are not about “fast” versus “slow” — they describe how the path is built between your location and the exit. The sections below explain how each type works, what it suits and how the costs differ, so you can pick by use case.

IEPL Stability first

IEPL: a fixed point-to-point channel

IEPL (International Ethernet Private Line) is a fixed-bandwidth channel leased between two endpoints. Once traffic enters the line at the entry point, it no longer hops through the public internet and goes straight to the exit data center. Its value is not raw theoretical bandwidth but a fixed path: the route does not change just because one link on the public network is temporarily congested, so performance during the evening peak stays close to what you get in the early hours.

It suits continuity-sensitive work: long video meetings, remote work that must not drop a session, live sports where one buffer means missing the key moment, and repeated large-file uploads and downloads in cross-border collaboration. The trade-off is cost — IEPL is billed by fixed bandwidth rather than by actual traffic the way public routes are, so there are fewer of these routes in the plans, usually concentrated in major gateway cities.

Path
Entry → IEPL channel → Exit data center
Best for
Meetings, live streams, large files, long sessions
Cost
Leased by fixed bandwidth; highest unit cost
Relay Balanced choice

Relay: through an intermediate node before the exit

A relay route first sends traffic to an intermediate node, which then forwards it to the final exit. These nodes are usually placed in regions with good connectivity, and their job is to replace one unstable direct path with two shorter, more controllable ones. The trade-off is an extra hop, so relay performance depends on the quality of the link between the intermediate node and the exit.

It fits most everyday use: web browsing, social media, regular video streaming and AI tool chats. These are the most numerous routes here and cover the widest range of cities, making them the default all-purpose choice. If a route slows down at certain hours, switching to another city entry in the same country usually helps more than changing countries — the exit region stays the same while the relay node changes.

Path
Entry → Intermediate node → Exit
Best for
Browsing, video, AI tools, everyday work
Cost
Moderate; the most routes and the widest coverage
Direct Shortest path

Direct: one hop straight to the exit data center

A direct route adds no relay: traffic goes from the access point straight to the exit data center, giving the shortest path and the fewest hops. Its performance depends most on the quality of the public link between the access point and the exit data center — great when that link is clear, and immediately noticeable when it is congested. With no intermediate forwarding, direct routes usually cost less in bandwidth than IEPL.

It suits cases where the exit region is fixed and latency matters most: reaching a service available in one specific country, low-latency gaming, or downloading large files off-peak. Testing is simple — try both the direct and relay routes for the same country and use whichever feels smoother right now; switching in the client takes one click.

Path
Access point → Exit data center (one hop)
Best for
Region-specific access, gaming, off-peak downloads
Cost
Lower, but heavily affected by public link quality
How to read route names

In the client, each route is shown as “city + type”, for example “Japan · Tokyo IEPL” or “United States · Los Angeles Direct”. The city sets the exit region; the type sets how the path is built. For streaming, first pick a city in the region the platform requires, then look at which types that city offers — if a city has both IEPL and relay, try IEPL first.

How to Choose a Route by Use Case

No single route is best for every scenario. Below are suggested picks for five common use cases, in order — start with the first and move down if it does not fit. After each switch, open the target service once to confirm: the “Connected” status in the client only means the tunnel is up, not that the site sees the exit region you wanted.

Everyday browsing and social media

Start with the Asia-Pacific city closest to you — relay routes in Japan, Hong Kong or Singapore, for example. Shorter distance means a shorter round trip, a faster first byte and smoother scrolling. If you only open a few pages now and then, a direct route is enough; if you stay connected most of the day, a relay route is steadier because it is less sensitive to fluctuations on the public link.

  • First choice: Japan · Osaka Relay / Hong Kong · Tsuen Wan Relay
  • Alternative: Singapore · Singapore Direct
  • Tip: when a city has several entries, try them one by one and keep the smoothest right now

Streaming and video

For streaming, check the region the platform requires first, then the route type. Regional catalogs are decided by your exit region, so matching the region comes first. Once the region is set, prefer IEPL routes in that region — buffering mid-stream is the worst outcome, and a fixed path reduces those interruptions. 4K playback needs bandwidth, so pick IEPL or direct and avoid the busiest hours.

  • Japan content: Japan · Tokyo IEPL
  • United States content: United States · Los Angeles IEPL / United States · New York IEPL
  • Europe content: United Kingdom · London IEPL / Germany · Frankfurt IEPL
  • Tip: after switching regions, reload the player page so the platform re-checks your exit

AI tool chats

AI tools are fairly relaxed about region but much stricter about connection continuity: if a long conversation drops midway, the context can be lost. So prefer IEPL or a stable relay route here rather than switching often. Uploading long documents or generating images produces a lot of upstream traffic, so avoid peak hours.

  • First choice: United States · Los Angeles IEPL / Japan · Tokyo IEPL
  • Alternative: United States · San Jose Direct / Singapore · Singapore Direct
  • Tip: do not switch routes mid-conversation — switching rebuilds the session

Gaming and low-latency use

What gaming needs comes down to two things: a stable round-trip time and no packet loss. Neither is solved by “more bandwidth”, so the logic differs from streaming — prefer direct routes with few hops and a short path, then IEPL in the same region as the game server. If a single match feels fast and then slow, an intermediate link is probably fluctuating; changing the entry city usually helps more than tweaking client settings.

  • First choice: a direct route in the same region as the game server
  • Alternative: IEPL in the same region (fixed path, less fluctuation)
  • Tip: confirm the game server's region first, then pick a matching city entry

Cross-border work and remote collaboration

Work is the most stability-sensitive scenario: a dropped video call, an interrupted push to a code repository or a failed cloud document sync all break the flow. For this, use one IEPL route consistently and keep another route in the same region as a backup to switch to manually if the main one misbehaves. For teams, note that this service allows unlimited devices — several devices can connect at once, each choosing the region it needs.

  • First choice: IEPL in the region where your company's resources live
  • Alternative: another city entry in the same country or region
  • Tip: note down the routes you use most so you are not scrolling the list every time

Coverage at a Glance

Below are some of the countries and regions where routes are deployed, grouped by macro-region. A country usually has several city entries, and the client lets you collapse or expand by country. The list changes with data center resources; the client after logging in shows the actual available coverage.

Asia-Pacific

  • Japan
  • Hong Kong
  • Singapore
  • South Korea
  • Taiwan
  • Malaysia
  • Thailand
  • Indonesia
  • Vietnam
  • Philippines
  • India
  • Australia
  • New Zealand

North America

  • United States
  • Canada
  • Mexico

Europe

  • United Kingdom
  • Germany
  • Netherlands
  • France
  • Spain
  • Italy
  • Sweden
  • Poland
  • Switzerland
  • Ireland
  • Austria
  • Denmark
  • Finland
  • Norway
  • Czechia

Other regions

  • Turkey
  • United Arab Emirates
  • Israel
  • South Africa
  • Brazil
  • Argentina
  • Chile

The list above is a sample. Full coverage is 120+ countries and 180+ routes. In the client they are grouped by macro-region and you can search by city name; multiple entries in one country or region let you switch when a route is busy while the exit region stays the same.

Route FAQ

Common questions about node counts, choosing routes and switching. More answers in the Help Center.

Do all plans include the 180+ routes?

Routes are not tiered by plan. All three monthly subscriptions (¥9.9/month for 60GB, ¥18/month for 250GB, ¥28/month for 500GB) can reach all 180+ routes; the only difference is the monthly data allowance. Data resets every month on your activation date, and if you upgrade mid-cycle the price difference is prorated over the remaining days.

What is the difference between several city entries in the same country?

Same exit region, different paths. Japan, for example, has two entries, Tokyo and Osaka: Tokyo offers IEPL and Osaka is relay. They connect to different data centers, so when one is smoother at a given time you can just switch — the exit region stays the same and you do not need to sign in to the target service again.

Does the route list change?

Yes. When data center and bandwidth resources are adjusted, individual city entries may be added or retired, and the list in the client updates accordingly. This page shows a sample of routes; the client after logging in shows the actual available list.

How do I know which streaming services a route supports?

The table on this page lists confirmed platforms for some routes. Regional streaming catalogs are decided by your exit region, so matching the region is step one and choosing the type is step two. After switching regions, reopen the player page so the platform re-detects your exit.

Can several devices use different routes at the same time?

Yes. This service allows unlimited devices: Windows / macOS / iOS / Android / Linux devices can connect at the same time, each choosing the region and route it needs. Device management is available in the user panel after logging in.

What should I try first when a route will not connect?

Switch to another city entry in the same country first, then to other cities in the same macro-region, and only then change macro-region — most problems come from a single link fluctuating temporarily, and another entry fixes it. If no route connects at all, work through the troubleshooting page step by step.

Other questions? Go to the Help Center, or work through the troubleshooting steps one by one: Full Troubleshooting Guide.

Plans

From ¥9.9/month; data packs never expire

Three monthly subscriptions and three data packs. Every route included at no extra cost, with a 30-day money-back guarantee.

View Plans → Get started

Step by step, from sign-up to importing your subscription

No email address needed to sign up — just a username and password. After importing, verify connectivity once per platform.

View Guides → Feature

AI tools: access and stability

How to reach chat and image-generation tools, their regional requirements and common error fixes.

View the AI Tools guide →
VPNCZ

120+ countries / 180+ routes, unlimited devices, bank-grade encryption, 30-day money-back guarantee.

Start Free View Plans
Start Free