Network layer / regions and connection paths

VPN server locations and international routes

110+ countries / 220+ routes. Start with the region your service requires, then choose a connection path that suits your needs.

No device limit Bank-grade encryption 7-day no-questions-asked refund

View routes in the dashboard View plans →

This page is a static route-selection guide. Sign in to the user panel to check current cities, connection types and available nodes.

Browse routes by region

The regions below are popular locations, not a complete node list. A region identifies an exit location; it does not guarantee access to any particular website.

Popular countries and regions: cities, connection types and streaming availability
Country / Region	City	Connection type	Streaming availability
Asia-Pacific
Hong Kong	See the user panel	See the route details	Depends on the target platform
Japan	See the user panel	See the route details	Depends on the target platform
Singapore	See the user panel	See the route details	Depends on the target platform
North America
United States	See the user panel	See the route details	Depends on the target platform
Europe
Italy	See the user panel	See the route details	Depends on the target platform
Netherlands	See the user panel	See the route details	Depends on the target platform
Other
Other covered regions	See the full list in the user panel	See the route details	Check each target platform separately

The same region can have different connection paths

When choosing a location such as Hong Kong, Japan or Singapore, first check whether the target website accepts connections from that region, then test it in practice. Geographic proximity can help narrow down your options, but the experience also depends on your local network, entry point, carrier peering and the target server’s location. A region name alone cannot tell you how the full route will perform.

Choose US and European locations based on your needs, too. If a service requires a specific region, start by meeting that requirement. If it doesn’t, there’s no need to add route complexity just to use a more distant exit location. City and connection-type details follow the user panel’s listings so that regional coverage isn’t mistaken for a promise about a specific data center, transport path or fixed exit.

Check the user panel for the full list of other regions. This page doesn’t expand unlisted countries, cities or connection details into a node directory. If node names or groups change after a client subscription update, use the nodes and route details currently shown in your account rather than looking for names from an old screenshot.

Route types and path differences

IEPL, relayed and direct connections describe different ways of organizing a network path. The following explains these technical concepts; it does not mean every region offers every type or promise a specific node configuration.

Dedicated transport segment

IEPL

IEPL generally refers to an international Ethernet private line, a dedicated transport service provided by carriers to connect different locations. For cross-border access, it can carry the cross-region segment of a route. The connection from your device to the entry point and from the exit to the target website still matter, so the name of a private line alone cannot tell you how the complete connection will perform.

This type of path may suit tasks where consistent data transfer matters, such as extended collaboration sessions and file syncing. Actual performance still depends on entry-point reachability, transport capacity and exit peering. An unstable local wireless connection, a sleeping device or a busy target website can still interrupt service; changing only the transport segment won’t fix every issue.

Dedicated transport usually requires more explicit capacity planning and line procurement, so its cost structure differs from ordinary public internet transport. That doesn’t mean a particular VPNBody plan includes a dedicated line or that any route delivers fixed performance. Check the node details to confirm the route type; if it isn’t listed, don’t assume.

Entry-point relay

Relayed connection

A relay connects you to an entry point first, which then forwards traffic to a subsequent node. Your initial connection point and final exit region may be different. Relaying organizes the path so that the entry connection and exit selection can be handled separately; it doesn’t simply shorten the geographic distance.

When your local network has a suitable path to an entry point, a relay may be an option for everyday browsing, work or streaming. The extra forwarding step also means the entry point and onward transport need to work well together. An entry point that performs well on one network may not do so on another carrier or connection.

Relaying involves resources for the entry server, forwarded traffic and onward links, and configurations can vary considerably. It isn’t inherently the same as an IEPL private line or better than a direct connection. For a fair comparison, use the same local network and target service. Avoid changing the exit region and app settings at the same time, or it’ll be hard to tell what made the difference.

Public internet path

Direct connection

A direct connection generally means the client connects to the target node over the public internet without an additional service relay entry point. “Direct” describes how the connection is organized, not a route without physical network equipment; traffic still travels through local access networks and carrier infrastructure.

Direct connections can help you compare paths and may suit general browsing. Public internet routing varies by carrier, time of day and destination, so a smooth connection at one time doesn’t guarantee the same performance all day. If performance fluctuates, first distinguish a local network issue from a problem on the route to the target node, then decide whether to try another entry point or region.

Compared with options that require dedicated transport or relay resources, a direct connection usually has a simpler resource setup, though actual costs still depend on exit traffic and infrastructure. Route costs are not the same as the price you pay. Check the VPNBody plans page for plan prices and traffic rules; don’t infer them from a route type.

