Choose a route · Locations and paths

VPN server locations
and cross-border routes

Choose an exit location first, then consider the route type. The location determines the apparent source of your connection to a service; the route affects how the connection gets there. Assess these separately.

110+ countries / 160+ routesCoverage

UnlimitedSimultaneously connected devices

7-day refund policyRefund policy

This page is a static route-selection guide and does not show live connection status. Sign in to the account dashboard to see actual route names, cities, and available types.

View routes in dashboard View plans

Locations and exit points

Coverage includes 110+ countries and 160+ routes. The examples below cover commonly used locations and are not a complete inventory. Route types illustrate how to compare paths; they do not mean a particular type is always available in a given location. Check the dashboard for current options. Countries and cities in Europe and other regions are not listed here unless confirmed.

A country or region label identifies the exit location; a city narrows it down but does not mean all data travels through that city. Routes in the same location may take different paths, and performance can vary across local networks. Proximity is a useful starting point for filtering, not a substitute for testing the connection.

Location and route type reference—not a list of currently available routes
Country or region	City	Example route type	Streaming support
Asia-Pacific
Japan	Check the dashboard	Relay	Test with the service you plan to use
Singapore	Check the dashboard	Direct	Test with the service you plan to use
Hong Kong	Check the dashboard	IEPL route	Test with the service you plan to use
Australia	Check the dashboard	Relay	Test with the service you plan to use
North America
United States	Check the dashboard	IEPL route	Test with the service you plan to use
Canada	Check the dashboard	Direct	Test with the service you plan to use
Europe
Check the dashboard for available countries	Check the dashboard	Check the route details	Test with the service you plan to use
Other regions
Check the dashboard for available countries	Check the dashboard	Check the route details	Test with the service you plan to use

Route types and how paths differ

IEPL, relay, and direct describe how a network path is organized, not a simple ranking of quality. Knowing the difference can help pinpoint whether an issue lies with the entry point, the cross-border segment, or the destination service—instead of switching locations at random whenever a connection falters.

IEPL route

Dedicated capacity on the cross-border segment

IEPL usually refers to an international Ethernet private line. In a route design, it carries a specific cross-border segment; the connection from your device to the entry point and from the exit point to the destination may still use other networks. An IEPL label does not mean there is a dedicated end-to-end connection between your device and a website, nor does it guarantee a particular speed.

This route type may be worth considering when connection continuity matters, such as for remote meetings, extended work sessions, or ongoing requests. To assess whether it suits you, try your usual tasks during the times you normally use them. Check for repeated disconnections or sessions that need to be restarted, rather than judging by the route label alone.

Costs typically reflect cross-border capacity and its upkeep. The resources and network arrangement differ from those of public routes, but underlying costs are not a separate charge set by VPNSelf, and dedicated routes may not be available in every location. Check the dashboard for route availability and the pricing page for plan prices; these are separate details to verify.

Relay

A route via an intermediate node

A relay route adds an intermediate node between your device and the final exit point to forward traffic between the entry and exit. It can change how your local network connects to an international route, but an extra relay does not inherently make a connection faster. The entry network, onward transport, and exit status all affect the experience.

If a direct connection to an exit point is unreliable on your local network, compare relay routes in the same region. Streaming, browsing, and work tasks can all help you test the connection. Keep the destination service and local network the same so you can tell whether changing the route made a difference.

Costs mainly involve relay nodes, transmission resources, and forwarding maintenance. Relay routes generally involve more route-management steps than direct connections, while their capacity arrangements may differ from those of dedicated routes. This provides context for the technical trade-offs; it does not imply a fixed price difference or indicate which routes are included with a particular plan.

Direct

Fewer intermediate forwarding steps

Direct usually means the client connects to the destination exit point without an additional relay node arranged by the service. The connection still passes through your local carrier and internet routing, so “direct” does not mean the shortest physical distance or that no other network equipment is involved.

Direct can be a useful starting point for everyday browsing or when your local network has suitable international connectivity. If pages load but ongoing requests or file transfers are unstable, compare other routes in the same region. A successful first connection alone is not enough to determine whether a route will work reliably over time.

