Global nodes and routes, grouped by region
Routes are managed in groups for Asia Pacific, North America, Europe and other regions, 100+ countries / 210+ routes. This page lists representative routes from each group with type and streaming support noted for each one; the full list opens by region inside the client.
No email address required
Create an account with just a username and password
- 14-day refund, no questions asked
- Unlimited devices online at once
- Alipay / WeChat / USDT
- Asia Pacific
- North America
- Europe
- Middle East
- Latin America
- Africa
- Oceania
Coverage overview: 100+ countries and 210+ routes
VPNEQ routes are managed in geographic groups. Each region has at least two routes, and when a country or city has more than one, the route types usually differ so you can switch between them as network conditions change. The 32 routes on this page are representative picks from each group, covering Asia Pacific, North America, Europe and other regions. The full list opens by region inside the client, and routes added or retired sync with your configuration.
The route type determines which path a connection takes and how stable it stays at different times of day. IEPL dedicated lines run on a private channel and suit use cases that demand stability; transit routes enter through a nearby gateway and forward from there, balancing cost and speed; direct routes connect straight to the destination data center and work well for nearby, latency-sensitive use cases. See the Route types section below for how each type works and where it fits.
100+
Countries and regions covered
210+
Total routes
Unlimited devices
Devices online at once
14 days
No-questions-asked refund
This page lists static facts only: country, city, route type and streaming support. Latency on the same route varies widely by location and ISP, so a fixed number would be meaningless and is not shown here. The client displays live latency for the route you are on.
Asia Pacific route list
Asia Pacific is the busiest group. Hong Kong, Tokyo and Singapore all run IEPL dedicated lines with short paths and little variation through the day, which makes them good defaults. Tokyo and Singapore each have several routes, so if one fluctuates in the evening you can switch straight to another in the same region. Malaysia, Thailand, Vietnam and Indonesia are mostly direct routes, well suited to reaching local services nearby; Mumbai and Sydney are transit routes covering South Asia and Oceania.
| Country / Region | City | Route type | Streaming support |
|---|---|---|---|
| Hong Kong | Hong Kong | IEPL dedicated | ND+YS |
| Japan | Tokyo | IEPL dedicated | ND+YS |
| Japan | Osaka | Transit | ND+Y |
| Singapore | Singapore | IEPL dedicated | ND+YS |
| South Korea | Seoul | Transit | ND+Y |
| Taiwan | Taipei | Transit | ND+Y |
| Malaysia | Kuala Lumpur | Direct | NY |
| Thailand | Bangkok | Direct | NY |
| Vietnam | Ho Chi Minh City | Direct | Y |
| Indonesia | Jakarta | Direct | NY |
| India | Mumbai | Transit | NY |
| Australia | Sydney | Transit | ND+YS |
Streaming column: N = Netflix · D+ = Disney+ · Y = YouTube · S = Spotify
North America route list
North America covers both US coasts. Los Angeles and New York are IEPL dedicated lines, good for North American streaming services, developer tools and office systems; San Jose and Seattle are transit routes that serve as backups in the same region. Canada is covered by Toronto (transit) and Vancouver (direct) on either side, and Mexico City is a direct route for reaching localized services. The transpacific path is long, so start with a dedicated line and then compare routes in the same region based on your own results.
| Country / Region | City | Route type | Streaming support |
|---|---|---|---|
| United States | Los Angeles | IEPL dedicated | ND+YS |
| United States | San Jose | Transit | ND+Y |
| United States | Seattle | Transit | NY |
| United States | New York | IEPL dedicated | ND+YS |
| Canada | Toronto | Transit | ND+Y |
| Canada | Vancouver | Direct | NY |
| Mexico | Mexico City | Direct | NY |
Streaming column: N = Netflix · D+ = Disney+ · Y = YouTube · S = Spotify
Europe route list
Every European group combines at least two route types — an IEPL dedicated line plus a transit route. London and Frankfurt are dedicated lines and the main options for European streaming and regional services; Paris and Amsterdam are transit routes that back each other up; Zurich, Stockholm, Madrid and Milan are direct routes wired straight into the destination data center, which suits use cases that need a local European exit. Europe is a long haul, and routes in the same city can behave very differently when the network is congested, so try each one in the client and set the steadier route as your default.
| Country / Region | City | Route type | Streaming support |
|---|---|---|---|
| United Kingdom | London | IEPL dedicated | ND+YS |
| Germany | Frankfurt | IEPL dedicated | ND+YS |
| France | Paris | Transit | ND+Y |
| Netherlands | Amsterdam | Transit | NY |
| Switzerland | Zurich | Direct | NY |
| Sweden | Stockholm | Direct | NY |
| Spain | Madrid | Direct | NY |
| Italy | Milan | Direct | ND+Y |
Streaming column: N = Netflix · D+ = Disney+ · Y = YouTube · S = Spotify
Other regions routes
Beyond the three main regions, there are also routes landing in the Middle East, Latin America and Africa. Dubai and Istanbul are transit routes covering the Middle East and the Eurasia crossroads; São Paulo, Johannesburg and Tel Aviv are direct routes for reaching local services or serving as an exit for a specific region. These regions have fewer routes than Asia Pacific, North America and Europe, and they fluctuate more at peak times, so treat them as supplements rather than defaults.
| Country / Region | City | Route type | Streaming support |
|---|---|---|---|
| Türkiye | Istanbul | Transit | NY |
| United Arab Emirates | Dubai | Transit | NY |
| Brazil | São Paulo | Direct | NY |
| South Africa | Johannesburg | Direct | N |
| Israel | Tel Aviv | Transit | NY |
Streaming column: N = Netflix · D+ = Disney+ · Y = YouTube · S = Spotify
The 32 routes above are representative picks from each group. Coverage spans 100+ countries and 210+ routes; the full list opens in the client by region and route type, sorted by availability.
Route types: IEPL dedicated / Transit / Direct
A route type describes the path a connection takes from the entry point to the destination data center. In the same city, switching types changes path length, congestion risk and cost. The table below breaks down how each of the three types works, where it fits and how it is priced, so you can match one to your use case.
IEPL dedicated lines
- How it works
- Traffic between the entry point and the destination runs on a private channel provided by the carrier, so it does not compete with public internet traffic for bandwidth. The path is fixed with few detours, and the connection varies far less at peak evening hours than a regular public route.
- Best for
- Use cases that demand stability: long video meetings, large file transfers, 4K streaming, and AI tool sessions that need to stay connected. Also a good everyday default.
- Cost
- The highest bandwidth cost of the three types, so dedicated lines are usually deployed in major cities and are fewer in number. If a region offers both a dedicated line and a transit route, pick the dedicated line first.
Transit routes
- How it works
- Traffic first connects to a nearby entry node, which then forwards it to the destination data center. The entry-to-destination leg uses whichever public path is performing best at the time, balancing cost and speed.
- Best for
- Reaching a relay in the target region, covering cities that dedicated lines do not reach, and standing in as a same-region backup when a dedicated line fluctuates. Plenty for everyday browsing, social apps and standard video playback.
- Cost
- Cost sits between dedicated and direct, and transit is the main way to cover long-tail cities. There are many of them and plenty to switch between, which makes them useful for filling gaps inregional coverage.
Direct routes
- How it works
- The client connects straight to the destination data center with no extra forwarding node in between. The path is the shortest with the fewest hops, which suits nearby regions in particular.
- Best for
- Reaching local services nearby and use cases that need a local exit (local e-commerce, localized content, for example). At short distances it performs close to a dedicated line; over long distances it is more exposed to public path conditions.
- Cost
- The lowest cost of the three types, so it is the most widely deployed. Good as a supplementary exit and backup route, but not recommended as your only route for intercontinental use.
Choosing a route: match it to your use case
You do not have to test routes one by one from the top. Pick a region based on what you need, then choose a route type within it — two or three tries is usually enough. Below are route-picking notes for nine common use cases.
Everyday browsing and search
Just pick a dedicated line in the nearest major region. The path is short and varies little through the day, so page loads and search responses stay steadier and you do not need to switch often.
Streaming video
Pick the destination country by content catalog: Tokyo for Japan, Los Angeles or New York for the US, London or Frankfurt for European content. Prefer dedicated lines for fewer buffering pauses on 4K playback.
AI tool sessions
Choose a dedicated line in North America or Japan. These use cases are sensitive to connection continuity, and a fixed dedicated path is less likely to drop mid-session. Keep a transit route in the same region as a backup.
Online gaming
Pick the region closest to the game server, preferring direct and dedicated routes. Games are sensitive to latency jitter, so play a round on each route in the same city and lock in the one with less jitter.
Cross-border work and meetings
Meeting apps are sensitive to packet loss, so choose a dedicated line and keep it fixed — do not switch mid-meeting. If your local network is unstable, fix that before changing routes.
Mobile networks
Cellular connections hand off frequently, and a dedicated line reduces reconnects. On subways, trains and other moving setups, turn on auto-switch and let the client pick the steadier route at the moment.
Large files and update packages
Downloads use a lot of bandwidth, so choose a dedicated line and avoid peak evening hours. Do not run several downloads on one route at the same time — spreading them across regions is steadier.
Backup route planning
Keep one backup for each region you use often in the client, pairing a dedicated line with a transit route in the same city. When the primary fluctuates, switch with one tap instead of hunting for a node again.
Multiple devices at once
Unlimited devices can be online at the same time, but it is better to spread them across regions. Give your phone and computer separate routes so traffic on one does not crowd out the other.
FAQ
The cities in the route list differ from what I see in the client — which one should I trust?
Trust the list shown in the client. This page lists representative routes from each group to explain the coverage structure and route types; the in-client list updates in real time as routes change and shows current availability and latency.
Why does the same route perform differently at different times?
Cross-border paths pass through multiple public network segments and carrier interconnection points, and public paths get more congested during peak evening hours, which affects transit and direct routes more noticeably. Dedicated lines run on a private channel and vary less. When you hit a slowdown, switch to another route in the same region first — that usually restores things.
How do I choose between dedicated, transit and direct?
Choose dedicated for use cases that need stability and long sessions; transit for long-tail cities or as a backup; direct for reaching local services nearby or when you need a local exit. If unsure, start with a dedicated line and then compare routes in the same region based on your own results.
Does the number of routes change?
Yes. Routes are adjusted according to data center and carrier conditions, and additions and retirements sync through the client configuration with no manual update needed. Coverage stays at 100+ countries and 210+ routes.
Is plan traffic counted per route?
No. Traffic is counted per account, and all routes share the same allowance no matter how many you switch between. Monthly subscription traffic resets each month on your activation date, and data packs last until used up with no expiry.
The route list and client configuration are available after signing in. No email address required — create an account with just a username and password; 14-day refund, no questions asked.