No email address required · Just pick a username

Global route and server list

110+ countries / 150+ routes, grouped into Asia Pacific, North America, Europe and other regions. Each row shows the city, route type and streaming support, so you can see the differences before deciding which one to connect to.

Try for Free View Plans
  • 7-day no-questions-asked refund
  • Anonymous, no logs
  • Unlimited devices
  • Alipay / WeChat Pay / USDT
  • Japan
  • Singapore
  • United States
  • Hong Kong
  • Italy

Nodes & Routes

Route table grouped by region

The table below is an excerpt from the route pool, covering four groups of common cities: Asia Pacific, North America, Europe and other regions. Its purpose is to help you decide which region to connect to before you buy — not to read through all 150+ routes one by one. The complete route list is grouped by region inside the client, where you can view and switch between routes right after logging in.

Asia Pacific 14 in table

Country / RegionCityRoute typeStreaming support
Japan Tokyo IEPL Dedicated NetflixYouTube 4KChatGPT
Japan Osaka Relay NetflixYouTube 4K
Singapore Singapore Relay NetflixDisney+ChatGPT
Hong Kong Hong Kong IEPL Dedicated NetflixYouTube 4KTikTok
Taiwan Taipei Direct YouTube 4KDisney+
South Korea Seoul IEPL Dedicated NetflixChatGPT
Malaysia Kuala Lumpur Relay NetflixDisney+
Thailand Bangkok Relay NetflixYouTube 4K
Vietnam Ho Chi Minh City Direct YouTube 4K
Philippines Manila Relay Netflix
India Mumbai Relay NetflixPrime Video
Indonesia Jakarta Direct Netflix
Australia Sydney Relay NetflixDisney+ChatGPT
New Zealand Auckland Direct Netflix

North America 10 in table

Country / RegionCityRoute typeStreaming support
United States Los Angeles IEPL Dedicated NetflixDisney+HBO MaxChatGPT
United States San Jose Relay NetflixYouTube 4KChatGPT
United States Seattle Relay NetflixPrime Video
United States Dallas Direct NetflixHBO Max
United States New York Relay NetflixDisney+ChatGPT
United States Chicago Direct NetflixYouTube 4K
United States Miami Direct NetflixPrime Video
Canada Toronto Relay NetflixDisney+
Canada Vancouver Direct NetflixChatGPT
Mexico Mexico City Direct Netflix

Europe 12 in table

Country / RegionCityRoute typeStreaming support
United Kingdom London IEPL Dedicated NetflixDisney+ChatGPT
Germany Frankfurt Relay NetflixChatGPT
France Paris Relay NetflixDisney+
Netherlands Amsterdam Relay NetflixChatGPT
Italy Milan Direct NetflixPrime Video
Spain Madrid Direct Netflix
Sweden Stockholm Direct NetflixSpotify
Switzerland Zurich Relay NetflixChatGPT
Poland Warsaw Direct Netflix
Ireland Dublin Direct NetflixChatGPT
Turkey Istanbul Direct Netflix
Russia Moscow Direct YouTube 4K

Other regions 9 in table

Country / RegionCityRoute typeStreaming support
United Arab Emirates Dubai Relay NetflixChatGPT
Israel Tel Aviv Direct Netflix
Saudi Arabia Riyadh Direct Netflix
South Africa Johannesburg Direct Netflix
Egypt Cairo Direct Netflix
Nigeria Lagos Direct YouTube 4K
Brazil São Paulo Direct NetflixPrime Video
Argentina Buenos Aires Direct Netflix
Chile Santiago Direct Netflix

The streaming column in the table marks the platforms a route can usually reach. Regional rules on content platforms change, so the marks are a guide only — what actually opens is what counts. The meaning of each route type (IEPL dedicated / relay / direct) is explained in the next section.

Line Types

Three route types: dedicated, relay, direct

Route type describes how a route travels: where it goes first from your device, and where it exits. It decides how stable the route is at peak times, what it suits, and what it costs. The three types carry different labels in the client, so you can tell them apart by label when switching.

IEPL Dedicated

How the path works
Between the entry and exit data centres, traffic runs on a private channel with fixed links at both ends, so it does not compete for the congested exchange points on the public internet. The path is pre-arranged and does not reroute when public routing shifts.
Best for
4K streaming at peak hours, long-running AI tool sessions, video calls, and remote work or development sessions that need to stay connected for hours.
Cost
The highest bandwidth cost of the three types, so it is deployed only in core cities (Tokyo, Hong Kong, Los Angeles, London, Seoul and others). Plans are metered by data usage, and using a dedicated route does not consume extra data.

Relay

How the path works
Traffic first connects to a relay entry point close to you, and the relay node then forwards it to the exit over an optimised path. The first leg is short and the second follows an optimised path, balancing cost against stability.
Best for
Most everyday use: web browsing, YouTube 4K, Netflix, AI tools such as ChatGPT, cross-border shopping and overseas SaaS dashboards.
Cost
Cheaper than dedicated routes and dearer than direct ones, so it is the largest group in the route pool and covers the widest range of cities (Singapore, Frankfurt, Sydney, Dubai and others).

Direct

