VPNLong · International Server Directory

Global routes,
Regions & Types

110+ countries / 150+ routes. Choose an exit region, review the route, then test the service you need.

Unlimited simultaneous connections No logs 7-day money-back guarantee

The table below is a selection from the route directory, not a complete server list or a live status report. Available routes and their names are shown in the user dashboard and the latest client list. Cities indicate exit locations, not entry points.

Open the user dashboard Subscription setup guide →

REGIONAL DIRECTORY

Find an exit by region

Countries and cities show where an exit is located; route types describe how traffic is routed. Assess them separately: one region can have multiple route types, and the same type can serve different exit locations. A city name alone cannot tell you whether a particular website will work.

Asia-Pacific · Selected exit locations
Country / RegionCityRoute typeStreaming support
Hong Kong, ChinaHong KongIEPLVerify with real-world testing
SingaporeSingaporeRelayedVerify with real-world testing
JapanTokyoIEPLVerify with real-world testing
JapanOsakaRelayedVerify with real-world testing
South KoreaSeoulRelayedVerify with real-world testing
AustraliaSydneyDirectVerify with real-world testing
North America · Selected exit locations
Country / RegionCityRoute typeStreaming support
United StatesLos AngelesDirectVerify with real-world testing
United StatesSeattleRelayedVerify with real-world testing
United StatesNew YorkRelayedVerify with real-world testing
CanadaVancouverRelayedVerify with real-world testing
CanadaTorontoDirectVerify with real-world testing
Europe · Selected exit locations
Country / RegionCityRoute typeStreaming support
SwitzerlandZurichRelayedVerify with real-world testing
United KingdomLondonDirectVerify with real-world testing
GermanyFrankfurtRelayedVerify with real-world testing
FranceParisDirectVerify with real-world testing
NetherlandsAmsterdamRelayedVerify with real-world testing
SwedenStockholmDirectVerify with real-world testing
Other regions · Selected exit locations
Country / RegionCityRoute typeStreaming support
BrazilSão PauloRelayedVerify with real-world testing
ChileSantiagoRelayedVerify with real-world testing
South AfricaJohannesburgRelayedVerify with real-world testing
United Arab EmiratesDubaiRelayedVerify with real-world testing
How to read the streaming column

An available exit does not guarantee access to a particular content library. Platforms may consider your account region, payment region, exit IP, and content licensing; results can vary by platform. The table uses a consistent “verify with real-world testing” note. For details, see streaming access guidance.

PATH CLASSIFICATION

IEPL, relayed & direct routes

Route types describe how traffic is carried, not how fast a connection will be. A complete connection still depends on your local network, access network, cross-border links, and destination website. Congestion at any point can affect performance. Route labels do not replace testing during your actual usage hours.

IEPL

IEPL

How cross-border traffic is routed

IEPL generally refers to an international Ethernet private line. For subscription services, the label indicates that a cross-border segment uses private-line capacity; it does not mean every part of the connection is covered. The path from your device to the entry point, your local Wi-Fi, and the connection from the exit to the destination website all affect results. IEPL is not an end-to-end performance guarantee.

It can be a candidate for extended work sessions, meetings, or ongoing access to services abroad, particularly when standard public-internet routes are inconsistent. First confirm the exit region meets your needs, then check that sign-ins, file transfers, and continued access remain stable. The route name alone should not be the deciding factor.

Private-line capacity generally involves higher network and maintenance costs, but this page does not use that to infer plan price differences, dedicated resources, or priority. Check your account for currently available routes. Choosing a higher data allowance does not automatically mean you receive different route guarantees.

RELAY

Relayed

Reach an overseas exit through an entry point

A relayed route sends your connection to an entry point first, then onward to an exit. This changes how traffic is routed and may help when a direct route to a particular overseas exit is a poor fit. Relayed connections are not inherently faster than direct ones; consider the entry point, onward link, and exit status together.

Relayed routes are a regular option for everyday browsing, research, and accessing apps across regions. If multiple relayed routes are available for the same exit region, compare them using the same local network and destination website. Check whether pages load fully and interactions remain responsive rather than relying on a single connection notice in the client.

Relayed routes require maintaining an entry point and onward links. Costs depend on the route combination, capacity, and exit resources; an extra entry point alone does not indicate whether a route is more or less expensive. Relaying is a routing choice, not a statement about resource sharing or a destination service’s licensing.

DIRECT

Direct

