RN Relay Regional directory / route selection

Global Routes
Regions and Types

Start with the region required by your destination, then compare the routes to the exit. VPNRN covers 100+ countries / 150+ routes, with international routes for different needs.

This page is a static route-selection reference, not a live connection status. Current available routes, exits and types are shown in the client after login.

Try It Free View Plans

Browse Routes by Region

The table lists example regions and cities; it is not a complete list of coverage. A country or region indicates the exit location and does not grant access to every service there.

How to assess streaming support: A network route to a streaming service does not guarantee access to a particular library. The table uses “Verify by exit”; availability depends on the service’s supported regions, your account subscription and actual playback results.

Regional route examples; check the client for current availability
Country / Region City Route Type Streaming Support
Asia-Pacific
JapanTokyoIEPLVerify by exit
SingaporeSingaporeIEPLVerify by exit
Hong Kong, ChinaHong KongDirectVerify by exit
JapanOsakaRelayVerify by exit
South KoreaSeoulRelayVerify by exit
AustraliaSydneyRelayVerify by exit
New ZealandAucklandRelayVerify by exit
MalaysiaKuala LumpurRelayVerify by exit
North America
United StatesLos AngelesRelayVerify by exit
United StatesSeattleRelayVerify by exit
United StatesNew YorkRelayVerify by exit
CanadaVancouverRelayVerify by exit
CanadaTorontoRelayVerify by exit
Europe
GermanyFrankfurtRelayVerify by exit
United KingdomLondonRelayVerify by exit
FranceParisRelayVerify by exit
NetherlandsAmsterdamRelayVerify by exit
SwitzerlandZurichRelayVerify by exit
Other Regions
BrazilSão PauloRelayVerify by exit
South AfricaJohannesburgRelayVerify by exit
United Arab EmiratesDubaiRelayVerify by exit
ChileSantiagoRelayVerify by exit

Separate the exit location from the connection route

The city in a route name usually identifies the exit location, while the route type describes how traffic reaches that exit. They serve different purposes: the exit location affects the region a destination website sees, while the route type affects how traffic travels over your current network. Choosing a Tokyo exit does not mean traffic travels directly from your location to Tokyo; choosing a relay route does not mean the exit is in the same region as the relay entry point.

If a website requires a specific region, check its regional rules first, then look for the corresponding exit in the client. For everyday access to international websites, you can start by comparing commonly used Asia-Pacific locations. Geographic distance is only one factor: carrier peering, access method and the destination’s location can also affect performance, so map distance alone cannot determine which route is best.

IEPL, Relay and Direct Routes: What’s the Difference?

Route types describe how connections are organized, not how fast they are. Start with your use case, then compare performance on your current network.

IEPL

Dedicated transport path

IEPL usually refers to an international Ethernet private line, using dedicated transport resources to connect network endpoints in different regions. Compared with international traffic that relies entirely on the public internet, this arrangement can reduce the impact of some public routing changes. However, the local network between your device and the entry point, as well as the connection from the exit to the destination service, still affects the overall experience. “Dedicated line” does not mean every segment uses the same type of resource.

A good option for extended AI web sessions, online meetings or longer work sessions. If performance changes noticeably in the evening, compare IEPL with other route types in the same exit region. Check whether pages load, sessions stay connected and file transfers remain consistent. Keep your local network and destination the same during testing so changes in Wi-Fi or another access network are not mistaken for route differences.

Dedicated transport resources typically cost more to procure and maintain, so the IEPL label describes how resources are organized; it does not mean every plan carries an extra charge. This page does not list surcharges by route type. Confirm availability and plan coverage in the user panel, and see the pricing page for plan prices.

Relay

Separate entry and exit points

A relay route sends the connection to an entry point first, then forwards it along another path to an exit in the destination region. The entry point handles access; the exit communicates with the destination website. Choosing the right entry can improve the route when a direct connection to a distant exit performs poorly on some networks. But an extra hop also means the entry, transit segment and exit need to work well together. “Relay” alone does not tell you whether a connection will be faster or slower.

Relay routes can suit users who need a wider choice of regions, access multiple international websites, or have poor direct performance to a particular distant region. To compare relay routes, keep the exit region fixed and try the available paths. Switching between continents at random changes regional detection, distance to the service and content delivery nodes, making it harder to pinpoint what affects performance.

Relay costs depend on entry resources, cross-region transport and exit maintenance. Route setups vary widely, so it is rarely accurate to summarize them all as “cheaper than IEPL.” What matters most is finding an option within your plan’s available routes that can reliably handle your tasks, rather than guessing resource costs from the route name.

Direct

Connect directly to a remote node

Direct usually means the client connects to the remote node without passing through a relay entry configured by the subscription service. The route may look more direct, but actual traffic still depends on your local carrier and international peering. One fewer relay does not necessarily mean a shorter physical route or less time to reach the destination website.

Direct routes can work well when your current network has good connectivity to the region, and they can also serve as a useful comparison. If a relay entry is temporarily unsuitable for your network, trying a direct route in the same region can help determine whether the issue is with the entry segment. If no route works, check your device’s network, client connection status and subscription updates before repeatedly switching cities.

