Global nodes

Global Nodes and Route Coverage

100+ countries and 170+ routes, grouped into Asia Pacific, North America, Europe and other regions. Below we explain what dedicated, relay and direct routes each solve, then give the order to judge a route by use case. The live list in your panel is the source of truth for what is available right now.

100+ countries
170+ routes
60-day money-back guarantee

Route types

What dedicated, relay and direct routes each solve

The difference is not simply "fast or slow" — it is how the path is built and how stable it stays at peak hours. Read the difference once, then pick by use case instead of switching routes over and over.

IEPL dedicated

End-to-end on a private line, no shared public exit

Stable latency, low packet loss and little evening-peak swing. Suited to 4K streaming, video calls and long large-file transfers. Bandwidth is allocated per plan, and this is the most expensive of the three.

Relay

Join nearby, then leave on an optimised path

You connect to a nearby relay node first, and an optimised path forwards to the destination. Stability sits between dedicated and direct, price sits in the middle, and it suits everyday browsing, social apps and AI tools.

Direct

Straight to the destination data centre, shortest path

Lowest cost and the widest country coverage, good for nearby access and as a backup route. Quality follows the public internet, so evening peaks may be less steady than a dedicated line.

By region

Representative routes in four regions

Each region below lists a few representative cities and route types to show how coverage is structured — this is not the full list. A single country usually has several routes, sorted by latency and load in the panel.

Asia Pacific

07 ROUTES

Country / region	City	Route type	Best for
Japan	Tokyo	Dedicated	4K streaming, AI tools
Japan	Osaka	Relay	Everyday browsing, gaming
Singapore	Singapore	Dedicated	SE Asia work, video calls
Hong Kong SAR	Hong Kong	Relay	Low-latency access, streaming
South Korea	Seoul	Direct	Nearby access, backup
Taiwan	Taipei	Relay	Chinese-language sites, browsing
Australia	Sydney	Direct	Southern-hemisphere sites

North America

05 ROUTES

Country / region	City	Route type	Best for
United States	Los Angeles	Dedicated	4K streaming, AI tools
United States	San Jose	Relay	Developer services, cloud consoles
United States	New York	Relay	East-coast sites, office work
Canada	Toronto	Direct	North American content, backup
Mexico	Mexico City	Direct	Latin American sites

Europe

05 ROUTES

Country / region	City	Route type	Best for
United Kingdom	London	Dedicated	European streaming, office work
Germany	Frankfurt	Relay	European business, cloud services
Netherlands	Amsterdam	Relay	European nodes, downloads
France	Paris	Direct	Western European sites
Switzerland	Zurich	Direct	Privacy-friendly sites, backup

Other regions

03 ROUTES

Country / region	City	Route type	Best for
United Arab Emirates	Dubai	Relay	Middle East sites, cross-region work
Brazil	Sao Paulo	Direct	Latin American content
South Africa	Johannesburg	Direct	African sites

Scope note: the tables above are a structural sample; routes change with load and maintenance. The live list in your panel is the source of truth for available countries, cities and route types.

How to choose

Four steps to pick a route by use case

You do not need to test all 170+ routes. Judge in the order below and two or three tries usually settle it.

Fix the destination first, then the route type. Decide which country's sites you need, filter to that country, then choose between dedicated, relay and direct by use case.
Judge by time of day, not by one speed test. An afternoon number says nothing about the evening peak. Run each candidate in your usual hours and compare the spread, not the peak.
Size bandwidth by devices and concurrency. Count a phone and a laptop online together, and everyone at home sharing the line. Budget about 25 Mbps per 4K stream and about 4 Mbps per video call.
Keep one backup route. When the primary route goes into maintenance you switch straight over instead of hunting. Pick a different city or a different route type so both are not affected at once.

FAQ

Four questions about nodes and routes

Why does the route count differ from the list on this page?

This page lists representative cities to show how coverage is structured. 100+ countries and 170+ routes is the total of all available routes; the full list lives in the panel, sorted by latency and load.

Why are there several routes in the same region?

One city can have dedicated, relay and direct paths at the same time, aimed at different use cases. Multiple routes also spread load: when one is congested you switch to another without changing country.

Is a dedicated route always faster than a relay?

A dedicated line wins on stability rather than peak speed. The path is shorter and does not share a public exit, so evening peaks swing less; but if the destination sits near the relay node, the relay may measure lower latency. Trust your own measurements in your usual hours.

Do I need to reconfigure the client when I change routes?

No. The subscription link stays the same — just pick another node in the client, and configuration and rules update with the subscription. On a new device, import the same subscription link.