Servers

Routes and servers at a glance

Route lists grouped by region, how the three route types differ in design and cost, and which to pick for each use case. The table shows a sample only; the full list lives in the client.

100+ countries 220+ routes Unlimited devices 30-day money-back guarantee No email address required

Route table

Routes by region

Four groups cover Asia Pacific, North America, Europe and the rest of the world. Each row gives the country and city, the route type, and how well that city's routes handle major streaming services.

Routes grouped by region · Sample only
Country / Region City Route type Streaming
Asia Pacific
SingaporeSingaporeIEPL DedicatedNetflix · Disney+
JapanTokyoRelayNetflix · YouTube 4K
JapanOsakaIEPL DedicatedNetflix
Hong KongHong KongIEPL DedicatedNetflix · Disney+ · HBO Max
South KoreaSeoulRelayNetflix
TaiwanTaipeiDirectYouTube 4K
MalaysiaKuala LumpurDirectNetflix
ThailandBangkokDirect—
IndiaMumbaiRelay—
North America
United StatesLos AngelesIEPL DedicatedNetflix · Hulu · HBO Max
United StatesSan JoseRelayNetflix
United StatesSeattleDirect—
United StatesNew YorkRelayNetflix · Disney+
CanadaTorontoRelayNetflix
CanadaVancouverDirect—
Europe
United KingdomLondonRelayBBC iPlayer · Netflix
GermanyFrankfurtIEPL DedicatedNetflix
NetherlandsAmsterdamRelayNetflix
FranceParisDirectNetflix
ItalyMilanRelayNetflix · DAZN
SpainMadridDirect—
SwedenStockholmDirect—
PolandWarsawDirect—
SwitzerlandZurichRelay—
Other
AustraliaSydneyRelayNetflix
New ZealandAucklandDirect—
United Arab EmiratesDubaiRelay—
TurkeyIstanbulDirect—
BrazilSão PauloDirect—
ArgentinaBuenos AiresDirect—
South AfricaJohannesburgDirect—

The table describes route attributes only: country, city, route type and streaming support. Routes change as capacity is added or adjusted, so the list inside the client is always the latest; overall coverage is 100+ countries and 220+ routes.

Route type

Three route types

Every connection runs from your location to the target service, and how the middle leg travels decides stability, path length and cost. The three types are set out below by design, best use and cost.

01 · Dedicated

IEPL Dedicated

A private, fixed-bandwidth channel runs between the entry point and the exit node, with link quality governed by the carrier's service level.

How it works
An International Ethernet Private Line builds a point-to-point channel between the two ends and skips the public internet's intermediate hops. Jitter at peak hours is therefore much lower than on an ordinary path, and throughput sits closer to the rated bandwidth.
Best for
Long-lived sessions: 4K streaming, cross-border work, video calls. Pick it first when continuity matters more than price.
Cost
The highest of the three, billed by fixed bandwidth. Dedicated lines are therefore laid only in major hub cities such as Singapore, Tokyo, Hong Kong, Los Angeles and Frankfurt.

02 · Relay

Relay routes

The entry point sits close to the user, the middle leg runs over an optimised forwarding path, and an exit node completes the chain.

How it works
The client connects first to a nearby entry node, and traffic is forwarded over an optimised link to the exit. That is one hop more than a direct route, but the middle leg is usually steadier than the public international gateway.
Best for
Medium- and long-haul access to North America and Europe. When a direct route wobbles at peak hours, a relay in the same region is often the steadier choice.
Cost
Moderate. The extra hop is handled on the service side, with nothing to configure on the user's end — select it in the client and it works.

03 · Direct

Direct routes

The client connects straight to the exit node, with no extra forwarding in between.

How it works
Shortest path, lowest protocol overhead, no intermediate node involved. Real-world performance depends entirely on the state of the local international gateway at that moment.
Best for
Short distances, good gateway conditions, and lightweight tasks that are sensitive to path length, such as page loads, short requests and lookups.
Cost
The lowest of the three. With no middle-leg bandwidth cost, direct routes are the most widely deployed and cover the most cities.

Which route to pick

Picking a route by use case

Start with the region the target service sits in, then decide how the path should travel. For the same task, route types differ mainly in peak-hour stability, not in whether the connection succeeds at all.

