VPNXB / ROUTE DIRECTORY

VPN Server Locations and
Cross-Border Routes

Coverage spans 100+ countries and 180+ routes.
Choose a destination region, then check the exit location and route type.

Unlimited simultaneous devices 60-day money-back guarantee View account routes

Browse route locations

Start with the region. The connection experience also depends on the entry path, exit location, and where the destination service is hosted.

These countries and cities illustrate location options; they are not a list of currently available nodes. The subscription list in the client shows the routes you can actually use. Check route type, exit location, and available cities after importing and updating your subscription. This directory does not rank performance or imply that every city has a dedicated route.

How to read the table: “Check on platform” means you should verify how the target platform identifies the region; it is not a guarantee of streaming access. On mobile, swipe horizontally across the table to see all columns.

Location directory · Check the client for current routes and availability
Country / region City Route type Streaming availability
Asia Pacific
JapanTokyoCheck the client for availabilityCheck on platform
JapanOsakaCheck the client for availabilityCheck on platform
SingaporeSingaporeCheck the client for availabilityCheck on platform
Hong Kong SAR, ChinaHong KongCheck the client for availabilityCheck on platform
South KoreaSeoulCheck the client for availabilityCheck on platform
AustraliaSydneyCheck the client for availabilityCheck on platform
New ZealandAucklandCheck the client for availabilityCheck on platform
North America
United StatesLos AngelesCheck the client for availabilityCheck on platform
United StatesSeattleCheck the client for availabilityCheck on platform
United StatesNew YorkCheck the client for availabilityCheck on platform
CanadaVancouverCheck the client for availabilityCheck on platform
CanadaTorontoCheck the client for availabilityCheck on platform
Europe
ItalyMilanCheck the client for availabilityCheck on platform
GermanyFrankfurtCheck the client for availabilityCheck on platform
United KingdomLondonCheck the client for availabilityCheck on platform
FranceParisCheck the client for availabilityCheck on platform
NetherlandsAmsterdamCheck the client for availabilityCheck on platform
SpainMadridCheck the client for availabilityCheck on platform
SwedenStockholmCheck the client for availabilityCheck on platform
Other regions
United Arab EmiratesDubaiCheck the client for availabilityCheck on platform
BrazilSão PauloCheck the client for availabilityCheck on platform
South AfricaJohannesburgCheck the client for availabilityCheck on platform

When choosing a location, distinguish between the entry point, exit point, and destination server. The entry point is where your device connects first; the exit point is the network location seen by the destination website; the server is where the website or app processes your request. These locations can differ, so a node name alone does not describe the entire connection path. For region-specific content, check the exit location. For smooth work, also assess how the destination service responds.

Geographic distance is only a starting point. Nearby locations are often worth trying first, but ISP routing, congestion, and server-side delivery all affect performance. Don’t assume a route is fastest based on its city name, or treat someone else’s experience as a reliable guide to your local network. Keep the routes that suit your needs and check them again at the times you usually connect.

Dedicated, transit, and direct routes

The following explains common route designs; it does not mean VPNXB offers every type in every region. Check the client for current route labels.

PRIVATE TRANSPORT

IEPL dedicated line

For more predictable routing

IEPL generally refers to an international Ethernet private line that carries traffic between designated network endpoints. Compared with routes that rely entirely on the public internet across regions, a dedicated segment can reduce uncertainty caused by some routing changes. However, your device-to-entry and exit-to-destination connections may still use public networks. “Dedicated line” does not mean the entire connection uses a private path, nor does it guarantee the same experience at all times.

This design can suit long-lived connections and sustained transfers, such as remote work, file syncing, and extended video playback. Leasing, capacity planning, and maintenance usually cost more. When assessing a route, check which segment uses the dedicated line rather than relying on the label alone. Client protocol and route type are also different: the same protocol can use different paths. Encryption and route design should be considered separately.

RELAY TRANSPORT

Transit route

For a considered entry and exit combination

A transit route sends a request to an entry point first, which then forwards it to an exit point. This adds a forwarding hop but also allows more flexibility in choosing the path. If the public route from your device to the destination region is poor, a suitable entry point and forwarding path may improve the experience. Transit is not automatically slower, and direct is not automatically faster; assess the complete route.

Transit routes can suit everyday browsing, cross-region work, and services that require a specific exit location. Costs depend on entry resources, forwarded traffic, and exit maintenance, and vary by network combination. Congestion at the entry point or instability along the forwarding segment can also affect the connection. To compare transit routes, use the same local network and target app, and check page loads, interruptions, and sustained transfers—not just the regions in the route names.

DIRECT TRANSPORT

Direct route

For performance over public routes

A direct route generally means your device connects to the destination node without an additional transit entry point. The path is simpler, typically requiring fewer operational steps and fewer resources, but actual traffic still depends on ISP routing. “Direct” describes the deployment, not a straight line on a map. Public traffic may pass through different exchange points, and congestion or route changes can affect how apps perform.

If your local network has a good path to the destination region, a direct route can be worth trying for browsing and light use. If performance changes noticeably in the evening, consider both your local network and the public route rather than blaming the protocol alone. Lower cost does not necessarily mean lower quality; dedicated, transit, and direct routes reflect different resource trade-offs and should not be ranked by label alone. For more on how they work, see the protocol reference.

Choose a cross-border route by use case

Start with what the app needs. Location, sustained transfers, and connection consistency matter more than a node name.

Everyday browsing: start with a familiar region

When browsing international websites, try a nearby region where the service is accessible. Open the sites you use regularly and check that text, images, and sign-in all work. Seeing the homepage does not mean every resource uses the same path: images, verification pages, and file attachments may come from different servers. A route that consistently handles these tasks is more useful than frequently switching regions.

