NETWORK · Route Components Index

Global servers and routes

120+ countries / 220+ routes. Choose an exit region, then compare route types.

Your region determines the exit location, while the route affects connection performance. This page offers static route examples and selection tips; actual options depend on your dashboard and subscription.

First Month Free View Plans
Coverage
120+ countries / 220+ routes
Connected devices
Unlimited devices
Account access
No email address required

REGION · EXIT

Browse routes by region

Go to dashboard

The countries or regions, cities, and route types below illustrate how to read a server list. They are not a complete inventory, and not every combination is always available. A city in a route name indicates the exit location; it does not guarantee the shortest path to a destination. After importing your subscription, start with the options shown in your client and test them with the apps you use.

Streaming availability depends on the platform, account region, and current exit checks, so all entries are labeled “Check with the platform.” A region name is not a promise of catalog access or playback quality. On narrow screens, scroll the table horizontally to see all columns.

Static route examples · See your dashboard and subscription for available routes
Country or region City Route type Streaming availability
ASIA PACIFIC
Hong Kong, ChinaHong KongIEPL dedicated lineCheck with the platform
SingaporeSingaporeRelay routeCheck with the platform
JapanTokyoDirect routeCheck with the platform
JapanOsakaRelay routeCheck with the platform
South KoreaSeoulDirect routeCheck with the platform
AustraliaSydneyRelay routeCheck with the platform
NORTH AMERICA
United StatesLos AngelesRelay routeCheck with the platform
United StatesSeattleDirect routeCheck with the platform
United StatesNew YorkRelay routeCheck with the platform
CanadaTorontoDirect routeCheck with the platform
EUROPE
United KingdomLondonRelay routeCheck with the platform
GermanyFrankfurtDirect routeCheck with the platform
FranceParisRelay routeCheck with the platform
NetherlandsAmsterdamDirect routeCheck with the platform
SwitzerlandZurichRelay routeCheck with the platform
ItalyMilanDirect routeCheck with the platform
OTHER REGIONS
BrazilSão PauloRelay routeCheck with the platform
South AfricaJohannesburgDirect routeCheck with the platform
United Arab EmiratesDubaiRelay routeCheck with the platform
IndiaMumbaiDirect routeCheck with the platform

LINE · PATH

Route types and path differences

IEPL, relay, and direct describe how a route is structured, not a feature or performance tier. The same exit region can use different entry points and transmission paths. Routes labeled as relays can also perform differently depending on your local carrier and time of day. For a fair comparison, keep the app, device, and local network the same and change only the route.

LINE · IEPL

IEPL dedicated line

IEPL generally refers to a transmission link built around a dedicated Ethernet circuit. In a route setup, dedicated resources are used for a key transmission segment alongside the entry, exit, and internet access segments. This can reduce reliance on changes in some public internet paths; it does not make every connection between your device and the destination a private network. Your local Wi-Fi, access point, and destination site can still affect performance.

These resources typically involve higher setup and maintenance costs, and may suit office work, remote collaboration, or long interactive sessions where a steady connection matters. When choosing a route, check session continuity, whether file transfers complete, and how it performs at your usual times. A dedicated-line label does not mean the resources are exclusive or that every app will be faster. VPNPart does not make unverified performance claims.

Route overview Local connection → Entry point → Dedicated transmission segment → Exit → Destination service

LINE · TRANSIT

Relay route

A relay route sends traffic to an entry point first, then forwards it along an intermediate path to the exit. Entry and exit points can handle access and destination traffic separately, so cross-border access does not have to rely entirely on a direct path from your local network to the exit. A relay adds a forwarding step, but when the route suits your network, it may provide a more consistent experience than a direct connection.

Relay routes require entry, forwarding, and ongoing maintenance resources. Their cost structure is usually more complex than a simple direct connection, though the name alone does not determine the actual cost. They may suit everyday browsing, video, and file transfers. If you experience occasional pauses, compare different paths within the same region first. Changing countries without considering the entry point may not help identify the issue.

Route overview Local connection → Relay entry point → Forwarding path → Exit → Destination service

LINE · DIRECT

Direct route

A direct route generally means the client connects to the exit server through your local network, without using a designated relay entry point. “Direct” describes the logical connection, not a physical route free of network equipment. Traffic still travels across carrier networks, and routing can vary by region and time of day, so a nearby location does not necessarily offer better performance.

Direct routes generally require fewer dedicated relay resources and have a simpler setup, but public internet access still needs to be maintained. They may suit browsing, downloads, or backup connections when the path from your local network to the region works well. If performance is inconsistent during your usual hours, compare relay or IEPL routes in the same region rather than relying on the order of entries in your client.

