NETWORK / ROUTE INDEX

Global VPN Servers

Choose an exit region based on the app you use, then compare IEPL, relay, and direct routes. Check the 8LVPN client for current cities, route types, and streaming labels.

INDEX / REGIONS & EXIT LOCATIONS

Sample International Route Search

The table shows how to combine a country or region, city, and route type. It is not a list of servers currently available or for sale. Cities and route types are examples to illustrate filtering. Check the current options and details in the client; routes without a streaming label should not be assumed to support playback.

Sample combinations of region, city, and route type
Country or region City Route type Streaming support
Asia Pacific · Asia
JapanTokyoDirectCheck the client label
JapanOsakaRelayCheck the client label
JapanNagoyaDirectCheck the client label
JapanFukuokaRelayCheck the client label
Hong KongHong KongRelayCheck the client label
SingaporeSingaporeDirectCheck the client label
North America
United StatesLos AngelesIEPLCheck the client label
United StatesSan JoseRelayCheck the client label
United StatesSeattleDirectCheck the client label
United StatesDallasRelayCheck the client label
United StatesChicagoDirectCheck the client label
United StatesNew YorkDirectCheck the client label
Europe
SwitzerlandZurichRelayCheck the client label
SwitzerlandGenevaDirectCheck the client label
SwitzerlandBaselRelayCheck the client label
SwitzerlandBernDirectCheck the client label
Other · Oceania
AustraliaSydneyDirectCheck the client label
AustraliaMelbourneRelayCheck the client label
AustraliaBrisbaneDirectCheck the client label
AustraliaPerthRelayCheck the client label

On narrow screens, swipe horizontally to view all table columns.

Choose the region first, then compare cities. If a service or work tool requires a specific exit region, narrow your options to routes that meet that requirement, then compare cities. The city shown may not be where the target app’s servers are located, and a closer city on the map does not necessarily mean a shorter route. Test the same service on the same device and network, and compare the full workflow rather than relying on place names alone.

Check what each streaming label actually covers. Make sure the label applies to the platform you want to use; one label does not mean support for every platform. After connecting, open the target library and play the specific title. Loading the home page, signing in, and playing the content are separate checks. Catalog availability can also vary by region and account requirements.

PATH / ROUTING

IEPL, Relay, and Direct Routes

Route types describe how traffic reaches an exit, not how fast a connection will be. The same exit region may have different routes, and a route can perform differently across access networks and times of day.

IEPL

Device → Access point → Dedicated circuit → Exit

IEPL stands for International Ethernet Private Line. An IEPL route uses a dedicated circuit for part of the path between an access point and a remote exit. Compared with routing the entire way over the public internet, this segment is easier to manage. Your device still connects to the access point through the local network, and the exit connects to the destination service over a separate segment. A dedicated circuit does not replace troubleshooting your local Wi-Fi or the destination service.

If you mostly use the service during evening peak hours and calls or sustained transfers repeatedly drop on standard routes, compare them with a dedicated route in the same region. Dedicated routes typically require cross-border circuits, access at both ends, and ongoing operations, so their carrying costs are generally higher than those of standard public internet routes. This compares route infrastructure costs; it does not mean 8LVPN charges separately by route type.

Relay Routes

Device → Relay entry point → Exit

A relay route sends traffic to an entry point first, which then forwards it to an exit in the destination region. The extra hop adds another routing step, but the entry point does not have to be in the same place as the exit. If a direct route from your network to an exit often performs poorly, a relay entry point may provide an alternative path. On the other hand, changing exits may not help if the connection between your device and the entry point is unstable.

A relay can be a useful same-region alternative for a specific task—for example, when a streaming library requires a particular region but the corresponding direct route often fails to load fully. Change only the route when comparing options; keep the device, browser, and access network the same. Relays require entry-point resources and forwarding operations. Their costs depend on the path and how it is provisioned, so the “relay” label alone does not determine plan pricing.

Direct Routes

Device → Exit

A direct route connects the client to a remote exit over the current network without an additional relay entry point operated by the service. It does not mean traffic passes through only one device; your internet provider still routes it as needed. Direct routes have a simpler service-side setup and make a good starting point for everyday browsing and troubleshooting. If pages load normally, there is no need to keep switching to more complex route types.

Direct routes generally do not require extra relay resources or a dedicated circuit, so their infrastructure is more straightforward. Performance still depends on the public route between your local network and the remote exit. If a connection works during the day but repeatedly fails in the evening, compare it with a relay or dedicated route in the same region at the same time. If switching access networks fixes the issue, investigate the original network first.

Change one thing at a time when comparing routes: keep the app and destination region fixed, then switch the route type. This makes it easier to tell whether the difference comes from the exit region or the path traffic takes.

WORKLOAD / USE CASES & TESTING

Choose an International Route for Your Needs

Test a route with a real task: read a page, play a video, complete a request, or stay on a call until it ends. A connected status only confirms that a connection was established; it does not guarantee every app can complete its task.

Everyday Browsing

If you do not need a specific region, start with a direct route as a baseline. Open the international websites you use regularly and check that the text, images, and sign-in pages all load. If only one site fails, try another site on the same route for comparison before changing your connection setup. If several sites stop loading around the same time, compare with a relay in the same region. Once you find a route that reliably handles your usual tasks, keep it as your default.

Streaming

Choose an exit in the region where your target content is available, then check whether the client shows a label for that platform. Open the library and play the title you want, checking for repeated buffering during playback or when seeking. If only high-quality playback is unstable, lower the quality on the same title for comparison. If the title is missing from the catalog, check the region and account requirements first. Playback quality also depends on the content, platform plan, and device capabilities; route type alone cannot determine it.

Read the streaming route guide →

AI Tools

First check that the service region and account requirements are supported by the tool you want to use. For web apps such as ChatGPT, use the same exit to test signing in, sending a request, and receiving the full response. If the page opens but responses keep failing, try another route type in the same region. For developer APIs, distinguish network timeouts from server errors such as authentication or quota messages. If you receive a clear account or quota notice, address the issue it identifies instead of continuing to switch routes.

Read the AI tool access guide →

Gaming

First confirm which game region you are actually connected to. The lobby, login service, and match servers may be in different regions, so a smoothly loading store or news page does not indicate how a match will perform. Test login, matchmaking, and a full session in training or another non-ranked mode first; keep the game region and access network the same when comparing routes. Avoid changing exits mid-match, as reconnecting may disconnect you. Some game clients have their own rules for network proxies, so check the platform guidance before use.

Remote Work

First check whether your organization requires a fixed exit, a corporate connection, or a managed device. If access permissions are verified by source IP, frequently changing exits may trigger reauthentication; different routes in the same region may also use different exit IPs. For calls, test incoming audio, outgoing audio, and screen sharing separately, then test uploads with a non-sensitive file. If work tools must be accessed through a connection provided by your organization, follow its internal setup requirements rather than substituting a public subscription.

Once you have chosen a route, use the client guide to test the connection. If you are connected but an app still does not work, note your device OS, access network, route name, reproduction steps, and any app messages, then use the troubleshooting guide to narrow down the cause. When submitting a support ticket, include those details. Before sharing screenshots, hide account credentials and subscription links.