If only one website has loading issues, first check its status, your browser cache, and your routing rules. When switching routes, change only the route and keep your local network and client settings the same. This makes it easier to identify what changed. Once you’ve found a route that works for everyday use, save a backup if you like; there’s no need to compare every node each time you browse.

Streaming: check the region, then test playback

Platforms such as Netflix and Disney+ may use the exit IP address, account region, subscription eligibility, and content licensing to determine what you can watch. A node labeled for a region does not mean every title from that region will be available. Check your account and the title’s licensing first, then verify how the platform identifies your exit location. If the platform reports a region mismatch, changing the client protocol alone may not help.

Streaming depends on sustained data transfer, not just a quick response when a page opens. Test startup, resuming after seeking, and continuous playback at your usual viewing time. Higher resolutions require a more stable connection and local network, and use more plan data. This service does not guarantee “buffer-free 4K” on every route. See the streaming access guide for detailed checks.

AI tools: keep your region and session consistent

When using ChatGPT, Claude, or Gemini, first check which regions the tool supports and any account requirements. A network route affects how you connect; it does not replace eligibility requirements set by the platform. If you see a region notice, verification page, or access error, distinguish a connection issue from platform rules instead of assuming every error is caused by the node.

For long generations, file uploads, and ongoing sessions, a consistent exit location is usually preferable to repeatedly switching regions. After signing in, stick with a route you’ve verified and avoid changing paths during a task; if you must switch, save your work first. For Claude acceleration and connection checks for other tools, see the AI tools access guide.

Gaming: check the client and traffic requirements first

Games can be sensitive to brief fluctuations, packet loss, and interrupted sessions. A smooth download does not guarantee a good gameplay connection. First confirm that your client, protocol, and routing rules cover the game’s traffic, especially its UDP traffic. A working browser connection alone does not confirm that game traffic is routed through the service.

Choose a route based on the game server’s location, not just where you are. Test sign-in, matchmaking, and connection stability in training or other low-stakes situations before using a route for a competitive match. A route subscription is not a dedicated optimization service for any particular game, and this page makes no claims about competitive performance. If something goes wrong, note the game, server region, and client status to help distinguish a server issue from a routing issue.

Work: prioritize completing your workflow

Remote work often involves meetings, documents, code repositories, and cloud storage, and different services may use different network paths. Test with real tasks: open a shared document, sync a file, join a meeting, and check the audio. A working sign-in page alone does not show whether the rest of your workflow will be reliable. If your organization has network requirements, follow its access and device management policies first.

When using enterprise connection tools at the same time, check whether their routing and DNS settings conflict. Don’t route all system traffic through multiple tools at once without confirming the setup. VPNXB supports Windows / macOS / iOS / Android / Linux, with unlimited simultaneous devices. Each device’s experience still depends on its local network. For work, keep the exit location consistent and save anything you’re editing before switching routes.

From importing a subscription to checking the connection

Check “connected” and “the target app works” separately for clearer troubleshooting.

Check your subscription and client status first

Get the client and subscription from the user panel, then follow the quick start guide to import them. Update the subscription and check your current plan status and data usage before selecting a route from the list. This static location directory cannot replace the current node information in your client. If the import succeeds but the list does not update, troubleshoot subscription syncing first rather than looking for a fixed address by city name on this page.

Check the actual exit location and routing scope

After connecting, first check whether the client is routing traffic from the target app. System proxy settings and an app’s own network settings can differ, and browsers, desktop tools, and games may not use the same path. If your apparent exit location is not what you expected, check that you selected the right route, that the current rules cover the target app, and that no other connection tool is running. Don’t rely on the client’s connection indicator alone to determine the final exit location.

Compare routes using real tasks

Use the same device, local network, and app for each comparison, and check whether the whole task runs smoothly. If every region has problems, first check your local Wi-Fi, system settings, and the target service’s status. If one route has issues, try another option for the same use case and test again. Avoid changing the protocol, rules, and region all at once; otherwise, even if the issue clears, it will be hard to tell why.

To report an issue, use the support ticket page in the user panel and include the route name, platform, target app, and error message. Don’t send your full subscription link, password, or account credentials. Details about what you were doing and when the issue occurred can help identify whether it involves the subscription, routing rules, network path, or target platform.

Route and location FAQs

Can I select any city in this directory?

Do not treat this reference directory as a list of currently available nodes. VPNXB covers 100+ countries and 180+ routes; check the updated subscription list in the client for actual cities, node names, and route types. The directory helps you understand which locations to consider, but does not guarantee that a city will always have an available node.

If a node is labeled Japan, will I definitely see Japanese content?

Check the exit location, account region, and content licensing separately. Platforms may use different rules to determine your region, and their content catalogs can change. A route’s region label does not replace checking on the platform or guarantee that a particular title is available.

Is a dedicated line always better than a direct route?

Not necessarily. A dedicated line offers more control over a specific segment of the route, but the overall experience also depends on your local connection, entry point, and destination service. A direct route may work well when the public path is clear. Compare routes using the tasks you need to complete rather than relying on labels.

Can different devices use different regions?

Unlimited devices can be connected at the same time. Each device can select an available route in its client. If you use the same account on a target platform from different regions, follow that platform’s session and region rules. Support for multiple devices does not mean the platform permits every combination of locations.

How does plan data relate to route locations?

Choosing a location does not replace managing your plan data. Monthly subscription data resets monthly on the activation date; when you upgrade mid-cycle, the price difference is prorated for the remaining days. Data add-ons do not expire and remain available until used. See the plans page for full pricing and billing details, and check your current account status in the user panel.

What account and refund details should I know before getting started?

No email address is required; create an account with a username and password. VPNXB offers a 60-day money-back guarantee. See the refund policy for details. This page does not guarantee route performance or access to specific content.

Start Free