This setup typically uses fewer dedicated relay resources, but actual costs also depend on exit resources and network procurement. Direct is not necessarily a lower-priced option, and a dedicated route is not necessarily a higher-priced one. Choose based on your use case and actual performance; billing follows the published monthly subscription and data add-on terms.

Choose a cross-border route by use case

Choose a route in this order: service location requirements → exit location → route type → real-world task. Change one factor at a time and keep choices that already work. That way, if something goes wrong, you can identify what changed instead of losing track after changing the location, client mode, and app settings all at once.

Everyday browsing

For sites without specific location requirements, start with a nearby location available in the dashboard. Check the homepage, sign-in page, and the content you use regularly; access to the homepage does not guarantee that site resources or account services are working too. If only one site has an issue, check whether the site itself is having problems before switching routes.

Once you find a route that works, keep it as your everyday default and note the client’s current connection mode. Rule-based and global modes can send different apps along different paths, so a working browser connection does not prove that other apps are connected too.

Streaming and live broadcasts

Before streaming, check which regions have rights to the content you want, then choose an appropriate exit location. A Japan route can be a starting point for checking content in the Japanese catalog, but playback depends on how the platform identifies your account and exit point. Finding a title, opening its details, and starting playback are separate checks.

Test with the app and picture quality settings you normally use. Check playback, seeking, and subtitle loading. If only one app fails, first confirm that it is using the selected route. Don’t keep switching countries because of a brief pause; frequent changes can also prompt the platform to reassess your session.

AI tools

For tools such as ChatGPT and Claude, first check the service’s supported regions and account requirements. A network route only handles the connection path; it does not replace eligibility requirements set by the platform. A webpage loading does not mean that sign-in, file uploads, extended generation, or API requests will all work with the same settings.

For tasks that take time, keep an eligible exit location and route consistent where possible, and avoid switching routes while a request is in progress. In development environments, check that your terminal, editor, and calling program are actually using the client’s route; a working browser connection does not prove API requests are connected. See the AI tools guide for more.

Gaming connections

Choose a location based on your account’s game region, the game’s terms of service, and the actual server location—not just what is geographically closest. Launcher sign-in, content updates, and gameplay may use different network services, so signing in successfully does not confirm that the entire game will work as expected.

First check that your client supports the connection method required by the game, then test it in practice. The route type labels for this service do not guarantee gaming performance or compatibility with any particular game. Follow the game publisher’s guidance if it has specific network requirements.

Remote work

For work, prioritize connection continuity during extended sessions and follow your organization’s network policies. Enterprise services may determine access based on exit location, account permissions, or trusted networks. Switching locations may not resolve an access issue and could trigger another authentication check.

Test meetings, document syncing, and file transfers separately. Avoid switching routes during work if possible; if you need to reconnect, save your work first. If you also use a corporate network client, ask your organization’s administrator about potential configuration conflicts. Do not change security settings managed by your organization.

Connection checks and routine maintenance

Make sure your subscription is up to date

The route list comes from the subscription retrieved after sign-in. If the dashboard and client show different routes, use the client’s subscription update feature and check whether it completes successfully. Then confirm that your selected route is still available. Don’t copy unknown subscriptions from public forums or post your own subscription link publicly.

VPNSelf supports Windows / macOS / iOS / Android / Linux. On platforms other than iOS, sign in to get the client; iOS access depends on an eligible plan in the dashboard. Retrieve your subscription after signing in. For import steps, see the getting started guide.

Separate route issues from account issues

After the client reports a successful connection, open the service you want to use and try the task you normally perform. If regular websites work but the target service shows an error, check its message, your account region, and the app’s connection settings. If several services have issues, compare other route types in the same region.

Unlimited devices means there is no limit on the number of devices connected at the same time; it does not give each device a separate plan data allowance. Monthly subscription data resets on each monthly renewal date. Data add-ons remain available until used and never expire. Before troubleshooting, also check your plan status and remaining data in the dashboard.

No email address is required to get started—just a username and password. Find details about plans, routes, and connection steps on the pricing page, in the account dashboard, and in the complete guide. This page is a reference for choosing locations and routes.