Route overview Local connection → Public internet path → Exit → Destination service

PURPOSE · SELECTION

Choose an egress for your needs

Start by asking what you need to access, then decide which route to use. Browsing, video playback, and maintaining a remote session place different demands on a connection. A successful client connection only confirms that the basic connection is established; it does not verify that an app works. Save routes you have tested and keep alternatives with different paths.

WEB · BROWSING

Everyday browsing: check the full page load

For everyday browsing, start with a nearby exit that meets the destination site’s regional requirements. After opening a familiar page, check that images, search results, sign-in pages, and attachments also load correctly. If the homepage opens but some content is missing, split-tunneling rules or DNS resolution may be involved; the route itself may still be working.

When comparing routes, use the same browser and page, and keep your local network as consistent as possible. Avoid changing the client mode, exit, and DNS settings all at once, or it will be hard to tell what improved the experience. If only one site has issues, read the troubleshooting guide before switching regions.

MEDIA · PLAYBACK

Streaming: verify access, then check playback

For streaming, first choose an exit that meets the region requirements for your account and the content you want to watch, then check sign-in, the catalog, and playback. Seeing a title in the catalog does not guarantee it will play, and successful playback does not guarantee a consistent picture quality. Platform checks, account entitlements, device capabilities, and your local network all affect the result.

Once playback starts, check sustained viewing and seeking—not just whether the artwork appears. If you see a region warning, note its exact wording and compare other exits in the same region. Avoid switching regions repeatedly during playback, as changes to the session can be mistaken for route problems. See streaming access support for more information.

AI · SESSION

AI tools: keep your exit and session consistent

Before using an AI tool, check the service’s regional eligibility and account rules. Choose an eligible exit, then test the web interface, desktop app, or command-line tool separately; they may not use the same proxy settings. If the website works but the command-line tool cannot connect, check the proxy configuration in its environment first.

Long responses, file uploads, and ongoing interactions make session continuity especially important. Keep the same exit during a task and avoid unnecessary region changes. If an issue occurs only in a particular editor or plugin, save the error message and distinguish an authentication error from a network interruption. See AI tool access guide for more help; not every error is caused by a server.

GAME · CONNECTION

Gaming: distinguish downloads from gameplay

Game downloads and real-time gameplay are different tasks. Downloads depend more on sustained transfers, while gameplay needs responsive interactions and a stable path. A general subscription route is not a dedicated service optimized for a specific game, so the exit city alone cannot tell you whether it will suit gameplay.

Before you start, check that the client is routing the game’s traffic and follow the game’s region and account rules. Test against the same server region and check whether you can join, maintain a session, and avoid unexpected disconnects. If game traffic is not using the proxy route, changing servers will not change the result; check the app rules first.

WORK · CONTINUITY

Work: prioritize continuity and recovery

For remote work, test meetings, code repositories, cloud documents, and file transfers separately. Joining a meeting does not guarantee smooth screen sharing, and browsing a code repository does not guarantee that a push will complete. Prefer paths that perform consistently during your usual work hours, and keep a tested alternative for important sessions.

VPNPart supports unlimited devices and can be configured on Windows, macOS, iOS, Android, and Linux. Multiple devices still share the traffic allowance for the relevant plan; each device does not get a separate allowance. For company devices, follow your organization’s network policies. If an enterprise access policy blocks a connection, check with the appropriate administrator.

CHECK · BEFORE SWITCHING

What to verify after connecting

Confirm your subscription, then test your apps

Log in to the user dashboard to get your subscription, then import it into your client. After updating the subscription, confirm that your chosen route is still listed and check your plan status and remaining traffic. Do not post subscription links in public forums or send others screenshots showing your full configuration and subscription details. For initial setup, follow the setup guide.

Once the client is connected, use My IP to check your browser’s current exit information. If the exit is as expected, open the app you want to use. Checking your browser’s exit does not prove that every app uses the same route; verify split-tunneling rules, in-app settings, and which apps are covered by the system proxy separately.

If something goes wrong, keep conditions comparable

First confirm that your local network can access commonly used services, then compare other routes in the same region. If the issue still affects only one app after switching, check its error message and routing rules. If several apps are affected, compare different route types and note the time, local network type, client platform, and route name.

If you need help, submit the details above through a dashboard support ticket, with a screenshot of the error after obscuring sensitive details. Remove passwords, subscription links, and sensitive account information. A clear description of the app and action that failed is more useful than simply saying “the route isn’t working.”

Start Free