120+ Countries / 250+ Routes

Global server locations and route directory

The route directory is organized by region, city and access method. First confirm where the target service is located, then choose IEPL, relay or direct routes based on stability, path length and your use case rather than judging by city name alone.

First Month Free View Plans
  • Unlimited devices online at once
  • 14-day no-questions-asked refunds
  • No email address required
ROUTE DIRECTORY Regional entry points
Routes you can switch between
APAC Asia-Pacific

Tokyo, Singapore, Hong Kong, Taipei, Seoul

NA North America

Los Angeles, San Jose, Seattle, New York, Vancouver, Toronto

EU Europe

London, Paris, Frankfurt, Amsterdam, Stockholm, Madrid

OTHER Other regions

Sydney, Auckland, Mumbai, Dubai, São Paulo, Johannesburg

IEPL Relay Direct
REGION INDEX

Browse server routes by region

The table below lists selected entry points to illustrate regional distribution and access types; it is not a complete route list. In practice, switch between available routes in the client within the same region. Streaming results also depend on account region, content licensing and platform policies. If the detected region is incorrect, switch to another entry point in the same area and test again.

Asia-Pacific North America Europe Other regions
APAC

Asia-Pacific

Suitable for international websites, streaming platforms and cloud services in Japan, Singapore, Hong Kong, Taiwan and South Korea. Location is only one selection factor; also consider carrier routing and current network conditions.

Country / region City Route type Streaming support
JapanTokyoIEPLSupported
JapanOsakaRelaySupported
SingaporeSingaporeIEPLSupported
Hong KongHong KongIEPLSupported
TaiwanTaipeiRelaySupported
South KoreaSeoulRelaySupported
NA

North America

Suitable for AI tools, developer platforms, business systems and media content in North America. West Coast entry points are often a useful first test for Asian networks, while Eastern locations can be tested based on the target platform’s location.

Country / region City Route type Streaming support
United StatesLos AngelesIEPLSupported
United StatesSan JoseRelaySupported
United StatesSeattleDirectSwitch and test
United StatesNew YorkRelaySupported
CanadaVancouverDirectSwitch and test
CanadaTorontoRelaySupported
EU

Europe

Use these routes for European content, cross-border work resources and regional websites. Match the target service’s country first; if no specific country is required, test London, Paris, Frankfurt or Amsterdam in sequence.

Country / region City Route type Streaming support
United KingdomLondonIEPLSupported
FranceParisRelaySupported
GermanyFrankfurtRelaySupported
NetherlandsAmsterdamDirectSwitch and test
SwedenStockholmDirectSwitch and test
SpainMadridDirectSwitch and test
OTHER

Other regions

Selected entry points across Oceania, South Asia, the Middle East, South America and Africa. These routes are best when a local exit is specifically required for a service, account or content; they are not recommended as default routes simply because the cities are less familiar.

Country / region City Route type Streaming support
AustraliaSydneyRelaySupported
New ZealandAucklandDirectSwitch and test
IndiaMumbaiRelaySupported
United Arab EmiratesDubaiDirectSwitch and test
BrazilSão PauloRelaySupported
South AfricaJohannesburgDirectSwitch and test
ROUTE TYPES

Understand the three route types

IEPL, relay and direct routes describe different access paths, not a simple quality ranking. Performance can vary by region, local carrier and time of day, even for routes of the same type. A practical approach is to narrow choices by use case first, then keep a backup entry point in the same region.

TYPE A

IEPL

For stability-sensitive tasks

IEPL routes use a more controlled transmission path across international segments, reducing unpredictable detours on public networks. For sustained transfers, long-lived connections and tasks sensitive to evening network fluctuations, start by testing this route type. It is well suited to video meetings, remote desktops, code repository sync, continuous AI tool use and high-bitrate streaming where connection continuity matters.

These routes generally cost more to provision and maintain than standard access, so there is no need to keep all traffic on one entry point. For everyday browsing, use rule-based mode and send only services requiring international routes through IEPL. This simplifies management and avoids unnecessary path changes. If a website requires a specific exit region, match the region first, then compare route types.

TYPE B

Relay routes

Balancing coverage and cost

A relay route first connects to an entry point that is closer or better suited to the current network, then uses an intermediate link to reach the target region. Its value is in shaping the international path and avoiding excessive detours from a direct local connection to a distant destination. For everyday browsing, file access, streaming and development work, relay routes often offer a balanced mix of regional coverage, connection stability and cost.

When choosing a relay, do not focus only on the final city. The entry-and-exit combination, the path from your local carrier to the access point and the target service’s region all affect performance. If one country offers multiple relay entries, test the nearer city first, then confirm that the target service recognizes the required region. A relay is not automatically better than a direct route; it organizes the path rather than guaranteeing the same result in every network environment.

TYPE C

Direct routes

A simpler path

A direct route connects from the current network straight to a server in the target region. With fewer intermediate steps and a clear structure, it makes it easier to assess the original path between the local network and the remote service. When the local carrier has a suitable connection to the target region, direct routes work well for general browsing, light file transfers and tasks requiring a specific local exit.

