VPNFact / International Route Directory

Server Locations

Narrow your options by region, then compare routes using the task you actually need to complete. The regional index shows where to start looking; route types describe how traffic may be forwarded. Neither can replace a real connection test.

Directory / Browse by region

International Route Index

“Not listed” means this page does not provide details to verify. It does not mean that a region has no routes, or that streaming is supported or unsupported there. Check the available options in the client. If the app shows only a region or route abbreviation, do not infer the data center city, connection method, or platform compatibility from the name.

Publicly listed regions and route details
Country or region City Route type Streaming support
Asia Pacific
Hong KongNot listedNot listedNot listed
JapanNot listedNot listedNot listed
SingaporeNot listedNot listedNot listed
North America
United StatesNot listedNot listedNot listed
Europe
NetherlandsNot listedNot listedNot listed
GermanyNot listedNot listedNot listed
Other
Details for other regions are not listed on this page. Check the available routes in the client.

A region label, the geographic location of an exit IP, and the region shown by a website for your account are not the same thing. A platform’s displayed region may also depend on account settings and its own detection rules, so the region name alone cannot confirm which content catalog is available.

Terms / Routes and costs

IEPL, relay, and direct routes

These terms do not all describe the same kind of thing. IEPL refers to a specific way of carrying traffic over certain network segments; relay and direct describe connection and forwarding paths. A relayed route may also use a dedicated line on some segments. The explanations below are general concepts and do not mean that every route type is available in the regions listed above.

Transport method

IEPL dedicated line

IEPL is an international Ethernet private line, typically provided by a carrier between agreed handoff points. For cross-border access, the dedicated line may carry traffic only over part of the route, from an access point to a remote handoff point. Traffic from your device to the access point and from the exit to the destination website may still use public networks. The term does not mean that a single private link runs all the way from your device to the destination, nor is it an encryption protocol or a streaming support label.

This option may suit tasks where consistent routing matters, such as meetings at a regular time or remote collaboration. Costs generally depend on the locations of the handoff points, leased capacity, cross-region segments, and operations. Even when a dedicated line is used for part of the route, local wireless congestion or an issue with the destination service can still affect performance. To decide whether it is worthwhile, compare the complete task during the hours you usually use it, rather than relying on the route name alone.

Forwarding path

Relay route

A relay route connects to an access node first, then the service forwards traffic to a remote exit. The access node and exit do not have to be in the same region. If the direct route from your access network to a remote exit performs poorly, another forwarding path may be worth testing. However, an additional forwarding hop also adds another point to troubleshoot. A problem on the access segment, forwarding segment, or exit can all show up as slow page loads or dropped connections.

Relay costs generally include the access node, transmission between nodes, exit resources, and maintenance. The term “relay” alone does not tell you whether the route uses a public link or a dedicated line, nor does it mean that it necessarily costs more than a direct route. For a fair comparison, keep the exit region and task the same and change only the access path. This makes it easier to tell whether a difference comes from the connection route or how the destination handles different exits.

Forwarding path

Direct route

In subscription route names, “direct” generally means the client connects straight to the exit node without an additional server-side relay layer. “Direct” does not mean there are no routers or carrier interconnections along the way. It is also different from “direct” in some client routing rules, where it usually means the app’s traffic does not go through an acceleration route. When reviewing settings, check whether “direct” refers to the node type or how app traffic is handled.

A direct route can avoid the cost of a separate access node and relay transmission, but exit resources and public network interconnections still have costs. If the direct route performs well during the hours you usually use it, it can serve as a comparison option for web browsing or light office work. If results differ significantly between your home broadband and another access network, compare the local connection and carrier routes first rather than drawing conclusions about the route type from a single test.

Choosing a route / Test with real tasks

Choose a route by use case

Start with the requirements you must meet, such as the region allowed by the target service, your organization’s required exit location, or the region of your game account. When comparing routes, use the same device, access network, and destination service where possible, and change only one route at a time. Recording where an issue occurs makes it easier to review than simply noting “fast” or “slow.”

Everyday browsing

If the target website has no specific regional requirements, you can start with a nearby region, but don’t treat distance as proof of routing performance. Try opening a new page, continuing after signing in, and downloading a file you use regularly. Note whether the initial page takes a long time to appear or the page loads but images are missing. If only one site shows an error, cross-check with another site first. If only the first visit is slow, check DNS resolution and browser extensions before switching regions.

Streaming

First check your account region, subscription benefits, and the title you want to watch, then test whether the route can play that content. Opening the homepage or seeing a poster does not guarantee that the video will play continuously. Once playback starts, try seeking and changing the video quality to see whether it pauses frequently. For a region warning, check the platform’s rules first. For buffering, check your device’s wireless connection, other traffic on your home network, and video quality settings. These issues call for different troubleshooting steps; see the streaming guide for help telling them apart.

AI Tools

First check the tool’s service regions and account requirements, then test sign-in, ongoing conversations, and file uploads using your usual workflow. Getting a text response does not guarantee that attachments will upload successfully; an unavailable model or feature may also be related to account permissions. If a long response stops partway through, try a short request in the same tool before comparing routes. Keep the exit location consistent during sign-in verification so you can isolate the issue without changing both the browser session and exit at once. See AI tool access guide for related steps.

Gaming

First confirm your account’s game region and shortlist routes for that region. Once you can reach the lobby, also check matchmaking, in-game controls, and voice chat; these features may use different service addresses. Pause background syncing and game downloads during testing, and make sure the client is routing game traffic—not just browser traffic. If the issue occurs only after matchmaking, confirm the actual game region and check the in-game network message first. Don’t switch routes during a live match, or you may mistake a dropped session for a route failure.

Remote work

Follow your organization’s requirements for access routes. During meetings, check that audio stays connected, video doesn’t freeze, and screen sharing starts reliably. For collaboration, check document saves, file uploads, and repository sync. If your company systems require a fixed exit location or managed devices, ask your administrator whether a network acceleration service is allowed. Test beforehand using the same device and access network, and keep a verified alternative route available. For more comparison tips, see how to choose a route for remote work.

Keep connection records you can review. Note the access network, route name, destination service, and steps that triggered the issue. Record whether the same action worked after switching routes. This makes it easier to reproduce known conditions and troubleshoot one factor at a time if the issue returns. Before sharing screenshots, hide subscription links, account details, and internal service addresses.

Representative regions

The names below correspond to the index above and do not indicate the order of relays between regions.

  • Hong Kong
  • Japan
  • Singapore
  • United States
  • Netherlands
  • Germany