VPN Server Locations - VPNOh | 100+ Countries, 170+ Routes and Route Guide

Asia-Pacific routes

Asia-Pacific is where cross-border access demand is most concentrated. Hong Kong and Tokyo run on IEPL dedicated lines, so the cross-border leg never detours through the public internet — a good fit for long work sessions and 4K streaming. Singapore is also a dedicated line and covers Southeast Asia. Seoul and Jakarta are relay routes with steady performance at peak hours. Kuala Lumpur, Bangkok, Ho Chi Minh City and Mumbai are direct routes, well suited to reaching local services in Southeast and South Asia.

Asia-Pacific server locations
Country/Region	City	Route type	Streaming
Hong Kong	Hong Kong	IEPL dedicated line	Streaming optimized
Japan	Tokyo	IEPL dedicated line	Streaming optimized
Japan	Osaka	Relay route	—
Singapore	Singapore	IEPL dedicated line	Streaming optimized
South Korea	Seoul	Relay route	Streaming optimized
Indonesia	Jakarta	Relay route	—
Malaysia	Kuala Lumpur	Direct route	—
Thailand	Bangkok	Direct route	—
Vietnam	Ho Chi Minh City	Direct route	—
India	Mumbai	Direct route	—

North America routes

North America is anchored on the US West Coast. Los Angeles is an IEPL dedicated line and carries most of the trans-Pacific traffic; San Jose is a relay route with streaming optimization, a good fit for US-region content; New York covers the Eastern time zone, useful for cross-time-zone collaboration and following US market hours. Canada has two routes, in Toronto and Vancouver: Toronto is a relay with streaming optimization, Vancouver is direct. Mexico City is a direct route serving northern Latin America.

North America server locations
Country/Region	City	Route type	Streaming
United States	Los Angeles	IEPL dedicated line	Streaming optimized
United States	San Jose	Relay route	Streaming optimized
United States	New York	Relay route	—
Canada	Toronto	Relay route	Streaming optimized
Canada	Vancouver	Direct route	—
Mexico	Mexico City	Direct route	—

Europe routes

Europe's routes cluster around three network hubs: Frankfurt, London and Amsterdam. London is a relay route with streaming optimization, suited to UK-region content; Frankfurt and Amsterdam are relays covering Central and Western Europe; Paris, Madrid and Warsaw are direct routes, good for reaching local services or working from Europe. Combining European and Asia-Pacific nodes covers most cross-time-zone collaboration scenarios.

Europe server locations
Country/Region	City	Route type	Streaming
United Kingdom	London	Relay route	Streaming optimized
Germany	Frankfurt	Relay route	—
France	Paris	Direct route	—
Netherlands	Amsterdam	Relay route	—
Spain	Madrid	Direct route	—
Poland	Warsaw	Direct route	—

Other regions

Sydney is a relay route covering Oceania; Dubai is direct, serving the Middle East; São Paulo and Johannesburg cover South America and Africa respectively, both direct routes. These regions are mainly used for reaching local services and for cross-region collaboration.

Other regions server locations
Country/Region	City	Route type	Streaming
Australia	Sydney	Relay route	—
United Arab Emirates	Dubai	Direct route	—
Brazil	São Paulo	Direct route	—
South Africa	Johannesburg	Direct route	—

Route types explained

VPNOh routes fall into three types: IEPL dedicated lines that build a fixed channel between the two ends of the cross-border path, relay routes that travel an optimized relay path, and direct routes that land on a local exit. The three differ in cross-border path, stability and relative cost, so simply match the type to your use case.

IEPL dedicated line

IEPL is an international Ethernet private line: it builds a point-to-point Layer 2 channel between the two ends of the cross-border path, and traffic travels a fixed path straight through, without the default-route detours of the public internet. The direct benefit of a fixed path is that it does not fluctuate with public-internet congestion at peak hours, which suits connections that need to stay up for a long time. Private lines are billed by bandwidth and distance, making them the most expensive of the three types, so they are deployed only in core regions such as Hong Kong, Tokyo, Singapore and Los Angeles.

Best for: Remote work, video calls, 4K streaming, large cross-border file transfers
Stability: Fixed path, little fluctuation at peak hours
Relative cost: Highest of the three

Relay route

A relay route travels an optimized relay path between an entry node and an exit node: the client connects to the nearest entry point first, the cross-border leg avoids congested default routes on the public internet, and traffic exits through a local exit. Compared with direct routes, a relay adds one hop, but the cross-border path quality is more controllable; compared with dedicated lines, it costs less and can be rolled out across more countries. Relays are the largest group of routes and suit everyday browsing, AI tools, streaming and gaming.

