Global Route Directory

Server Nodes and Route Selection

VPNFF covers 90+ countries and 200+ routes. Routes are organized by access path and purpose, can be switched directly in the client, and support unlimited devices.

90+ countries covered 200+ routes to choose from Unlimited devices supported
Open User Dashboard View Plans
Regional directory

Browse representative routes by region

The table highlights major regions, city entry points, and route types. Actual routes in the client may change with network scheduling and maintenance; the table does not show real-time performance data. Choose based on your destination, access network, and actual experience.

Country City Route type Streaming support
Asia-Pacific routes
Japan Tokyo IEPL Dedicated Supported
Japan Osaka Transit Supported
Singapore Singapore IEPL Dedicated Supported
Hong Kong, China Hong Kong IEPL Dedicated Supported
South Korea Seoul Transit Supported
Taiwan, China Taipei Transit Supported
Australia Sydney Direct Supported
North America routes
United States Los Angeles IEPL Dedicated Supported
United States San Jose Transit Supported
United States Seattle Direct Supported
Canada Toronto Transit Supported
Canada Vancouver Direct Supported
Mexico Mexico City Direct Supported
Europe routes
United Kingdom London IEPL Dedicated Supported
Germany Frankfurt Transit Supported
France Paris Direct Supported
Netherlands Amsterdam Transit Supported
Italy Milan Direct Supported
Routes in other regions
United Arab Emirates Dubai Transit Supported
South Africa Johannesburg Direct Supported
Brazil São Paulo Direct Supported
About streaming labels: “Supported” means the route can be used for streaming access in the corresponding region. It does not guarantee that every content library remains available at all times. Available content is still determined by the platform’s regional policies, account status, and licensing arrangements.
Route specifications

IEPL Dedicated vs. Transit vs. Direct

Route names describe the primary path between local access and the target exit. No route type suits every network or use case, so understanding path differences matters more than looking at the city name alone.

IEPL

IEPL Dedicated

IEPL dedicated routes focus on controlling the cross-border segment. Traffic first enters a designated access point, then travels over a relatively fixed international link to the exit region, reducing unpredictable inter-network exchanges on public networks. Their main value is path stability, not a single speed test at one moment.

These routes suit ongoing meetings, remote desktops, cloud document collaboration, extended media playback, and AI tools that require stable sessions. When access involves frequent requests or long-lived connections, path changes usually have a greater impact than the speed of opening one webpage, making dedicated routes a strong choice for work and sustained use.

Dedicated routes typically cost more to access, schedule, and maintain than standard paths. There is no need to send all traffic through a dedicated route: use one for important tasks, and choose transit or direct routes for ordinary browsing based on the destination. This better matches route resources to actual needs.

RELAY

Transit routes

A transit route first sends the connection to a relay entry point better suited to the current access network, then forwards it to the target region. It is not simply an extra hop; it adjusts the network combination between entry and exit to avoid unstable direct paths between the local network and a remote data center.

Transit routes suit everyday browsing, file synchronization, video playback, and common international services. When traffic crosses carrier networks or regions, or the local route is suboptimal, a transit entry point often provides a steadier experience than connecting directly to a remote exit. If several transit entries appear for the same region, try them in sequence and keep the one that performs more consistently on the current network.

Transit routes balance cost and path control, making them broadly useful. They are still affected by the local connection, relay status, and target service network, so route names alone are not enough. A more reliable approach is to use each option continuously for the same task in the same network environment before deciding whether to keep it as a regular route.

DIRECT

Direct routes

A direct route connects the current network straight to an exit in the target region without passing through a VPNFF transit entry. Its path is more straightforward, making it suitable when the local network already has good connectivity to the target data center, as well as for reaching more distant regions or specific city exits.

Direct routes depend more heavily on the current access network. Home broadband, office networks, hotels, and public Wi-Fi may use different exits and inter-network paths, so the same direct route can perform differently in each environment. After changing networks, reassess the route instead of relying on results from the previous environment.

When the destination does not require a persistent connection, or when you want an exit in a specific country and city, try a direct route first. If loading becomes inconsistent, sessions drop, or the cross-region path is too long, switch to a transit or IEPL dedicated route in the same region. Switching routes does not change the plan’s coverage or device rules.

Use-case matching

Choose a route for your destination

Identify the target service’s region first, then consider the route type. An exit close to you is not necessarily close to the target service; the destination, connection duration, and local network all shape the experience.

