120+ countries · 170+ routes

Global server routes

Choose a server by region, route type, and task. The route table shows static coverage information rather than using momentary metrics to represent long-term connection quality.

  • Quantum encryption
  • Unlimited simultaneous devices
  • 14-day no-questions-asked refund
  • No email address required
RELAY DIRECTORY Regional index
APAC APAC Hong Kong · Tokyo · Singapore
NA North America Los Angeles · San Jose · Toronto
EU Europe London · Frankfurt · Paris
OTHER Other regions Dubai · São Paulo · Sydney
IEPL Relay Direct
ROUTE INDEX

Browse routes by region

Use the table to check common regions, cities, and available route types. It is not a complete server list; the actual available endpoints are determined by the subscription obtained after signing in. The streaming column means that the region has routes intended for that use. It does not guarantee the same result for every platform, account region, or content library.

Country / region City Route type Streaming support
APAC
Hong Kong, China Hong Kong IEPL Supported
Japan Tokyo IEPL Supported
Japan Osaka Relay Supported
Singapore Singapore IEPL Supported
Taiwan, China Taipei Relay Supported
South Korea Seoul Relay Supported
Australia Sydney Direct Supported
Malaysia Kuala Lumpur Direct Test by platform
Thailand Bangkok Direct Test by platform
India Mumbai Relay Test by platform
North America
United States Los Angeles IEPL Supported
United States San Jose Relay Supported
United States New York Direct Supported
Canada Vancouver Relay Supported
Canada Toronto Direct Supported
Mexico Mexico City Direct Test by platform
Europe
United Kingdom London IEPL Supported
Germany Frankfurt Relay Supported
France Paris Relay Supported
Netherlands Amsterdam Direct Supported
Italy Milan Direct Test by platform
Spain Madrid Direct Test by platform
Switzerland Zurich Relay Test by platform
Finland Helsinki Direct Test by platform
Other regions
United Arab Emirates Dubai Relay Test by platform
Turkey Istanbul Direct Test by platform
South Africa Johannesburg Direct Test by platform
Brazil São Paulo Relay Supported
Argentina Buenos Aires Direct Test by platform
New Zealand Auckland Direct Supported
ROUTE TYPES

How the three route types work

Route names describe how data is organized as it enters an international link from the local network. There is no universal ranking outside a specific use case: stable tasks usually benefit from controlled paths, short browsing sessions from regional matching, and long-distance access from checking where the target service is actually deployed.

TYPE A IEPL

A more controlled international path

IEPL routes carry cross-border traffic over more tightly controlled international links, reducing repeated path changes across the public internet. The focus is not a one-time peak speed test, but making paths for long-lived connections, sustained transfers, and busy periods more consistent.

These routes suit video calls, remote development, continuous AI conversations, code repository sync, and high-bitrate streaming. Because link resources and routing costs are typically higher, reserve them for interruption-sensitive tasks rather than sending every connection through the same endpoint.

TYPE B Relay

Connect through an optimized entry point first

Relay routes send the connection to a more suitable entry point first, which then connects to the target region. This adds a routing layer, but can avoid an unsuitable direct path between the local exit and the remote network. For balancing coverage, cost, and stability, relay routes are often the most versatile option.

Everyday websites, file downloads, social platforms, and most streaming tasks can start with a relay route. If a route loads pages slowly, leaves images incomplete, or repeatedly rebuilds long connections on your current network, try another relay entry in the same region instead of switching straight to a more distant country.

TYPE C Direct

Connect directly to the target region

Direct routes travel from the local network to the target region without an extra relay layer. Their simpler structure suits strong local exits, nearby destinations, or tasks that do not require a persistent connection. They also make it easier to assess the baseline connection quality between your network and a given region.

Direct routes depend more on the local carrier network and public international paths, so the same city may perform differently across networks. They are usually a lightweight choice for everyday browsing and a useful comparison for troubleshooting: when direct and relay routes differ noticeably, the issue is often the path rather than the client settings.

USE CASE

Choose servers by task

Server selection is not about finding one permanently “best server.” Translate the task into a region, path, and connection profile. Identify where the target service is located, decide whether interruptions matter, and only then compare routes in the same region.

The following approach does not depend on a single short-term test and can be reused on Windows, macOS, iOS, Android, and Linux. After switching, let the task run for a while, then judge it by page response, video buffering, session continuity, and file transfer behavior.

BROWSE

Everyday browsing: start with a nearby region

For international websites, research, image viewing, and email, start with a geographically nearby region and a simple path. Users in APAC can usually begin with Hong Kong, Tokyo, or Singapore. If both relay and direct routes are available in the same region, try relay for general access and use direct as a comparison.

Browsing depends more on first-screen response and the continuous loading of many small resources. If text loads but images, scripts, or attachments keep waiting, switch to another endpoint in the same region and check whether the client is using a proxy mode suited to the task. There is no need to start by switching to a distant region.

