DATA PATH · LOCATIONS & ROUTE TYPES

VPN Server Locations
International Route Guide

Start with the exit location, then consider the connection path. The location determines where a service sees your connection coming from; the route type describes how traffic reaches that exit.

VPNDP covers 110+ countries and 230+ routes. The regional list below is a static reference, not a complete inventory. Check the subscription available after login for current routes, names, and types.

Browse locations ↓ How to import your subscription ›

REGIONS

Regional exits and routes

The table lists reference locations, cities, and route types. Streaming services may also consider your account, regional content catalog, and exit status, so a city name alone cannot confirm whether a title will play.

Reference locations and route types; check your subscription for availability
Country / region	City	Route type	Streaming support
Asia-Pacific
Japan	Tokyo	IEPL	Check on the platform after connecting
Singapore	Singapore	Relay	Check on the platform after connecting
Hong Kong	Hong Kong	IEPL	Check on the platform after connecting
South Korea	Seoul	Relay	Check on the platform after connecting
Australia	Sydney	Direct	Check on the platform after connecting
New Zealand	Auckland	Direct	Check on the platform after connecting
North America
United States	Los Angeles	Direct	Check on the platform after connecting
United States	Seattle	Relay	Check on the platform after connecting
Canada	Toronto	Relay	Check on the platform after connecting
Mexico	Mexico City	Direct	Check on the platform after connecting
Europe
Germany	Frankfurt	Relay	Check on the platform after connecting
United Kingdom	London	Direct	Check on the platform after connecting
France	Paris	Relay	Check on the platform after connecting
Netherlands	Amsterdam	Relay	Check on the platform after connecting
Sweden	Stockholm	Direct	Check on the platform after connecting
Switzerland	Zurich	Direct	Check on the platform after connecting
Other regions
Brazil	São Paulo	Relay	Check on the platform after connecting
Chile	Santiago	Direct	Check on the platform after connecting
South Africa	Johannesburg	Direct	Check on the platform after connecting
United Arab Emirates	Dubai	Relay	Check on the platform after connecting

TOPOLOGY

Route types and trade-offs

Route type is not a speed rating. Understand the path first, then choose based on how your apps perform. Consider the protocol, exit location, and route type separately.

IEPL

Access → dedicated backbone → exit

IEPL generally refers to an international Ethernet private line that connects network endpoints in different regions over dedicated capacity. Compared with paths that rely entirely on public internet routing, the dedicated segment’s route and capacity are easier to manage. However, the client’s access network and the connection from the exit to the destination site can still be affected by local networks and the service itself. A dedicated line does not mean every part of the path is fixed.

Best for: Extended work sessions, remote meetings, and tasks that are sensitive to connection fluctuations. Focus on whether the task works reliably over time, not just on the route name. For video calls, also check your local upload capacity and Wi-Fi conditions; changing routes cannot replace these basic checks.

Cost considerations: Dedicated capacity generally involves higher procurement and maintenance costs, and resource planning depends more on fixed links. This is a general difference in network topology; it does not mean VPNDP charges extra for this route type or guarantees exclusive capacity. Check your subscription for available routes.

RELAY

Relay route

Access → relay node → exit

A relay route adds a forwarding step between the client and the destination exit. The client connects first to an accessible entry point, which then forwards traffic along the next leg. An extra hop does not necessarily mean a slower connection: avoiding a congested or indirect public-internet route can improve the overall experience. A congested relay segment, however, can affect performance.

Best for: Everyday browsing, international productivity apps, and use across websites in different regions. If a direct connection to an exit is unstable, try a relay route in the same region to compare paths without changing the exit location. Keep the app and local network the same during the comparison, and avoid changing several settings at once.

Cost considerations: Relays require additional forwarding capacity, traffic handling, and path maintenance. Costs depend on how the entry and exit are connected. A relay is not another name for a dedicated line or a universal performance tier. Check the full route label so you do not mistake the entry location for the final exit.

DIRECT

Direct route

Access → public internet route → exit

A direct route generally connects the client to the selected exit without a dedicated relay entry. Its path is relatively straightforward, but the actual public internet route depends on network interconnection. Direct does not mean a geographically straight path, nor does a nearby location guarantee better performance. Different local ISPs can get different results when connecting to the same exit.