Best for: Everyday browsing, AI tools, streaming, gaming
Stability: Controllable cross-border path, steady overall
Relative cost: Moderate

Direct route

A direct route connects the client straight to a local exit node with no extra relay, giving the shortest path. Its real-world performance depends mainly on the link quality from your local network to that node: when the link is clean, the path is the shortest one available; when the link itself is congested, there is no extra room for optimization. Direct routes suit reaching local services, landing close to home, and filling in long-tail country coverage.

Best for: Local services, nearby exits, long-tail country coverage
Stability: Depends on your local link to the node
Relative cost: Lowest of the three

Comparing the three route types
Route type	Cross-border path	Stability	Best for	Relative cost
IEPL dedicated line	Point-to-point Layer 2 channel, no public-internet detours	Fixed path, little fluctuation at peak hours	Remote work, 4K streaming, large file transfers	Highest
Relay route	Nearby entry + optimized relay + local exit	Controllable cross-border path	Everyday browsing, AI tools, streaming, gaming	Moderate
Direct route	Client connects straight to a local exit	Depends on the local link	Local services, nearby exits, long-tail coverage	Lowest

Choosing a route by use case

No route is inherently better; what matters is whether it matches your use. Below are picks for five common use cases — start with the quick-reference table, then read the notes for each.

Route quick reference by use case
Use case	Preferred route type	Recommended regions
Everyday browsing	Relay / Direct	The region closest to you
Streaming	IEPL dedicated line / Relay	Regions marked as streaming-optimized
AI Tools	Relay / IEPL dedicated line	US West Coast, Japan, Singapore
Gaming	Direct / IEPL dedicated line	The nearest entry node
Work	IEPL dedicated line	Hong Kong, Tokyo, Frankfurt

Everyday browsing

Pages, news and social media do not demand much peak bandwidth, but they are sensitive to how fast a connection is established. Prefer the entry node closest to you — relay or direct both work, and there is no need to pick a distant node on purpose. With several devices online at once, keep your main device on a relay node and put the occasional ones on direct nodes for a more balanced experience overall.

Streaming

4K streaming tests both bandwidth and stability. Prefer the regions marked as streaming-optimized in the table — those have landing optimizations for streaming CDNs. Play 4K on only one device at a time and let the others use 1080p, so a single route does not get saturated. If playback starts buffering, switch to another route in the same region first, then consider changing regions.

AI Tools

AI tools care more about route stability than peak bandwidth — a dropped connection loses the session you were generating. It is best to stay on one relay or dedicated-line node rather than switching exit regions often; if a region keeps dropping when you reach AI services, switch to another route within the same region first, and only then move to the US West Coast, Japan or Singapore.

Gaming

Gaming is about round-trip latency and jitter, not bandwidth. Prefer the nearest entry node and avoid sharing that route with other devices running downloads or 4K playback. Direct routes have the shortest path and are usually the better fit for gaming; if your local link to the entry node is itself unstable, switch to a dedicated line or relay. After switching, play for a few minutes before judging — a single login's momentary performance is not enough to go on.

Work

Video calls, code repository sync and internal system access all need long, stable connections. Prefer IEPL dedicated lines: the path is fixed and does not fluctuate with public-internet congestion at peak hours. For long meetings, keep the device running the meeting app on a dedicated-line node and let other devices browse over a relay node. That is what unlimited simultaneous devices is for — each device can pick a route that matches its own use.

Route FAQ

What does the streaming-optimized label mean?

It means that region has landing optimizations for streaming CDNs, so playback is more likely to hit a nearby streaming node. Regions without the label still work for streaming — they just do not have that extra optimization. The label is only a hint when choosing a route; real-world performance still depends on your local network and the time of day.

Where can I see the actual latency and speed of each route?

Measure it in the client. Latency and bandwidth vary with your local network, ISP and time of day, and the same node performs very differently for different users — fixed numbers would have no reference value, so this page only lists static coverage facts: region, route type and streaming-optimization labels.

How many routes can one account use at the same time?

Unlimited simultaneous devices — each device picks its own route, with no separate purchase per device. A single device can only connect to one route at a time; multiple devices can connect to nodes in different regions.

What if the region I want is not in the list above?

This page lists representative cities for each region; actual coverage is 100+ countries / 170+ routes, and the full list is visible after you sign in to the client. If a region you use often really is not included, you can submit a ticket from the user panel — route adjustments take this kind of feedback into account.

Route coverage and route types are as listed on this page; for pricing, refunds and how to get started, see the plans page and the FAQ page.

Global server coverage