First choice · Direct / Relay

Everyday browsing and search

>

Page loads and search requests are short and highly concurrent, so favour a nearby entry point. Use Asia Pacific routes for sites in Asia and relays for Europe and North America, saving dedicated bandwidth for tasks that need sustained throughput.

First choice · IEPL Dedicated / Relay

Video and streaming

4K playback needs sustained, steady bandwidth, and peak hours are the real test. Prefer the cities marked for Netflix, Disney+ and YouTube 4K; if buffering starts, switch to a dedicated route in the same region before considering another region.

First choice · Relay / IEPL Dedicated

AI Tools

Chat tools hold long-lived connections, with waits between request and response. Switching exits mid-session tends to break context, so pick one route and keep it until the session ends — that works better than testing routes over and over.

First choice · Direct

Gaming

Games are the most sensitive to round-trip latency and packet loss, so the shorter the path the better. If a direct route jitters at peak hours, move to a relay, then start a fresh match before judging the result — never switch mid-match.

First choice · IEPL Dedicated

Work and remote collaboration

Video meetings and file sync are long sessions where a drop costs more than a bandwidth peak. A dedicated line's fixed bandwidth suits all-day use; fall back to a relay when travelling or on a temporary network.

View plans Troubleshooting

Coverage

Regions covered

Coverage spans 100+ countries and 220+ routes. Below are the regions commonly seen in the route table and in the client, to help you check whether a target service is covered; the client holds the full list.

Singapore Japan South Korea Hong Kong Taiwan Malaysia Thailand Vietnam Philippines Indonesia India Australia New Zealand United States Canada Mexico Brazil Argentina Chile United Kingdom Germany France Netherlands Belgium Switzerland Austria Sweden Norway Denmark Finland Poland Czechia Spain Portugal Italy Greece Turkey United Arab Emirates Israel South Africa Egypt

How to use

Switching routes and self-checks

Switching routes is not a one-click affair: update the subscription to get the latest list, choose entry and exit by use case, then confirm the exit lands in the region you expect.

Update the subscription

Update the subscription manually in the client to pull the latest route list. The subscription URL is only available in the user panel; if the update fails, first confirm your local network works, then work through the subscription section of the troubleshooting page item by item.

Pick the exit first, then the entry

The exit decides which region the target service sees; the entry decides how the path travels. For a service in the United States, choose a North American exit first, then pick between direct, relay and dedicated entries — doing it the other way round wastes a round of effort.

Verify the exit region

After connecting, confirm on the IP lookup page that the exit region matches what you expect. If the exit is still local, the rule mode did not match that app — go back to the client's rule list and check the routing settings.

Compare across time slots

Test the same task once at peak hours and once off-peak, and note which route holds up better. Route quality shifts with time of day, so one test proves little — and a single result should not be used to write a route off.

Settle on a few go-to routes

Fix two or three routes as your defaults and keep the rest as backups. Constant switching makes the client rebuild connections over and over, which hurts the experience; disconnect before connecting to a new route.

FAQ

Route questions

Why isn't the city I need in the route table?

The table lists sample cities only; the full route list is grouped by region inside the client and covers 100+ countries and 220+ routes. If you need a specific region, find it in the client first, then decide the route type by use case.

How do IEPL dedicated, relay and direct routes differ?

A dedicated line runs over a private, fixed-bandwidth channel with link quality governed by the carrier's service level, and costs the most; a relay adds one hop between entry and exit, with an optimised middle leg; a direct route forwards nothing extra, takes the shortest path, and depends entirely on the local international gateway.

What affects how a route performs?

Local international gateway quality, the region the target service sits in, the time of day, and the route type you choose. This page does not display metrics that fluctuate over time — judge by actual use. If things stay slow, work through the troubleshooting page step by step, then compare route types.

Do I need to pick routes separately for each device?

Devices are unlimited: one subscription works on several devices at once, and each device picks its own route. Phones and computers usually target different services, so there is no need to keep the same route across them.

Is there a refund guarantee on subscriptions?

30-day money-back guarantee; see the refund policy for the process. Data packs last until used up and never expire, while monthly plans reset their data on the activation date each month — two different billing models, so pick whichever fits your usage.