Best for: Browsing, research, and general app use when routes from your local network to the destination region are working well. Use direct as a baseline, then compare it with other route types in the same region. If only one website is slow while other services work normally, the issue may be beyond the exit rather than with the entire route.

Cost considerations: Direct routes generally avoid the resource costs of a dedicated relay hop, but exit capacity and public internet interconnection still have costs. A simpler path does not mean lower quality or guaranteed lower data usage. Check the usage records in your account panel rather than inferring traffic use from the route name.

SELECTION

Choose an exit for your needs

First identify the region your app needs, then check whether the connection is stable. Different use cases call for different criteria, and not every app needs to use the same exit.

Everyday browsing

For research, reading, and international websites, start with a nearby region that is available in your client. Check whether page text, images, and attachments load—not just whether the homepage opens. A website may fetch content from multiple regions, so one image failing to load does not necessarily mean the entire exit is unavailable.

If your everyday sites span several regions, keep a reliable exit for regular use and set up an alternative route in the same region. If something goes wrong, retry the page before switching routes. This helps distinguish a temporary request failure from a persistent connection issue.

Streaming

For streaming, first match the release region of the content you want to watch, then check your account plan, the platform’s service availability, and its licensing rules. A route name that includes a region does not mean every title from that region will be available. Platforms may also use exit location, account settings, and session history to determine your location.

After connecting, open the specific title and try playback, then check video quality and whether playback stays smooth. If only some titles are missing, check the regional catalog first; if playback fails across the board, compare other exits in the same region. After switching routes, reopen the app so it starts a fresh connection through the new exit and an old session does not skew the result.

AI Tools

When using tools such as ChatGPT, Claude, and Gemini, first check the regions and account requirements supported by each platform. Network access is only one part of the picture: account permissions, product availability, and service status can all affect sign-in or feature access. Not every error points to a route problem.

Test chat generation, file uploads, and downloads separately. If the site opens but uploads keep failing, check file requirements and client routing before trying another route in the same region. For regular use, stick to one exit region where possible to reduce extra verification caused by switching during a session. For more use cases, see the AI guide.

Gaming

Start with the region of the game server, not just your account region or store page. Sign-in, updates, and gameplay may connect to different services, so one exit may not suit every step. A network acceleration subscription does not override the game publisher’s requirements for clients, accounts, or regions.

Judge the connection by in-game responsiveness and stability. If downloads work but gameplay does not, check whether your client supports the game’s required transport method and whether the routing rules cover the relevant process. Switch routes after leaving the match to avoid disrupting an active connection or your current progress.

Remote work

For work, start with your company’s regional access requirements and policies. Remote desktops, video calls, code repositories, and document collaboration have different network needs: calls depend on consistent upstream and downstream traffic, repository tasks may be affected by large files and long-lived connections, and web documents require careful checks of save and sync status.

Before starting important work, test sign-in, file transfers, and collaborative saving. Company security software and personal clients may both change routing; follow your company’s IT policies if they conflict. VPNDP allows unlimited devices online at once, but check the client status on each device. A successful connection on one device does not confirm that the others are configured.

CHECKLIST

A post-connection verification checklist

Keep test conditions consistent and change only one variable at a time. Identifying whether the issue lies with local access, the route, or the destination app is more effective than switching every setting in succession.

Check your subscription and exit

First check your plan status in the account panel, then update the subscription in your client. Select a route from the current list, confirm the connection, and check that the exit region is what you expect. A connected status does not guarantee that a specific app is using that route; check whether the app is being routed through your local connection instead.

Test with a real task

Verify the connection with the task you actually need to do: open page text and attachments when browsing, play a title when streaming, confirm files save when working, and check that AI tools accept prompts and return complete results. Do not rely only on the client’s connection indicator, or generalize from one website’s issue to every app.

Compare routes, then report the issue

If something goes wrong, compare other route types in the same region before changing regions. Note your local network, route name, app message, and steps to reproduce the issue, then report it through the account panel ticket system. Never send your password or full subscription link, and redact sensitive account details from screenshots.

View plans Get the client app › Get connection help ›