Everyday browsing

Start with a nearby region

News, search, web tools, and ordinary file access usually do not require a fixed country. Start with a nearby transit route and check whether pages, images, and file transfers load continuously. If a website clearly targets a specific region, switch to an exit there.

Everyday browsing involves many short connections, so changing routes manually too often can interrupt login sessions. Once you find a route that suits the current access network, keep it as a regular entry point and reassess only when the destination or local network changes.

Streaming

Match the exit region to the content region

For streaming, start with the content’s region rather than simply choosing the nearest city. Choose a Japan route for Japanese content and a United Kingdom route for UK content. Support labels are for initial filtering; the actual catalog still depends on the platform account and regional policies.

Choose the route before playback and avoid switching repeatedly once playback starts. If a page opens but playback is inconsistent, switch within the same region from direct to transit or IEPL dedicated. This keeps the same exit region while changing the cross-border access path.

AI Tools

Prioritize session continuity

AI tools often use web sessions, streaming output, file uploads, and account verification at the same time. Prioritize connection continuity and choose an exit in a region where the target service is available. Avoid changing regions repeatedly during a long conversation or file-processing task, as this can change the session environment.

Start with an IEPL dedicated or transit route in the relevant region, then open the target tool to sign in and test it. If your AI services are hosted in different regions, record the routes that work best for each instead of keeping every tool on one exit. For more scenarios, see the ChatGPT Acceleration Guide.

Gaming

Prioritize the game server region

Choose a gaming route based on the actual server region. Account, store, and game server regions may differ, so use the service you are connecting to as the reference. Start with an entry point in or near that region, then compare direct, transit, and dedicated routes for responsiveness and connection continuity.

Downloading updates and playing a live match are different tasks. Updates prioritize sustained transfers, while gameplay prioritizes path stability, so you can choose different routes for each. If the game offers a server-region selector, choose the in-game region first, then match it to a VPNFF exit city.

Work

Create a regular entry point for your work region

Remote meetings, business email, code hosting, cloud drives, and remote desktops require more connection continuity than ordinary browsing. For work, choose an IEPL dedicated or transit route in the region where your work systems are hosted, and verify the connection before an important meeting or large file sync. Once a stable regular entry point is established, avoid switching because of brief differences in page loading.

If your company systems and meeting service are in different regions, record suitable routes for each and switch before starting the task. Remote desktops and ongoing meetings benefit from stable paths, while bulk file synchronization can be compared across route types in the same region. Hotel and temporary office networks may use different exit paths; recheck after arriving in a new environment instead of reusing a choice from your home network.

Switching workflow

From target region to a stable connection

Route selection is not about finding one name that always works; it is about building a repeatable way to evaluate the current network and task.

Confirm the target region

First identify the region served by the website, cloud service, media content, or game server. When the destination is clear, start with the relevant country or a nearby region; when it is unclear, begin with a nearby transit route that covers a broad range of uses.

Compare path types in the same region

Do not change the region and route type at the same time, or it will be difficult to identify the source of any difference. Fix the exit region first, then compare IEPL dedicated, transit, and direct routes in sequence. Test with the real use case: complete a meeting and document tasks for work, or search for content and play it continuously for streaming.

Check the exit and target service after connecting

Once the route shows as connected, visit My IP to check the exit region, then open the target service for a real-world test. A connection status alone does not confirm that app traffic is working as expected; verify both the exit information and the target application.

Keep regular routes for different tasks

Everyday browsing, AI tools, streaming, and work can use different entry points. Record the region and type that suit the current network, then switch before starting each task. Recheck after the access network changes instead of applying results from the old environment to the new one.

Client support

Windows / macOS / iOS / Android / Linux. Sign in to the user dashboard to get the client and subscription configuration.

Get the client
User guide

The route directory updates with the client

This page explains covered regions, representative cities, and route categories. Route names and available entry points in the client may change with maintenance, scheduling, or network conditions. Before an important meeting, remote operation, or extended media session, refresh the subscription in the client, then verify the exit and target service.

VPNFF uses username-and-password registration and does not require an email address. Monthly subscription traffic resets each month on the activation date; when upgrading mid-cycle, the price difference is converted into remaining days. Data packages remain valid until used and never expire. The service supports Alipay / WeChat Pay / USDT and offers a 7-day no-questions-asked refund.

Start Free