7xVPN / Location index

Global VPN Servers

Filter by exit region first, then compare route types. The table lists selected international routes; available servers may differ in the route list after you sign in.

View route table
Countries covered
120+
Number of routes
180+

Route directory

Regional Route Table

The city column shows the route's exit location, not its connection entry point. Streaming notes only identify services specifically listed as references. “Not specified” does not mean unsupported or available.

Sample international routes · by region
Country or region City Route type Streaming notes
Asia-Pacific
Hong Kong, ChinaHong KongIEPLNetflix
JapanTokyoRelayNot specified
SingaporeSingaporeIEPLDisney+
North America
United StatesLos AngelesDirectYouTube
Europe
SwitzerlandZurichRelayNot specified
Other regions
Not listed individually on this page. Check the user dashboard for details.

Streaming availability still depends on platform rules, account region, and the catalog you want to access. After connecting, check your exit location on My IP, then test the service itself.

Transport types

Route types and costs

Route type describes how traffic reaches its exit, not a speed rating. Two routes with the same exit region may take different paths; the same route type can also perform differently depending on the local network you connect from.

Dedicated segment

IEPL

IEPL is an international Ethernet private line. It uses a dedicated circuit for the cross-border segment to reduce reliance on changes in public internet routing along that segment. A private line does not mean traffic travels over one circuit from your device to the destination website: the connection from your device to the entry point still depends on local access, and the path from the exit to the destination depends on the onward route. So a private-line label does not guarantee the same performance at every time or for every destination.

Dedicated circuits typically involve leased capacity, ports, and bandwidth planning, with costs that differ from shared public-network forwarding. Consider a private line for extended streaming, sustained uploads, or video meetings. If a short test works but interruptions appear later, first check whether your local network is also fluctuating, then compare another route with the same exit region. Don’t rely on the route label alone to identify the cause.

Relay

Relay

A relay route receives your connection at an entry point, then forwards it to an exit in the destination region. This lets you choose the “local network to entry” and “entry to exit” segments separately: even if your local carrier’s direct route to an exit is poor, another entry point may provide a different path. Relaying adds a forwarding step, and congestion at the entry point or a poor route choice can make it less smooth than a direct connection.

Relay costs typically come from the entry server, exit server, and transmission across both network segments; they do not necessarily include the cost of a dedicated circuit. If a direct route to a particular region often drops during your usual hours, keep the same exit region and try a relay route first. This changes the path without changing the region, helping avoid platform region rules or account checks triggered by switching exit locations.

Direct

Direct

Direct means the client connects to the selected exit without an additional relay entry point configured by the service. Traffic still passes through carriers and upstream networks, so the path is not a literal straight line. If routing between your local carrier and the exit network is suitable, direct can remove one service forwarding step. If upstream routing takes a detour, a geographically closer exit may not be a better choice.

Direct routes typically use fewer relay resources, but still incur costs for exit servers, traffic, and network interconnection. They can serve as a baseline for everyday browsing: check whether your usual websites load smoothly, then decide if you need another path. These cost differences reflect how routes are deployed, not separate per-server pricing. See the Plans page for subscription prices and data policies.

Selection notes

Choose a Route by Use Case

First confirm which exit regions the service you want to use accepts, then decide which route types to compare. Change one variable at a time: switch route type within the same region to compare paths, or switch regions with the same route type to compare exits. Judge by what you can actually do; a successful connection alone does not mean the task is complete.

Everyday browsing

Start with a nearby exit that meets the website’s region requirements. Test sites you normally visit: check that the homepage opens, images load, and internal links work. If the homepage loads but static content takes a long time, don’t stop at “it opens.” If the issue occurs on only one site, check whether it is under maintenance or has extra requirements for your account or browser extensions.

If several sites show similar issues at once, try another route in the same region on the same network before switching regions. Don’t change routes while also switching Wi-Fi or browser settings, or it will be hard to tell which change made a difference.

Streaming

First check whether the platform appears in the reference notes for a candidate route, then confirm which catalog your account can access and which exit region you’ve selected. Opening the homepage is not a meaningful playback test. Play the content you actually want to watch and check startup, recovery after seeking, and repeated buffering during playback. When comparing routes, use the same device, title, and video quality settings where possible.

If the platform reports a region mismatch, check the exit location and account eligibility first instead of repeatedly switching between IEPL, relay, and direct routes. If playback works but often stalls during your usual viewing hours, compare different paths in the same exit region and check whether other devices at home are using the local network.

AI Tools

Before choosing an exit, confirm the regions where the service is available, account requirements, and usage rules. Test sign-in, request submission, receiving generated content, and file uploads separately: signing in successfully does not guarantee a longer request will finish. Check with a task you actually need, such as sending a request that streams a response, and see whether the full response completes.

Keep the same exit for an entire work session where possible. For region, account status, or usage limit messages, follow the service’s instructions; changing routes will not change account permissions. If there are no account-related messages and the connection drops only during long responses, try another route in the same region without changing the exit or task at the same time.

Online gaming

Choose a route based on the game server region, not the route name. First identify the region of your actual matches, then compare nearby exits for input response, rubber-banding, and disconnections. Test in the same game mode and at your usual time where possible. Lobbies, sign-in screens, and matches may connect to different servers, so the lobby experience is not a substitute for testing a full match.

If only one server region has issues, check the game service status first. If several regions show similar fluctuations when your local network is busy, pause background downloads and test again. Once you find a route that reliably completes matches, switch before matchmaking rather than changing exits mid-game.

Remote work

Choose an exit according to your organization’s access policies. For corporate gateways, internal tools, or authentication services, first confirm that your organization allows access and whether it requires a specific network or region. Test document collaboration, uploads, and audio/video meetings separately: opening a document list does not confirm that file uploads or screen sharing will stay connected.

Test audio, screen sharing, and file uploads before a meeting, and note which exit city and route type work. If you’re asked to authenticate again or access is denied, keep the error message and check with your organization’s administrator first. Avoid repeatedly changing exits before account verification is complete, so connection issues don’t get confused with access policies.

For your first connection, follow the Guides to import your subscription. If problems persist, troubleshoot connection or route issues in the Support Center. When submitting a ticket, include your device platform, exit city, route type, and steps to reproduce the issue. Do not include subscription links or account credentials.