MEDIA

Streaming: match the region before the distance

Streaming availability commonly depends on account region, content rights, and exit location. First identify the content region you need, then choose a route in that region marked “Supported.” Once playback starts, check whether quality stays stable, seeking recovers quickly, and continuous playback avoids reconnecting.

If a platform homepage opens but specific content will not play, try another route in the same region and restart the app to refresh its connection state. Avoid switching regions repeatedly, since account caches and local app state may temporarily retain the previous region. “Test by platform” means you should verify the result with the specific content service.

AI

AI tools: prioritize session continuity

Web chat, code completion, command-line assistants, and model APIs all depend on persistent connections. Brief interruptions may stop a response, reload context, fail a completion, or cause a terminal task to retry. For these tasks, prioritize an IEPL route or a stable relay entry and keep the exit region consistent where possible.

When using a browser, editor, and terminal together, place them under the same client rules to reduce exit differences caused by separate route choices. If only one application has connection issues, first check whether it follows the system proxy, then consider changing the route rather than attributing every problem to the server.

GAME

Gaming: follow the game server region

Choose a game route based on the actual server region, not the account language or store region. For Asian servers, test Tokyo, Singapore, Hong Kong, or Seoul first; for North American servers, start on the West Coast; for European servers, compare Frankfurt, London, or Paris. Login, matchmaking, and voice may use different network services, so enter a full match before judging the result.

If login works but matchmaking fails, first confirm that the client rules cover the game process and its launcher. If voice alone is affected, compare relay and direct endpoints in the same city. Game updates and live matches have different requirements: a general route may work for downloads, while matches call for fewer unnecessary switches.

WORK

Work: keep the exit aligned with your business region

Video calls, cloud documents, remote desktops, code repositories, and business dashboards prioritize connection continuity and a consistent exit. If your team’s services are concentrated in one region, prefer an IEPL or relay route there and keep it unchanged during work to avoid repeated session verification caused by changing exits.

Before syncing large files, use a small file to confirm that both upload and download work. Before a meeting, open audio, camera, and screen sharing in advance to check them. With many work devices, VPNRH supports unlimited simultaneous devices, so computers and mobile devices can use the same subscription; each device should still have its rules and current route checked separately.

SELECTION METHOD

A repeatable server-selection workflow

Route performance depends on the local network, access time, target service, and client settings. A consistent decision process is more reliable than remembering one server name.

  1. TARGET

    Identify the target region first

    Start with the target website, game server, team system, or content region and choose the corresponding country or a nearby region. If the service is deployed across several regions, begin with the closest endpoint. A regional mismatch can produce the wrong content or login state even when the connection itself is smooth.

  2. PATH

    Choose the route type next

    For long-lived connections, remote work, and sustained transfers, consider IEPL first; for general websites and everyday apps, start with relay; when the local exit is strong or the task is lightweight, test direct. Route type addresses path organization, so the name alone cannot predict the entire experience.

  3. CHECK

    Validate with a real task

    Open the actual website, video, editor, meeting, or game you need instead of stopping at a successful connection message. For browsing, check several pages loading in sequence; for streaming, check playback and seek recovery; for AI tools, check continuous chat and completion; for work, check uploads, downloads, and session persistence.

  4. FALLBACK

    Keep a backup endpoint in the same region

    Prepare another route type in the same region for common tasks. If the primary route has issues, switch within that region first to minimize changes to account region, content area, and business endpoints. If several routes in the same region fail, check the subscription update, client proxy mode, and local network.

Configuration notes

What matters beyond coverage numbers

VPNRH offers 120+ countries / 170+ routes. Coverage shows the breadth of available regions, but the right choice still depends on the task. Multiple paths in a frequently used region, easy switching within that region, and correct client control of the target app often matter more than simply adding distant endpoints.

The route list may change with network maintenance and regional resource adjustments. Update the subscription after signing in to obtain the routes currently available to your account. If the client continues to show old names or misses new endpoints, update the subscription first, then restart the client to confirm the list instead of editing the subscription manually.

No email address is required to create an account; a username and password are enough. Plans support Windows, macOS, iOS, Android, and Linux with unlimited simultaneous devices. Payment methods include Alipay, WeChat Pay, and USDT, with a 14-day no-questions-asked refund.

RELAY CHECKLIST
  • REGIONTarget region matched
  • TYPERoute type fits the task
  • CLIENTTarget app is covered
  • SESSIONValidate with the real task
  • BACKUPKeep a same-region backup
Windows · macOS · iOS · Android · Linux
NEXT STEP

View plans and subscription rules

Monthly subscriptions reset each month on the activation date. There are also traffic bundles that remain available until used and never expire. Compare your traffic needs first, then open the user panel to get the client and subscription.