Route overview

Global route and server coverage

VPNWing covers 120+ countries and 160+ routes, grouped by access type into IEPL, relay and direct. This page first lists route samples by region, then explains how each type works, what it costs and where it fits, and closes with a picking order by use case.

Start Free View Plans
  • IEPL
  • Relay
  • Direct
  • Unlimited devices
  • 30-day money-back guarantee
120+Countries
160+Routes
UnlimitedDevices online at once
30 daysMoney-back guarantee

Route list

Routes grouped by region

The table below lists route samples in four groups — Asia-Pacific, North America, Europe and Other — with columns for country/region, city, route type and streaming support. Route type maps to the three access methods. In the streaming column, “Supported” means the route opens mainstream streaming platforms normally; “Partial” means the platform opens but some regional catalogues need another route in the same region.

Country / region City Route type Streaming
Asia-Pacific
Japan Tokyo IEPL Supported
Japan Osaka Relay Supported
Hong Kong Hong Kong IEPL Supported
Hong Kong Tsuen Wan Relay Supported
Singapore Singapore IEPL Supported
South Korea Seoul Relay Supported
Taiwan Taipei Direct Supported
Malaysia Kuala Lumpur Direct Supported
Thailand Bangkok Direct Partial
Australia Sydney Relay Supported
India Mumbai Relay Partial
North America
United States Los Angeles IEPL Supported
United States San Jose Relay Supported
United States Seattle Relay Supported
United States New York Relay Supported
United States Dallas Direct Partial
Canada Toronto Relay Supported
Canada Vancouver Direct Supported
Europe
United Kingdom London IEPL Supported
Germany Frankfurt IEPL Supported
Netherlands Amsterdam Relay Supported
France Paris Relay Supported
Switzerland Zurich Relay Supported
Sweden Stockholm Direct Supported
Spain Madrid Direct Partial
Italy Milan Direct Partial
Poland Warsaw Direct Partial
Other
United Arab Emirates Dubai Relay Supported
Turkey Istanbul Direct Partial
Brazil São Paulo Relay Supported
South Africa Johannesburg Direct Supported
Mexico Mexico City Direct Partial

The table shows samples only. The full list opens by region on the Routes page in the client, and a single city usually has several routes on different access types to switch between. Overall coverage is 120+ countries and 160+ routes.

Route type

How the three route types differ

Two routes can both be called “Japan” and still behave very differently at peak hours depending on whether traffic rides an IEPL, is forwarded through a relay, or leaves locally. Each type has its own path structure, unit cost and best use, explained below.

01

IEPL

Dedicated path

IEPL is an international Ethernet private line: the carrier provides a dedicated Layer 2 path between the two ends, so traffic never shares a queue with other public internet flows. Packets enter the private line at the local entry and go straight to the peer node without crossing congested public backbone segments, which keeps the path fixed, jitter low and packet loss minimal. For long-lived tasks such as video calls, 4K playback and large uploads, this feels closest to a local network.

Private line capacity is billed as dedicated bandwidth, so the unit cost runs higher than relay or direct routes — which is why IEPL is concentrated in the busiest regions: Tokyo, Hong Kong, Singapore, Los Angeles, London and Frankfurt. When you need steady access to international sites, pick a private line in one of those regions first; paired with the same military-grade encryption used site-wide, both ends of the link stay encrypted.

  • Video calls
  • 4K playback
  • Long connections
  • Higher cost
02

Relay

Backbone forwarding

A relay route takes traffic at a local entry node and forwards it across the backbone to an exit node. The entry-to-exit leg runs on an optimised backbone path, so there is less detouring on the cross-border segment and shorter queuing at peak hours than on a direct route. Users notice two things: pages render faster, and long transfers are less likely to collapse in speed.

A relay needs a node at each end plus the capacity to forward traffic, so its unit cost sits between private line and direct. That is why relay routes are the most numerous and cover the widest set of cities. When one route congests, there is usually one or two other relays in the same region to switch to — which is why relay makes a sensible default.

  • Everyday browsing
  • Streaming
  • AI Tools
  • Mid-range cost
03

Direct

Local exit

A direct route is a local exit: traffic leaves the internet from a node in your region, the simplest structure with the lowest single-hop latency. The trade-off is that the cross-border segment still runs over the public internet, so peak-hour queuing and speed swings are possible. For nearby access, downloads and backups — tasks that mostly need bandwidth — direct is usually enough.

Direct nodes are the cheapest to deploy and cover the most cities, which makes them good nearby exits and backup routes. For competitive gaming, start with a direct node on the same continent and switch to relay or private line based on how it actually performs. No route type is inherently better — only better matched to the task.

  • Nearby access
  • Downloads and backups
  • Competitive gaming
  • Lowest cost

Route picks

Picking a route by use case

Below are picks for five common use cases, in priority order: try the first choice, and fall back to the second when it congests. Switching routes does not affect your account or plan — you can change routes in the client at any time.

Everyday browsing and search

