ROUTE INDEX / OUTPOST 42

Coverage index loaded

Server locations and route regions

90+ countries / 200+ routes. This page lists cities, route types, and streaming guidance by region without showing temporary metrics that can change with network conditions.

View Route Table View Plans

Unlimited devices
14-day money-back guarantee
No email address required

GLOBAL ROUTE DIRECTORY INDEX

COVERAGE 90+ countries 200+ routes

REGION / APAC Asia-Pacific

Nearby entry points including Tokyo, Hong Kong, and Singapore.

REGION / NA North America

Major cities across the United States, Canada, and Mexico.

REGION / EU Europe

Connections across Germany, the United Kingdom, France, the Netherlands, Switzerland, and more.

REGION / OTHER Other regions

Additional entry points across South America, the Middle East, Africa, and Oceania.

COORDINATES / STATIC DIRECTORY

Browse server routes by region

The table below is a sample of the coverage index. It illustrates common entry points and routing methods rather than expanding all 200+ routes. A city indicates the egress region; one region may offer multiple route types, and the current list in the client is based on your account configuration.

Country / Region	City	Route type	Streaming support
Asia-Pacific
Japan	Tokyo	IEPL Dedicated	Supported
Japan	Osaka	Relayed	Supported
Hong Kong	Hong Kong	IEPL Dedicated	Supported
Singapore	Singapore	Relayed	Supported
South Korea	Seoul	Direct	Supported on some routes
Taiwan	Taipei	Relayed	Supported
Australia	Sydney	Direct	Supported on some routes
India	Mumbai	Direct	Supported on some routes
North America
United States	Los Angeles	IEPL Dedicated	Supported
United States	Seattle	Relayed	Supported
United States	New York	Direct	Supported
Canada	Toronto	Relayed	Supported
Canada	Vancouver	Direct	Supported on some routes
Mexico	Mexico City	Direct	Supported on some routes
Europe
Germany	Frankfurt	IEPL Dedicated	Supported
United Kingdom	London	Relayed	Supported
France	Paris	Direct	Supported
Netherlands	Amsterdam	Relayed	Supported
Switzerland	Zurich	Direct	Supported on some routes
Italy	Milan	Direct	Supported on some routes
Other regions
Brazil	São Paulo	Relayed	Supported
Argentina	Buenos Aires	Direct	Supported on some routes
United Arab Emirates	Dubai	Relayed	Supported
South Africa	Johannesburg	Direct	Supported on some routes
New Zealand	Auckland	Direct	Supported on some routes

Region does not determine speed. A shorter distance often means a shorter transmission path, but the local carrier, access time, routing decisions, and the target service’s region can all change the actual experience. Map distance alone is not enough to judge performance.

Route type is not a fixed tier. IEPL dedicated, relayed, and direct routes describe different ways of organizing the connection. A direct route may perform smoothly on the right local network, while a dedicated route can still fluctuate because of the target service itself.

PATH CLASSIFICATION

Understand the three route types

Type labels explain how data travels from your local connection to the target region. They help narrow the choices but do not replace real-world testing. Consider the target service, usage time, and local network together.

PATH / IEPL Priority route

IEPL Dedicated

An IEPL dedicated route places the cross-border segment in a relatively independent network channel, with less reliance on the public internet. Its main advantages are a more direct link structure and more controllable routing, making it suitable for sustained transfers, long meetings, remote desktops, and large file synchronization.

These routes generally cost more to build and maintain, so they are better suited to key regions and frequently used entry points. A dedicated route is not guaranteed to be the fastest in every environment. The target service’s egress location, local access quality, and endpoint conditions still affect the result.

Suitable for long work sessions and sustained data transfers
Useful when the local network fluctuates noticeably during busy periods
Prioritize the region where the target service is located

PATH / RELAY

Relayed Route

A relayed route first sends the connection to a suitable access point, then uses an intermediate node to reach the target region. Its main purpose is to avoid unstable cross-border paths on the local network and reorganize the route based on the connection conditions between the entry and exit points.

Relaying usually falls between dedicated and direct routes in cost and routing complexity. It suits everyday browsing, streaming, AI Tools, and routine work. Because an additional hop is involved, the right choice depends more on the entry point, so different routes in the same city may be worth trying.

Suitable for tasks that balance regional access and connection stability
Useful when the target region is far away or the local direct path is unsuitable
Reconnect the app after switching to avoid reusing the old session

PATH / DIRECT

Direct Route

A direct route connects the local network straight to a server in the target region without an additional intermediate routing node. Its simple path is suitable when the local carrier already has a good connection to that region and provides a useful baseline for identifying the source of a problem.

Its cost structure is generally lower and its coverage is easier to expand, but performance depends more on the local network and public routing. If a direct route is unstable in the current environment, try a relayed or IEPL dedicated route in the same region. If it works well, there is no need to switch based on the label alone.

Suitable for general web access and lightweight app connections
Useful as a baseline for comparing route types in the same region
Keep using it when the local network path is performing well

USE CASE ROUTING

Choose a route by use case

Identify where the target service is hosted first, then choose the route type. Choosing solely by city name usually adds unnecessary cross-region traffic.

