Route directory

Server locations
Browse by region

BiliVPN provides cross-border network acceleration across 90+ countries / 200+ routes. Browse common exits by region, with notes on IEPL, transit and direct connections to help match a route to the location of your target service.

First Month Free View Plans
  • 90+ countries
  • 200+ routes
  • Unlimited devices

CATALOG SCOPE

How to read the coverage and directory

The route table shows the region, city, connection type and streaming compatibility. A city indicates the network exit region, not the visitor’s physical location. The route type describes how traffic enters the international link from the local network. Actual results also depend on the destination region, local carrier, time of day and the platform’s own location checks, so route selection should not rely on distance alone.

“Streaming supported” means the route can be used for common viewing scenarios, but libraries, account regions and platform policies may change. If a platform reassesses the region, disconnect, switch to another route in the same region and reopen the service. The directory helps establish a selection order; it does not promise fixed performance figures or a permanently available library.

ROUTE CATALOG

Grouped by region: route list

The table keeps the static fields needed for route selection. Route status may change with maintenance and traffic scheduling. Refresh the subscription in the client before connecting to obtain the currently available directory.

Country / region City Route type Streaming support
Asia-Pacific routes
Japan Tokyo IEPL Supported
Japan Osaka Transit Supported
Singapore Singapore IEPL Supported
Hong Kong, China Hong Kong Transit Supported
South Korea Seoul Transit Supported
Taiwan, China Taipei Transit Supported
Malaysia Kuala Lumpur Direct Platform-dependent
Thailand Bangkok Direct Platform-dependent
North America routes
United States Los Angeles IEPL Supported
United States San Jose Transit Supported
United States Seattle Direct Supported
United States New York Transit Supported
Canada Toronto Transit Supported
Canada Vancouver Direct Platform-dependent
Europe routes
United Kingdom London IEPL Supported
Germany Frankfurt Transit Supported
France Paris Direct Supported
Netherlands Amsterdam Transit Supported
Italy Milan Direct Platform-dependent
Other regional routes
Australia Sydney IEPL Supported
New Zealand Auckland Direct Platform-dependent
United Arab Emirates Dubai Transit Platform-dependent
Brazil São Paulo Direct Platform-dependent
South Africa Johannesburg Direct Platform-dependent

ROUTE TAXONOMY

Route types in practice

Route names describe the primary transmission path. No type has an absolute advantage outside its use case; consider the destination region, network conditions and purpose together. Match the destination region first, then compare different types in that region.

TYPE A

IEPL

The defining feature of an IEPL route is its use of a dedicated carrier path designed for enterprise network interconnection across the international segment. Compared with connections that rely entirely on hop-by-hop public internet forwarding, it places greater emphasis on managing the path between the entry and exit points. For sustained transfers, remote work, long meetings and high-bitrate streaming, consistent routing is usually more valuable than a brief peak, making this type a strong candidate for important tasks.

Dedicated route capacity generally costs more to build, access and maintain, and scheduling places greater emphasis on capacity management. This does not mean it will always outperform other types in every place or at every time. If the visitor is far from the entry point, or the destination service is busy, the local connection and destination response will still affect the experience. Match the destination region first, then compare types within that region.

Best for: sustained transfers · remote collaboration · high-bitrate streaming

TYPE B

Transit routes

A transit route first sends the connection to a selected intermediate entry point, then delivers it to the destination region through the transit network. The purpose is not simply to add another forwarding step, but to avoid poor public routes between the local network and a remote exit. For services located farther away, transit can split an unstable long-distance link into segments that are easier to manage.

Transit routes balance coverage, maintenance cost and use cases, making them suitable for everyday browsing, AI tools, streaming and general office work. Because the path includes an intermediate entry point, maintenance in that region can affect the route. Keeping an alternative route in the same region is generally safer than relying on one route long term. If the destination platform reassesses the exit region, switch between transit and IEPL routes in the same region.

Best for: everyday browsing · AI tools · regular streaming

TYPE C

Direct routes

A direct route reaches the remote exit from the local network without an additional dedicated transit entry point. Its path is straightforward and its regional coverage is easy to expand, making it suitable for light browsing, quick research, backup connectivity and nearby regions. The actual route depends on the local carrier and international peering, so the same city may perform differently across network environments.

Direct routes generally cost less than dedicated routes and avoid the extra scheduling layer of a transit entry point, but long-distance public routes may change during busy periods. If direct access meets your needs, there is no reason to switch based on the name alone. If pages respond unevenly, meeting audio breaks up or video quality changes frequently, compare it with a transit or IEPL route in the same region.

Best for: light access · nearby regions · backup connectivity

SELECTION NOTES

Choose an exit by use case

City distance is only the starting point. A more practical order is to identify the region recognized by the destination service, choose a route type suited to the task, then observe page response, continuous playback and session stability during real use. The notes below cover common use cases without relying on fixed latency or load figures.

Everyday browsing

For reading websites, researching information and using ordinary online services, start with a nearby Asia-Pacific route for a more consistent response. If a website serves different content by region, choose the target region instead of simply optimizing for distance. Direct or transit routes can both be starting points; if loading becomes uneven, switch to another type in the same region.

Streaming

For streaming, first match the region where the library is available, then check whether the platform correctly recognizes the route. Try routes marked “Supported” first; routes marked “Platform-dependent” are better suited to general regional access. After switching exits, fully close and reopen the target app so it can read the new exit. Account region, payment region and platform rules may still affect the content shown.

AI tools

AI tools often assess access using the exit region, session state and account environment. For ongoing use, keep the same target region and use an IEPL or transit route there as the primary option, with direct access as a backup. Frequent region changes may trigger additional verification, so when troubleshooting, change the route type within the same region before changing countries or regions.

Gaming

For gaming, match the game server’s region rather than the account store or content store region. Start with a nearby transit or IEPL route and observe responsiveness during an actual match. If the game offers a server-region selector, keep the game region consistent with the route exit to reduce unnecessary cross-region round trips.

Remote work

Remote desktops, online meetings and business tools prioritize session continuity. Choose an IEPL or transit route in the region where the work system is hosted, and keep a backup exit in the same region. Avoid switching routes during a meeting or file transfer. If switching is necessary, save your work first and re-establish the session to prevent the system from treating the exit change as a new login environment.

OBSERVATION METHOD

How to tell whether a route fits the task

Fix the target region first

Choose the exit region where the destination service provides the content you need. Comparing regions repeatedly changes the platform library, account assessment and network path at the same time, making the source of a problem difficult to identify. Fix the region first, then compare IEPL, transit and direct routes for clearer results.

Keep the test consistent

Use the same webpage, video segment, meeting entry point or office task for comparison. Do not substitute the loading experience on different websites for a route assessment, because the destination service may respond differently. A complete, continuous session is more informative than observing only the instant of connection.

Keep a backup in the same region

International links and destination platforms can change their routes or regional policies. Keep IEPL, transit and direct routes in frequently used regions as separate candidates. When access changes, switching by type is usually easier for restoring an existing workflow than looking for an unfamiliar region.

SERVICE RECORD

BiliVPN Route Usage Notes

The subscription covers 90+ countries / 200+ routes and supports Windows / macOS / iOS / Android / Linux, with unlimited devices. No email address is required; register with a username and password. Before choosing a service, review the plan details and 7-day no-questions-asked refund policy.

Coverage
90+ countries / 200+ routes
Devices
Unlimited devices
Platforms
Windows / macOS / iOS / Android / Linux
Registration
No email address required