Connect directly to a specified overseas entry point

Direct usually means the client connects to the specified overseas entry point over the public internet, without an additional relay entry configured by the service. The route is more direct in structure, but its actual path depends on access providers and public-internet routing. A nearby location does not necessarily mean a shorter network path.

When your local network has a good public-internet connection to the destination region, direct can be a practical everyday option and a useful comparison against relayed routes during troubleshooting. If a direct route in the same region is unstable while a relayed one works, keep the route that gets the job done. There is no need to repeatedly change a client configuration that has already been verified.

Direct routes have fewer additional relay steps, but resource costs still depend on overseas access, exit networks, and maintenance. Direct does not mean a dedicated exit, nor does it change how a destination website determines your region. Choose based on your use case and observed performance, not a ranking of route labels.

USE-CASE NOTES

Choose a route for your use case

Start with the destination service’s regional requirements, then choose a route that can reliably complete your task. No route name guarantees compatibility with every app, and you do not need to keep changing exits for different tasks.

Everyday browsing and research

If a website has no specific regional requirements, start with a commonly used Asia-Pacific exit and compare direct and relayed routes in practice. Open the pages you use and check that text, images, sign-in, and downloads all work. A homepage loading only confirms that some resources are reachable; it does not mean every part of the site is working.

Once you find a route that works, keep it as your usual choice and have another route available as a backup. If a page occasionally fails to load, check your local network first, then compare routes in the same region. This helps avoid mistaking website maintenance for a route issue.

Streaming and video

First identify the regional content library you need, then test the platform homepage, account sign-in, and playback of specific titles. Reaching the homepage and playing the content you want are different outcomes. Licensing, account settings, and exit IP checks can all affect playback, so an exit region in the table is not a promise of library access.

Continuous playback is a better test than loading a page once. During your usual viewing hours, check for buffering and playback interruptions, and confirm the client’s routing rules include the streaming app. If the app still shows the previous region after changing exits, reopen it and check the session. Avoid cycling through multiple countries to try to refresh the content library.

Accessing AI tools

Before accessing AI tools such as Claude, check the service’s current supported regions and terms of use. A successful network connection does not establish account eligibility or guarantee that every feature is available to every account. Your exit region needs to meet the service’s requirements; the route type itself cannot change the service’s account checks.

If your account is already working normally, try to keep the exit region consistent with your usual environment. If you see a regional notice or sign-in check, save the error message and check service announcements, account status, and your current exit before changing routes. For more on regional access and risk checks, see Choosing a route for Claude →.

Gaming and interactive apps

Check the game server’s region and whether the client allows the relevant traffic through the current connection. Downloads, account sign-in, updates, and gameplay may use different network paths, so a successful download alone does not confirm that a match will work.

This service’s international route directory does not guarantee compatibility with any particular game. If needed, test the full process outside critical play times and follow the game operator’s rules. If only one app has a problem, check its proxy support and routing settings rather than assuming a farther or more expensive route will fix it.

Work, meetings, and file collaboration

For work, prioritize session stability. Choose a tested route in a region permitted by your organization’s apps, then check single sign-on, document editing, meetings, and file uploads separately. Your organization’s administrator may restrict access regions or require a dedicated access method; follow your organization’s security requirements.

Avoid changing exits during a meeting or file upload, as reconnecting can interrupt the task. Unlimited simultaneous connections is a device-use policy, not a guarantee that activity on each device will never affect the others. Background sync, downloads, and video playback can still share local network capacity. When troubleshooting, pause nonessential tasks first, then check your work apps.

BEFORE SWITCHING

A pre-switch checklist

Check your subscription, then your route

If an exit listed here is missing from your client, check your plan status and data usage in the user dashboard, then update your subscription. This static directory explains regions and route types; the client list shows what is currently available to your account. Do not assemble server addresses manually or replace your account configuration with a subscription from an unknown source.

After connecting, test the actual website you need. Check sign-in first, then confirm its core features work. If only one site has a problem, review its routing rules and service status. If nothing works, check your local connection, client status, and whether the subscription update succeeded. Change one thing at a time so you can tell what made a difference.

For help, submit a ticket through the user dashboard. Include the platform, client message, route name, approximate time of the issue, and results from other routes in the same region. Redact sensitive account details from screenshots, including anything beyond your username. Do not send your full subscription URL, password, or login credentials. For more troubleshooting steps, see the troubleshooting guide →.