Page loads care about latency, not bandwidth. Relay routes in Hong Kong and Tokyo have the shortest path and render fastest; for heavy sites, move to a private line in the same region. If one site loads slowly, switch to another route in the same region first, then judge whether the route itself is the problem.

  • Relay first
  • Same-region switch

Streaming and 4K playback

4K playback needs a link that keeps dropping no packets so the bitrate can hold at the top tier. Private lines in Tokyo, Los Angeles and London are the first choice; the catalogue region is set by the exit, so when you need a different region, switch to another route in the same region rather than another country — a new country usually means signing in again, a new route does not.

  • IEPL
  • Same-region switch

AI tools and long conversations

A single answer from a generative tool is often a long connection lasting tens of seconds, and a mid-stream break means starting over. Private lines in Tokyo, Singapore and Los Angeles hold long connections better; use one when uploading long documents to avoid retransmission. For short day-to-day questions, relay is fine.

  • Long connections
  • Private line first

Gaming and real-time matches

Competitive titles are most sensitive to single-hop latency, and physical distance sets the floor. Choose a direct node on the same continent; for cross-region matches a relay is steadier than direct, but the latency floor is still set by distance — a farther exit will not be faster.

  • Direct and nearby
  • Same continent

Remote work and meetings

Video calls are the most sensitive to packet loss — even slight loss turns the picture into blocks. Switch to a private line before the meeting and stay on it; move file sync and backups to a relay route so they do not compete for the same path.

  • IEPL
  • Lock in before meetings

Coverage

Regions and cities covered

Beyond the samples, many more cities are available in the client. Overall coverage is 120+ countries and 160+ routes; below are the common entry regions, and you can browse the cities and route types inside each region in the client.

  • Japan
  • Hong Kong
  • Singapore
  • South Korea
  • Taiwan
  • Malaysia
  • Thailand
  • Australia
  • India
  • United States
  • Canada
  • Mexico
  • United Kingdom
  • Germany
  • Netherlands
  • France
  • Switzerland
  • Sweden
  • Spain
  • Italy
  • Poland
  • United Arab Emirates
  • Turkey
  • Brazil
  • South Africa

How to get access

Routes come with your plan

Routes are not sold separately — any monthly subscription unlocks every route and every region. The three plans differ only in monthly data; routes, regions and simultaneous devices are identical.

Monthly · 60GB

¥9.9/ month

60GB / month

  • 120+ countries / 160+ routes
  • Unlimited simultaneous devices
  • 30-day money-back guarantee
Get Started

Data resets monthly on your activation date

Best value

Monthly · 250GB

¥18/ month

250GB / month

  • 120+ countries / 160+ routes
  • Unlimited simultaneous devices
  • 30-day money-back guarantee
Choose This Plan

Data resets monthly on your activation date

Monthly · 500GB

¥28/ month

500GB / month

  • 120+ countries / 160+ routes
  • Unlimited simultaneous devices
  • 30-day money-back guarantee
Get Started

Data resets monthly on your activation date

Data packs stack with your plan: ¥158/300GB, ¥358/1000GB and ¥658/3000GB, valid until used up, never expiring. Plan data resets monthly on your activation date, and mid-cycle upgrades are prorated by remaining days. 30-day money-back guarantee; sign-up needs only a username and password, no email address; payment via Alipay / WeChat Pay / USDT.

FAQ

Route FAQ

Six questions on choosing routes, exit addresses, data and refunds.

  • Can I connect to every city in the table?

    The table lists route samples that show the regional spread and route types. The full list opens by region on the Routes page in the client, and a city usually has one or more routes on different access types — test them one by one to find the steadiest for the current hour.

  • IEPL or relay — which should I pick?

    Start with the task. Meetings, 4K playback and long document uploads need a stable connection over time, so go private line first; everyday browsing, streaming and AI tools are fine on relay, and you can move to a private line when one congests. Private lines are fewer and concentrated in Tokyo, Hong Kong, Singapore, Los Angeles, London and Frankfurt.

  • A site still will not open after switching routes — what now?

    Retry on another route in the same region first, then disconnect and reconnect once so the client performs a fresh handshake. If that fails, clear the local DNS cache or set the client's DNS to resolve through the route. Most cases are a path problem between the route and the target site, and another route in the same region fixes it.

  • How many devices can share one route?

    Unlimited simultaneous devices. One account can sign in on Windows / macOS / iOS / Android / Linux at the same time — no separate purchase for a second device, and no need to pick different routes per device.

  • Does the exit address change?

    The exit address is assigned by the node and may change after a reconnect or a route switch. Where you need a stable exit — login allowlists, backend bindings — pin a single route in the client and switch as little as possible.

  • What happens when data runs out, and how are refunds handled?

    Plan data resets monthly on your activation date. When the month's data runs out you can buy a data pack and keep going — ¥158/300GB, ¥358/1000GB, ¥658/3000GB, valid until used up, never expiring — or upgrade to a higher plan, with the difference prorated by remaining days. A no-questions refund can be requested within 30 days of your first payment by opening a ticket in the user panel.