A directory of cross-border routes in 120+ countries
Routes are grouped by region and written into the directory after being checked one by one. The table below records only static facts that don't change over time — country, city, route type and streaming support; latency in milliseconds, load and online user counts are not shown on the page, so sign in to the user panel when you need current status.
Route directory: grouped by region
Below is an excerpt from the route directory, grouped into Asia-Pacific, North America, Europe and other regions. Each route records four static facts: its country, city, route type and streaming support. The directory holds 220+ routes covering 120+ countries; what's listed here are the common entry points for each region. The complete list, drawn from the same source, is available in the user panel once you sign in.
The directory deliberately leaves out latency in milliseconds, load percentages and online user counts: these numbers shift with your local network, the time of day and route load, so a fixed value on the page has no reference value and is easily misread as a promise. When choosing a route, what matters more is the route type and the exit region — neither changes from moment to moment.
Asia-Pacific
Asia-Pacific routes are the most common entry point for international sites and streaming: the physical distance is short, the round trip is brief, and jitter during peak hours is usually the smallest. The IEPL dedicated lines in Hong Kong and Tokyo handle the scenarios that demand the most stability; Singapore and Seoul cover Southeast and Northeast Asian streaming libraries; direct and relay routes in Bangkok, Kuala Lumpur, Mumbai and Sydney serve cases that need a closer local exit.
| Country / Region | City | Route type | Streaming support |
|---|---|---|---|
| Hong Kong | Hong Kong | IEPL dedicated line | Netflix · Disney+ · YouTube |
| Hong Kong | Hong Kong | BGP relay | Netflix · YouTube |
| Japan | Tokyo | IEPL dedicated line | Netflix · Disney+ · YouTube |
| Japan | Osaka | Direct | Netflix · YouTube |
| South Korea | Seoul | Relay | Netflix · YouTube |
| Singapore | Singapore | IEPL dedicated line | Netflix · Disney+ · YouTube |
| Malaysia | Kuala Lumpur | Direct | Netflix · YouTube |
| Thailand | Bangkok | Direct | Netflix · YouTube |
| Vietnam | Ho Chi Minh City | Relay | YouTube |
| India | Mumbai | Direct | Netflix · YouTube |
| Australia | Sydney | Relay | Netflix · Disney+ · YouTube |
| New Zealand | Auckland | Direct | Netflix · YouTube |
North America
North America has the most routes, spread across the West Coast, the central region and the East Coast. Los Angeles and San Jose suit sites that mainly face the Pacific; New York and Toronto serve cases that need an East Coast exit, such as the regional checks some AI tools run and US streaming libraries; Dallas and Chicago take on traffic distribution for the central region. Keeping several routes within one country means you can switch directly when one entry point gets crowded, instead of everyone piling onto a single exit.
| Country / Region | City | Route type | Streaming support |
|---|---|---|---|
| United States | Los Angeles | IEPL dedicated line | Netflix · Disney+ · YouTube |
| United States | San Jose | Relay | Netflix · YouTube |
| United States | Seattle | Direct | Netflix · YouTube |
| United States | Dallas | Relay | Netflix · YouTube |
| United States | New York | Relay | Netflix · Disney+ · YouTube |
| United States | Chicago | Direct | Netflix · YouTube |
| Canada | Toronto | Relay | Netflix · YouTube |
| Canada | Vancouver | Direct | Netflix · YouTube |
| Mexico | Mexico City | Direct | Netflix · YouTube |
Europe
European routes radiate from three hubs: London, Frankfurt and Amsterdam. When you need European services, European streaming libraries or European data sources, pick these three cities first; Madrid and Milan in the south and Stockholm and Zurich in the north serve as direct and relay entry points for cases that need a closer local exit. Europe is physically farther from mainland China than Asia-Pacific, so treat these routes as on-demand options rather than daily workhorses.
| Country / Region | City | Route type | Streaming support |
|---|---|---|---|
| United Kingdom | London | IEPL dedicated line | Netflix · Disney+ · YouTube |
| Germany | Frankfurt | IEPL dedicated line | Netflix · Disney+ · YouTube |
| Netherlands | Amsterdam | Relay | Netflix · YouTube |
| France | Paris | Relay | Netflix · Disney+ · YouTube |
| Switzerland | Zurich | Direct | Netflix · YouTube |
| Sweden | Stockholm | Direct | Netflix · YouTube |
| Spain | Madrid | Direct | Netflix · YouTube |
| Italy | Milan | Relay | Netflix · YouTube |
| Poland | Warsaw | Direct | YouTube |
| Ireland | Dublin | Relay | Netflix · YouTube |
Other regions
Other regions cover the Middle East, Africa and South America, mainly for reaching local sites, viewing localized content and testing region-locked services. Dubai and Tel Aviv serve as Middle East entry points, Johannesburg and Cairo cover Africa, and São Paulo and Buenos Aires cover South America. These regions are physically farther from mainland China, so pick them on demand rather than as daily routes.
| Country / Region | City | Route type | Streaming support |
|---|---|---|---|
| United Arab Emirates | Dubai | Relay | YouTube |
| Israel | Tel Aviv | Direct | Netflix · YouTube |
| Turkey | Istanbul | Direct | Netflix · YouTube |
| South Africa | Johannesburg | Direct | Netflix · YouTube |
| Egypt | Cairo | Direct | YouTube |
| Brazil | São Paulo | Relay | Netflix · YouTube |
| Argentina | Buenos Aires | Direct | YouTube |
| Chile | Santiago | Direct | Netflix · YouTube |
IEPL, relay and direct: how they differ
The route type determines how data travels from your local entry point to the exit data center — not which country the exit is in. The same city may have all three kinds of entry point, and almost all of the difference in price and experience comes from this segment of the path.
-
IEPL dedicated line
End-to-end fixed link
- How it works
- IEPL is an International Ethernet Private Line. Data enters the dedicated channel at the local entry point and travels straight to the exit data center over a fixed link, avoiding congested nodes on the public internet; the international segment comes with end-to-end bandwidth guarantees from the carrier, so heavy simultaneous use doesn't randomly thin out the bandwidth.
- Best for
- 4K streaming at peak hours, long video meetings, and AI tool sessions that need a stable long-lived connection.
- Cost
- Dedicated lines are billed by bandwidth, with the highest unit cost of the three types, so they are deployed only in core cities and popular exits.
-
Relay
Connect nearby, forward centrally
- How it works
- A relay route first connects to a nearby relay data center, which then forwards traffic to the exit. The path between the relay and the exit runs over an optimized backbone, so compared with a direct connection it avoids more congested nodes, takes a shorter path and makes traffic scheduling easier.
- Best for
- Everyday browsing, 1080p to 4K streaming, and several devices online at once.
- Cost
- Cost sits between dedicated lines and direct routes; this is the largest category in the directory and covers the widest range of cities.
-
Direct
Shortest path, simplest structure
- How it works
- A direct route connects from the local entry point straight to the exit data center with no extra forwarding in between — the shortest path and the simplest structure. How it performs depends on the state of international public links at the time, so it varies noticeably from one part of the day to another.
- Best for
- Looking something up briefly, cases where the exit region matters but stability doesn't, and times when you need a low-cost backup entry point.
- Cost
- The lowest cost, well suited as a supplementary entry point; for scenarios that demand stability, switch to a dedicated line or relay.
| Aspect | IEPL dedicated line | Relay | Direct |
|---|---|---|---|
| Path structure | Local entry → dedicated channel → exit data center | Local entry → relay data center → exit data center | Local entry → exit data center |
| Peak-hour stability | High, with guaranteed bandwidth | Medium-high, over an optimized backbone | Depends on public link conditions |
| Unit cost | Highest | Moderate | Lowest |
| Share of the directory | A small number in core cities | The most numerous, with the widest coverage | Used as a supplementary entry point |
| Best for | 4K streaming · video meetings · long AI tool sessions | Everyday browsing · several devices online at once | Brief lookups · backup routes |
Pick by use case, not by city name
The same exit performs very differently depending on what you use it for: two routes that feel identical when loading web pages may be steady on one and jittery on the other in a video meeting. Below are route suggestions for five common use cases.
-
Everyday browsing
Opening web pages, looking things up and sending email aren't sensitive to latency, so a relay route is enough. Relay routes are numerous and a region usually has several entry points, so if one gets crowded, switch to another. The client can store several routes at once; switching doesn't require re-importing the subscription and doesn't affect sessions you're already signed in to.
Recommended: Relay -
Video & streaming
With 4K streaming, what matters is bandwidth headroom and jitter, not peak speed. Prefer the IEPL dedicated lines in Hong Kong, Tokyo, Los Angeles and London; if a platform says the region doesn't match, switch to another route in the same country — the exit region stays the same but the exit address changes, and the platform's verdict often changes with it. The streaming support noted in the directory has been checked, so you can use it as a starting point.
Recommended: IEPL dedicated line -
AI Tools
AI tools need a stable long-lived connection that reconnects quickly after a drop. Relay or dedicated routes in Japan, Singapore and the US West Coast are recommended, with the client left running; switching exits frequently within one session tends to trigger a platform's risk checks, so keep the same route for the whole session. If you must switch, end the session first.
Recommended: Relay / dedicated line -
Gaming
In games, what matters is the stability of the round trip. Routes in Hong Kong, Tokyo and Seoul are physically closer and have shorter round-trip times, so prefer relay and dedicated lines; don't switch routes mid-game, since switching rebuilds the connection. If one match suddenly lags, first check whether other devices on your local network are using bandwidth, then consider switching.
Recommended: Asia-Pacific relay / dedicated line -
Work & meetings
Video meetings are sensitive to packet loss and jitter, so an IEPL dedicated line is the safest choice. Connect ten minutes before the meeting starts and confirm the status rather than discovering mid-meeting that a route is unusable; when several devices are online at once, put the meeting device on the dedicated line and let the rest use relay routes so they don't compete for bandwidth.
Recommended: IEPL dedicated line
How routes are verified
Every route in the directory goes through the same process before it's listed: confirm the exit data center matches the stated region, confirm the route type matches the actual path, then test streaming and popular sites one by one. Only routes that pass are written into the directory.
Routes are maintained over the long term; listing them once isn't the end of it. Network changes on the data center side and routing changes on the carrier side both affect how a route performs, so the directory is re-checked on a schedule: routes that are no longer stable are pulled from the common entry points, new exits are added, and the streaming support notes are updated at the same time. The route list in the user panel comes from the same source as this page, so the route types and region labels you see match.
The coverage figures of 120+ countries and 220+ routes refer to the range of available exits — not concurrent user counts, and not an uptime promise. How many routes a given city currently has is best checked against the live list in the user panel; what this page lists are the common entry points for each region, to give you a sense of the overall spread.
Choosing a route costs nothing extra: a plan records the account and the data allowance, not specific routes, so one account can switch between any available route. There's no limit on concurrent devices, and each device picks its own route without affecting the others.
The data channel between the client and the exit uses quantum encryption; sign-in credentials and subscription information also travel over an encrypted channel. This service follows a no-logs policy: it does not record what you browse or which sites you visit.
Popular regions in the directory
- Hong Kong
- United States
- Singapore
- Japan
- Netherlands
- Canada
- South Korea
- United Kingdom
- Germany
- France
- Australia
- United Arab Emirates
- Brazil
- South Africa
FAQ about routes and choosing one
If your question isn't covered here, browse the Help Center by category or open a ticket in the user panel.
Why aren't latency numbers shown on this page?
Latency changes with your local network, the time of day and route load, so a fixed value on the page means nothing and is easily misread as a promise. The directory lists only static facts that don't change over time: country, city, route type and streaming support. When you need current status, sign in to the user panel and check the route list.
How many routes can one account use at the same time?
There's no limit on concurrent devices, and each device can choose its own route without affecting the others. A single device uses one route at a time; switching takes effect immediately in the client, with no need to re-import the subscription.
Is the streaming support in the table a guarantee?
The notes reflect the result at the time of checking, meaning the route could reach that platform then. Platforms adjust their region rules, so when something stops working, switching to another route in the same country usually restores it; keeping several routes per country in the directory is partly for this reason.
Is a dedicated line always faster than a relay?
Not necessarily. The advantage of a dedicated line shows in peak-hour and long-session stability; on a single speed test the two may be close. If you're just loading web pages, a relay route feels much the same as a dedicated line; over long 4K viewing or a video meeting, the dedicated line's stability becomes more obvious.
What if I want to switch to an exit in another region?
Just switch to another route in the client — no need to re-import the subscription or buy anything again. The subscription records the account and the data allowance, not specific routes; see the plans page for details on plans and data packs.