Direct routes depend more heavily on local network conditions. Long distances, obvious detours or busy networks can make performance change more easily than with relay or IEPL routes. Direct access is therefore useful as a regional alternative and troubleshooting path: if a relay behaves unexpectedly, switch to direct access to determine whether the issue comes from the target service, local network or intermediate path. Its cost structure is usually simpler, but that alone does not predict the final experience.

SELECTION GUIDE

Choose international routes by use case

Choose routes in this order: target region, task characteristics, route type and real-world testing. The sections below explain common use cases. The goal is not to find one permanent “universal entry point,” but to build a clear combination of primary and backup routes.

BROWSE

Everyday browsing

For international websites, research and lightweight web tasks, start with a nearby Asia-Pacific entry point. These tasks usually need less sustained throughput and depend more on requests completing successfully. Use a relay as the default and keep a direct route in the same region as a backup.

If only certain websites require international routes, use rule-based mode so local services keep their normal paths. If a page loads but the login session repeatedly expires, check whether you are switching countries or cities too often. Keeping the exit region stable during one task is usually better than constantly changing entry points.

STREAM

Streaming

For streaming, check regional matching first and route type second. Account libraries, licensing regions and platform policies all affect the result, so “Supported” in the table means the entry point can be used for the scenario, not that every account will see identical content.

Before playback, choose the country or region where the content is available, then open the platform and verify its library. If the detected region is unexpected, exit the app, switch to another route in the same area and open it again. For longer sessions, test an IEPL or relay route first and avoid changing the exit point repeatedly during playback.

AI

AI Tools

AI chat, code completion and command-line tools often depend on persistent connections. Brief path changes can interrupt responses, reload context or cause requests to fail, so choose a stable entry point in a region where the target service is available. Test North American and Asia-Pacific routes according to the service’s regional availability.

Using different proxy settings in the browser, editor and terminal can make websites work while extensions do not. First check system proxy settings and client rules together, then keep one primary route for continuous tasks. When submitting longer content or maintaining a development session, test an IEPL route first.

GAME

Gaming

Choose a game route based on the actual server region, not the account’s registration region. Confirm the game server area first, then start with a nearby entry point. Updates, store access and live matches may use different service addresses, so in rule-based mode make sure the relevant domains use routes in the same region.

Frequent exit-region changes can retrigger login sessions and server-region checks. Switch before entering the game and keep the route unchanged during the match. For connection-sensitive tasks, compare IEPL and relay routes in the same region and choose the one that best suits the local network.

WORK

Remote work and development

Business systems, remote desktops, video meetings, code repositories and cloud consoles all require continuous connections and a relatively stable exit region. Confirm the location of the enterprise system or cloud service first, then test an IEPL or relay route in that region. If the system records login locations, avoid switching repeatedly between countries during work.

Remote work also requires separating browser traffic from developer-tool traffic. Browser access does not guarantee that the terminal, package manager and editor extensions use the same route. If authentication succeeds but downloads fail, check application proxy settings, system proxy settings and rule matching one by one. Keep a backup entry in the same region after setup so you can switch during maintenance without changing the entire work environment.

CHECKLIST

Route selection checklist

Checking the region, task and access method separately is faster than switching randomly between routes.

  1. Confirm the target region first

    Use the region where the target website, content library, game server, business system or cloud service is located. Account registration location and server location may differ, so do not rely on interface language alone.

  2. Assess the task

    Regular web pages prioritize successful requests; streaming prioritizes regional detection and sustained transfer; AI tools and remote work prioritize persistent connections; gaming requires server-region matching and connection stability.

  3. Compare route types in the same region

    Test IEPL or relay routes first, then use direct access as an alternative and troubleshooting path. Results are meaningful only when comparing the same region and device under similar network conditions.

  4. Set a primary and backup entry

    Once a route works, record one primary route and one backup in the same region. Keep the region stable for everyday use and switch in order when problems occur. Avoid changing the client, mode and region at the same time, or the cause will be difficult to isolate.

ROUTE NOTES

Common questions about route selection

Is the closest city always the best choice?

Not necessarily. Geographic distance is only one filter; local carrier routing, the target service’s region and the access type matter too. Start with a nearby city, then compare IEPL, relay and direct routes in the same region.

Why keep a backup route in the same country?

Different entries in the same country may use different cities and access paths. A regional backup lets you switch without changing the account region or content area, while helping determine whether the issue comes from one path or the target service.

What should I do when streaming shows the wrong region?

First confirm that the route country matches the target content region. Then exit the streaming app, switch to another route in the same region and reopen it. Account region, content rights and platform policies also affect the result, so do not judge by the route name alone.

What if an entry listed on the page is missing from the client?

Refresh the subscription in the user panel first, then update the client configuration. The page shows examples of common regions and route types; actual options depend on the subscription content available after sign-in.

Can different devices use different regions?

Yes. Choose routes for each device according to its purpose; 35VPN supports unlimited devices online at once. Keep work devices on the work region, choose the content region for streaming devices and use a nearby entry for everyday browsing.

35VPN

Use global routes by region

Coverage across 120+ countries and 250+ routes, with unlimited devices online at once. Sign-up requires only a username and password; no email address is required.

First Month Free