How the path works
The client connects straight to the exit node with no relay hop in between. The path is the shortest and the overhead the lowest; how it feels in practice depends on the state of the public network between you and that node at the time.
Best for
Regions that are close by and have good local network quality; nodes in less common countries and regions are mostly direct, which makes them the best fit for reaching local services and local content or checking regional business details.
Cost
The lowest cost, so it has the widest coverage — most of the 150+ routes are direct nodes, including several cities across the Middle East, Africa and South America.

Quick rule of thumb: start with the use case, then the distance. For long sessions that must not drop (AI tools, meetings, remote development), pick a dedicated route first; for everyday browsing and streaming, a relay is enough; to reach a local service in a specific country or region, pick the direct node in that country that is closest to you.

How to Pick

Choosing by use case: recommendations for five scenarios

The same route performs differently depending on what you use it for: video suffers when bandwidth dips, AI tools suffer when a long connection drops, games suffer from round-trip latency. Below are route picks for five common use cases, in order of preference. The client enables automatic route selection by default; use these suggestions as a reference when you want to choose manually.

Everyday browsing: the nearest relay route is the simplest choice

Looking things up, reading the news and sending overseas email do not need much bandwidth — they need to work the moment you open them. A relay route in Japan, Hong Kong or Singapore nearby is enough, and the client's automatic selection will land in those regions anyway. The test is simple: if the first screen of a page loads within two or three seconds, the route is fine.

  • Priority order: Japan · Osaka → Hong Kong → Singapore
  • If one site loads slowly, switch to another route in the same region first — don't jump to another continent
  • When you need a page in a local language, pick a direct node in that country

Coverage

Entry points across 110+ countries

The route pool covers 110+ countries and 150+ routes; the table lists only common cities. Where a country has several cities, prefer the entry point that is geographically closer — it decides the leg from you to the start of the route; what happens after that start is decided by the route type. Below are some of the countries and regions covered.

  • Japan
  • South Korea
  • Singapore
  • Hong Kong
  • Taiwan
  • Malaysia
  • Thailand
  • Vietnam
  • Philippines
  • Indonesia
  • India
  • Australia
  • New Zealand
  • United States
  • Canada
  • Mexico
  • Brazil
  • Argentina
  • Chile
  • United Kingdom
  • Ireland
  • France
  • Germany
  • Netherlands
  • Switzerland
  • Italy
  • Spain
  • Sweden
  • Poland
  • Turkey
  • United Arab Emirates
  • Israel
  • Saudi Arabia
  • Egypt
  • South Africa
  • Nigeria

Why the table only lists 45 routes

The 150+ routes in the pool include several different entry points and protocol combinations for the same city. Listing them all would turn the page into an endless read, so only common cities and representative route types appear here. The full list is grouped by region in the client — log in and you can see it and switch directly, with no manual configuration.

Route maintenance and additions

The route pool is maintained and expanded continuously: cities and route types stay stable, and new regions sync automatically in the client with no need to re-download the subscription. If your usual region has no route yet, open a ticket in the user panel describing what you need it for, and expansion will take it into account.

FAQ

Route FAQ

The number of routes doesn't match the table I see — is it inflated?

The table shows common cities and representative routes, so it is an excerpt; the 150+ figure includes several different entry points and protocol combinations for the same city. The full list is grouped by region in the client, where you can see the entries and switch between them one by one after logging in. The table does not list live figures such as latency or load, because those change with time and with your own network, and hard-coding them on a page would tell you nothing.

How do I know which route suits me?

The client enables automatic route selection by default and picks a working route based on your current network, which is enough for most people. To choose manually, follow the suggestions above: decide the use case (browsing / streaming / AI tools / gaming / work), then the region, then look at the route type label. Try one or two alternatives in the same region and you will usually find the right one within minutes.

How many devices can one subscription connect at the same time?

Unlimited. One subscription works on Windows, macOS, iOS, Android and Linux at the same time, so phone and computer do not need to log in and out. To give different devices different routes, just pick separately in each client — they do not affect each other.

What do the streaming marks in the table mean?

They mean the route can usually reach that platform. Regional rules on content platforms change from time to time, and the same platform has different libraries in different regions, so the marks are a guide for choosing a route — what actually opens is what counts. If a platform will not open, try another route in the same region with the same mark first.

If you can't connect or the speed is slow, what's the first step?

First switch to another route in the same region in the client — the same city often has several entry points, and switching avoids the current one's fluctuations. Then check that the client is up to date and that your local network is working (try opening an ordinary web page without the route, for example). If two or three routes still fail, open a ticket in the user panel with your region, the service you are trying to reach and the routes you have already tried.

Can a route be removed while I'm using it?

The route pool is maintained by city and route type; individual entry points go offline briefly during upgrades or adjustments, and the client syncs the latest list automatically — you do not need to fetch the subscription again. Data on purchased plans resets monthly from the activation date, and route changes do not affect data you have already bought. If it is not right for you, you can request a refund under the refund terms within 7 days of your first payment.

Not sure which plan to pick? Start with plans and data packs, or go straight to the setup guides to see how to import the subscription in each client. For the protocol-level trade-offs, read the route and protocol reference.

Try for Free