Direct routes typically use fewer relay resources, but still involve exit network and maintenance costs. Direct does not mean low quality, nor does it inherently use less data. Route type does not change plan data rules: monthly subscription data resets on the activation date each month; data add-ons remain available until used and never expire.

Choose Routes by Use Case

Instead of asking “Which city should I connect to?”, start with “What do I need to do?” It usually makes it easier to find a route you can use consistently.

Everyday Browsing

Start with a familiar region

For reading international websites, researching or viewing images, start with a region that works with your usual services, then check that pages load fully. If text appears but images or attachments keep loading, the issue may involve connections to separate resource domains; it does not necessarily mean the entire exit is unavailable. Check your routing rules to make sure the page and its static resources are not taking different paths.

Once you find a route that works for everyday use, keep a backup in the same region. If one website has a problem, try another page or reopen it in your browser before switching routes. This helps distinguish issues with the site itself, browser cache or fluctuations in your local network.

Streaming

Check the content’s region first

For streaming, first check which region offers the content, then choose the corresponding exit. Opening the service homepage only confirms that the basic access route works. Playback also depends on regional licensing, your account subscription, device authorization and how the exit is identified. “Verify by exit” in the route table is not a playback guarantee and does not mean the service offers the same library in that region.

Test the specific content you want to watch, and check that playback continues and subtitles and audio tracks are correct. Before changing regions, stop playback and reopen the target page to avoid confusion from an old session using a different exit. For more scenarios, see Streaming Support.

AI Tools

Keep the exit region consistent

When using ChatGPT, Claude or Gemini, first check the regions and account requirements supported by the service. A successful connection and permission to use an account are separate issues. If you see a regional notice or sign-in verification, read the service’s instructions instead of assuming every prompt indicates a network problem. Avoid repeatedly changing exits to see what happens.

Once you identify a supported region, keep your session there where possible. Configure routing in the client as needed so the AI website and its related requests use a consistent path. If long sessions tend to drop, compare IEPL and relay routes within the same region. See AI Tools Access Guide for setup details.

Gaming

Check the game server region

A game’s store, login system and match servers may be in different locations, so a smooth-loading website does not guarantee the same experience in a match. Check your game region first, then confirm that the client supports the connection method and data rules the game requires. These international route details do not guarantee compatibility with every game, region or anti-cheat system.

Before playing, test login and connectivity in an environment permitted by the game. Keep the route stable during a match and avoid frequent node changes. If only the game is affected while websites work normally, note the game, region, affected step and client mode, then check through a support ticket in the user panel rather than submitting only a city name.

Work

Prioritize stable sessions and access permissions

Remote work involves company access policies, collaboration platform rules and meeting connectivity. Some work systems identify exit regions or restrict connection sources, so confirm that your organization allows this type of connection before choosing a route. If your company has a designated network solution, follow its requirements; a standard international route is not a substitute for company authorization.

Online meetings, document collaboration and file uploads benefit from a consistent connection path. Before starting work, test sign-in, syncing and uploads with the tools you actually use; avoid changing regions during important sessions. VPNRN supports Windows / macOS / iOS / Android / Linux with no device limit, but check the client connection and exit on each device separately.

Verify and Maintain Your Connection

Check your local connection first, then the exit, and finally the task you need to complete. Change one factor at a time to make results easier to interpret.

Update your subscription, then check the route name

The regional directory helps you understand the available options; the subscription list in the client is where you select routes. After maintenance or configuration changes, an old list may no longer reflect current availability. Sign in to the user panel to get your subscription, update it in the client, then check the route name, region and type. Do not post your subscription URL in public forums. For troubleshooting, share interface details without credentials.

Get the client and subscription from the user panel. After signing in, you can download clients for platforms other than iOS; access to the iOS download is subject to an active plan. For initial setup, follow the Quick Start Guide. For the full process covering routing rules, routine maintenance and importing on multiple devices, see the Complete Guide.

Check the exit before opening your destination

Once the client shows as connected, use the site’s IP Check to verify the current exit information. The result reflects only the path used by the check request; with split tunneling enabled, other apps may use different routes. Open the website or app you actually need and check sign-in, content loading and the task itself. Do not treat a location shown on the check page as the end of verification.

Exit-region identification can vary with database update schedules. If the check result differs from the destination service’s assessment, follow the service’s access rules and note the circumstances. A region name does not grant service authorization, and a network connection does not change the content permissions on your account.

Keep useful comparison details when troubleshooting

First check whether your local network can access familiar websites, then check the client’s subscription and connection status. If only a specific website has issues, compare with a backup route in the same region. If all destinations are affected, check the client mode and device network. Record the region, route type, destination service and error message; this is more useful for troubleshooting than a vague report that “the node doesn’t work.”

Assess a route by how well it handles your everyday tasks, not by an isolated speed-test screenshot. Keep a regular route and a backup in the same region, update your subscription regularly, and provide the details above when contacting support. Plans include a 30-day money-back guarantee; see the Terms of Use for details. For account and connection questions, visit the Help Center.