CASE / BROWSE

Everyday browsing

For international websites, research, or lightweight web tasks, start with a geographically nearby region. Asia-Pacific entry points are often convenient for Chinese-speaking users. If the site is clearly hosted in North America or Europe, choose that region directly to reduce additional server-side routing.

Everyday browsing does not require a fixed route type. Start with a nearby direct or relayed route and keep it when pages and downloads remain stable. Frequent switching makes sites repeatedly reassess your region and may trigger another login or content refresh.

CASE / STREAM

Streaming

Streaming depends first on the region where the content is available. Confirm the account region and target catalog, then choose a corresponding entry marked as supporting streaming in the table. After connecting, close the existing playback page and reopen the app so the platform reloads the catalog based on the new egress region.

If quality drops during playback, do not assume the route has failed immediately. Pause high-traffic tasks on other devices and check whether the player is still using an old cache. If the catalog is correct but transmission is unstable, switch within the same region from direct to relayed or IEPL dedicated.

CASE / AI

AI Tools

AI Tools often involve web sessions, API requests, file uploads, and continuous output at the same time. Prioritize session continuity rather than only the speed of the initial page load. If the target service is in North America, start with a US West Coast entry point, then change route types according to the local network.

If the page opens but the response stops midway, check whether the browser retained an old connection, whether the uploaded file is too large, and whether the local network changed. Keeping one region throughout a session usually makes account-region consistency easier than switching repeatedly between countries.

CASE / GAME

Gaming

Match the game server’s region first and minimize cross-region distance where possible. Entry points in Japan, Hong Kong, Singapore, and South Korea suit corresponding Asia-Pacific servers; for North American or European servers, choose a city in the same region. The launcher, login service, and actual match server may be in different regions.

If login works but the experience changes after entering a match, check whether the game automatically assigned another region. Before switching routes, leave the current match and launcher, then reconnect to the target region. Do not change the egress during a match, as the session may need to be re-established.

CASE / WORK

Remote work

Use the region of your company system, code repository, document platform, or meeting service as the reference point. Long meetings, remote desktops, and continuous synchronization are better candidates for testing IEPL dedicated or relayed routes first; ordinary email, web admin, and short file transfers can start with a nearby direct route.

Keep the egress region stable during work. Some enterprise systems may ask you to confirm your login again after a regional change. If switching is necessary, save documents and finish active uploads, disconnect the current route, select the new region, and re-enter your work apps.

COVERAGE LEGEND

How to read regional coverage

90+ countries / 200+ routes represents the total number of available regions and routes. You do not need to test them one by one: narrow the range by target region, then compare different links within that region.

Singapore United States Hong Kong Japan Switzerland Canada Germany United Kingdom France Australia South Korea Netherlands

LEGEND / COUNTRY

Countries and cities

Use the country to match the content region, account region, or location of a business system; use the city to assess the egress location more precisely. When a country has multiple cities, start with the entry point closer to the target service rather than automatically choosing the city nearest to you.

LEGEND / ROUTE

Multiple routes in one region

When a region offers direct, relayed, or IEPL dedicated routes, you can reach a similar egress area through different link structures. If performance fluctuates, change the type within the same region first. This preserves the target region while helping determine whether the issue comes from the transmission path.

LEGEND / CLIENT

Client list

Windows, macOS, iOS, Android, and Linux clients are obtained from the user panel. After signing in, load your subscription to see the routes currently available to your account. The marketing page does not provide static installers or display a live subscription URL.

LEGEND / ACCOUNT

Account and devices

No email address is required to create an account; set a username and password. The service supports unlimited devices, but simultaneous transfers across multiple devices share the traffic allowance of the plan. Check whether other devices are syncing files or streaming when choosing a route.

ROUTE CHECK PROCEDURE

How to decide when switching routes

Consistent route selection depends on a repeatable process. Change one condition at a time so you can distinguish issues caused by region, route type, app cache, or the local network.

Identify the target region first

Confirm the primary service region for the website, streaming catalog, AI tool, game server, or company system. If the target is clearly in the United States, start by comparing US cities; do not switch randomly across several countries at once.
Close the old session

Before disconnecting the current route, save edited content and finish uploads. Close the target app or browser tab so it cannot keep using the old connection. Then disconnect the route in the client and choose a new region and type.
Compare routes within the same region first

Keep the target region unchanged and switch only among direct, relayed, and IEPL dedicated routes. This shows whether the link structure affects task completion. If none perform well, consider a nearby city or another country in the same region.
Test with a real task

For browsing, open a commonly used page; for streaming, check the catalog and continuous playback; for work, test meetings, documents, and remote systems. Do not treat the first load of one page as representative of every task or rely on decorative, momentary figures.
Keep the option that works

Once you find a route that suits the current network and target service, keep using it for a while. If conditions change later, rule out local Wi-Fi, system sleep, app cache, and transfers on other devices before switching.

ACCOUNT ACCESS

Load the route list from your account

Client downloads and subscription access are available in the user panel. Supports Windows / macOS / iOS / Android / Linux and unlimited devices. No email address is required; a username and password are sufficient.

Get the Client View Setup Guides