Route directory / Choose an exit

Global server locations

VPNNear covers 120+ countries / 240+ routes. When choosing a location, first identify the exit region your target service requires, then compare route types based on how you plan to use the connection.

Browse routes by region

This table is a static index, not a list of currently available servers. For cities, route types, and streaming support not listed here, refer to the route list and labels in the client.

Regional index and example routes
Country or region City Route type Streaming support
Asia-Pacific
SingaporeSee clientSee clientRefer to the client labels
JapanSee clientSee clientRefer to the client labels
Hong Kong, ChinaHong KongIEPL routeRefer to the client labels
North America
United StatesSee clientSee clientRefer to the client labels
Europe
SwitzerlandSee clientSee clientRefer to the client labels
Other
See the route list in the client for other countries and regions.

The exit region is one selection criterion, not a ranking of connection quality. Even when several routes are available in the same region, check each route's type and usage labels. To confirm your current exit, open My IP before and after connecting and compare the exit address and its registered location. You’ll still need to verify access within the target service itself.

Traffic routing

IEPL, relay, and direct routes

Route type describes how traffic reaches the exit. It does not indicate a service tier, and the name alone cannot predict how a route will perform on your network.

Dedicated cross-border segment

IEPL route

IEPL stands for International Ethernet Private Line. In a subscription route, it provides the cross-border link between the entry point and the exit. Your device still connects to the entry point over its own network, and traffic travels over the exit's network after leaving it. So a dedicated line won't necessarily fix congestion on your home network or slow responses from the target service.

Consider this type of route if you regularly attend meetings at set times, submit online documents, or need to maintain long-running sessions. Check for frequent disconnects and whether you need to log in again after a session reconnects; don't just check whether the homepage loads. Dedicated routes typically require separate capacity planning and line leases, so setup and ongoing costs are often higher than for routes using the public internet.

Separate entry and exit

Relay routes

Your device connects to a relay entry point first, which then forwards traffic to an exit in the target region. The entry can be near your access network, while the exit is chosen to match the target service's regional requirements. The entry location does not indicate the final exit location. If you need a specific region, check the exit label in the client rather than inferring it from the entry name.

A relay can be worth trying when you need to keep the same exit region but want to test a different access path. If a direct route in that region often disconnects, keep the exit region the same and try a relay while repeating the same tasks. Relays require additional maintenance for the entry point, forwarding link, and exit, adding another potential point of congestion. Costs depend on how the relay segment is deployed and procured; more hops do not automatically mean higher costs.

Direct access to the exit

Direct routes

A direct route connects your device to the exit over the existing internet path, without an additional service-side relay entry. Internet traffic still passes through carrier routers and interconnected networks, so there isn't just one physical link between your device and the exit. Two locations that appear close on a map don't necessarily have a shorter actual route.

For everyday browsing, occasional research, or when you don't need a specific exit region, start by testing a direct route. Direct routes skip a separate relay, which generally lowers deployment costs, but performance depends more on the public internet path from your local carrier to the exit. If it works well during the day but keeps dropping at night, test another route type in the same region during the hours when the problem occurs.

Here, cost refers to the cost of building and operating a route, not the retail price of an individual route. Subscription prices and data terms are listed on the Plans & Pricing page.

How to choose a route

Choose an exit for your needs

Change one variable at a time: hold the region constant while comparing route types, then hold the route type constant while comparing regions. Retest with tasks you actually do to avoid mistaking cached pages, local network fluctuations, or account issues for route differences.

Everyday browsing: check that pages and attachments load fully

If you don't need a specific region, start with a direct route in a nearby region. Visit a site you use often, open a page with plenty of text and images, then download a commonly used attachment. Checking only the homepage can be misleading because of browser caching: a visible homepage doesn't mean its images, scripts, and attachments will all load correctly. If the same site gets stuck at the same point on different routes, first check browser extensions, your login status, and your local connection instead of repeatedly switching exits.

Streaming: check the region, then test playback

Choose an exit based on the platform's service regions and account rules, then check whether the client labels the route as supporting that streaming service. A matching region doesn't guarantee that a particular title will be available; the catalog may also vary by account and licensing. After connecting, open the title through the usual route and test playback, seeking, and uninterrupted viewing. If you can sign in but a specific title is unavailable, check its licensing first. If the catalog loads but playback keeps buffering, compare another route in the same region with the relevant support label.

AI tools: test a complete session from the same exit

First, check the tool's regional and account requirements. After connecting, don't stop at the sign-in page: run a session, check that the response finishes, and test any file uploads or page switching you rely on. An interrupted response and an account notice are different issues: try another route in the same region for the former, and check the reason provided by the tool for the latter. For long sessions or file transfers, wait for the current task to finish before switching exits so you don't mistake a switch-related interruption for a route failure.

Gaming: check the server region and actual gameplay

First, confirm the game's server region and matchmaking area, then choose an exit for that region. Login, matchmaking, and gameplay may use different services, so reaching the lobby doesn't guarantee a consistent experience throughout a match. Test in training mode or a casual match, checking for character rubber-banding, voice chat dropouts, and reconnects before deciding whether to keep the route. If changing exits affects the server region or matchmaking pool, check your game settings and account region first; don't confuse region assignment with connection instability.

Work: prioritize stable, approved exits

Follow your organization's access rules first. If your company's systems require a designated network or registered exit, don't change it yourself. If subscription routes are allowed, test sign-in, document syncing, and video calls during your usual work hours in advance. Pay particular attention to audio dropouts during screen sharing and whether large files upload successfully. Keep a tested route in the same region as a backup. During an important meeting or file upload, don't switch routes unless the current task has already been interrupted.

After switching routes: check the exit separately from the service

First, use My IP to check your browser's current exit, then return to the target app and test the key action. A new exit shown in your browser doesn't mean every app uses the same route. If an app behaves differently, check its connection settings and the client's split-tunneling rules. If the registered location doesn't match your expectations, first confirm whether the client is showing the entry or the exit, and keep in mind that location data can vary between lookup services.

If you still need help troubleshooting, note the route name, when the issue occurred, your access network, and the step that failed, then visit the Support Center. “Sign-in worked, but the upload failed” is more useful than “can't connect.” Before sharing a screenshot, hide account details and your subscription URL.