Choose a route by use case

Choose in this order: target service requirements, compatibility with your local network, then performance for the task at hand. Different use cases call for different checks; there’s no need to look for one answer based on a route name alone.

WEB

Everyday browsing

Start with a route that meets the website’s regional requirements and is easy to identify, then open sites you use regularly. Check more than whether the homepage loads: make sure pages work after signing in, images load and internal links open. It’s common for a homepage to load from cache while later content comes from other domains, so seeing a headline isn’t proof that the whole visit works.

If a page opens but images or sign-in don’t work, check that the client’s split-tunneling rules and your browser’s proxy settings are consistent. Don’t immediately switch between several regions. Keep your settings unchanged, try another route in the same region, then compare results to distinguish a route issue from an app configuration problem.

MEDIA

Streaming

First check whether the target platform offers its service in the selected region, then verify your account region, subscription access and content rights. The platform determines which titles are available; a network connection only provides an access path and can’t replace account eligibility. A node in a particular region doesn’t mean every title there will play.

Test through playback: check whether video starts, scrubbing works and playback continues normally. If the page loads but the player shows a proxy warning, follow the platform’s instructions to check its exit-location decision. After switching routes, start a fresh app session so old connections don’t affect the results. Keeping a stable route while watching makes troubleshooting easier than switching repeatedly.

AI tools

Tools such as ChatGPT, Claude and Gemini may have different regional policies and account requirements. Check the target service’s current published requirements first, then choose an eligible region. Network access doesn’t guarantee that your account is eligible; sign-in verification, account status and platform risk controls can all affect access.

These tools also rely on sustained sessions. Seeing an input box doesn’t guarantee that a long response will stream completely; test an actual prompt, response and follow-up conversation. Keep the exit region consistent while using the service, and avoid changing routes repeatedly between sign-in and submitting a request. APIs and web apps may use different domains and connection settings, so developers should check each separately. See the AI Access Guide.

PLAY

Gaming

Check the game server region and the game’s network rules first, then decide whether the current client route is suitable. Game websites, sign-in services, updates and live matches may use different addresses, so a smooth download doesn’t tell you how a match will perform. A geographically close route isn’t necessarily the best path to the game server.

For a fair comparison, use the same game region and local connection, and watch for delayed input, dropped sessions or voice chat issues. Some apps depend on specific transport methods and client support, so check the actual configuration. This page doesn’t describe general international routes as game-specific connections or promise match results.

WORK

Remote work

Follow your company’s requirements for network access and data handling first. Meetings, shared documents, file syncing and company sign-in may each rely on different domains. Testing search or general web browsing won’t cover the full workflow. Before an important meeting, test video and audio, screen sharing and document access on the network you plan to use.

For longer work sessions, keep a familiar primary route and a backup option, but don’t switch during a meeting or file upload without a reason. Changing the exit may disrupt existing sessions and require you to reconnect. VPNBody supports Windows / macOS / iOS / Android / Linux with no device limit. Check client rules on each device; traffic is based on your selected plan.

Check the connection before and after switching

Narrow down the issue before changing routes. Keeping a clear record of each step makes it easier to reach conclusions you can repeat.

Check your subscription and client

Sign in to the user panel to check your subscription status, update the subscription in your client and confirm the selected node. The client and subscription links are all in the user panel, so you won’t mistake an old configuration for the current route list. No email address is required; create an account with a username and password.

Get the client →

Keep comparison conditions consistent

Use the same local network and target, try another route in the same region first, then consider changing regions. After switching, reopen the target app so it uses the new connection. If you change your access network, region and split-tunneling mode all at once, it’s difficult to tell which change affected the result.

Read the getting started guide →

Record the issue and submit a support ticket

If the issue persists, note the service you’re using, the route name shown in the client, where the error occurs and any message displayed, then describe it in a support ticket through the user panel. Hide account details and subscription links in screenshots. Don’t post a complete subscription URL in public discussions or share your password with anyone.

Open a support ticket →

Choose your route and plan separately

Route coverage helps you choose a connection direction; plan traffic helps you manage everyday usage. They’re separate considerations. Monthly subscription traffic resets each month on the activation date, and the price difference for a mid-cycle upgrade is prorated for the remaining days. Traffic add-ons remain available until used and never expire. First confirm that your apps can complete the tasks you need in your chosen setup, then compare prices and traffic on the plans page. VPNBody offers a 7-day no-questions-asked refund; see the Terms of Service for details.