FOR BORDER · Route Directory

Routes and regions

Check the region you need to access, then choose a connection type. Route names describe the exit location and path; they don’t override the destination service’s regional rules.

Start Free View Plans

Region / City / Route

Browse routes by region

The table below is a reference for understanding exit regions and route types, not a complete subscription list. The country or region indicates the exit location a service will typically see; the city gives a more specific location. Route type describes how the connection is routed. Consider these factors separately rather than deciding based only on the route name or geographic distance.

Streaming availability is subject to conditions: even when the exit region meets a platform’s requirements, check its licensing, account-region rules and actual playback.

On narrow screens, scroll the table horizontally. Route types are for reference only; check the current list in your dashboard before connecting.

Regions and Route Types
Country / Region	City	Route Type	Streaming Availability
Asia-Pacific
Singapore	Singapore	Relayed	Check the platform’s regional rules
Hong Kong	Hong Kong	IEPL	Check the platform’s regional rules
Japan	Tokyo	Relayed	Check the platform’s regional rules
Japan	Osaka	Direct	Check the platform’s regional rules
South Korea	Seoul	Relayed	Check the platform’s regional rules
Australia	Sydney	Direct	Check the platform’s regional rules
North America
United States	Los Angeles	Direct	Check the platform’s regional rules
United States	San Jose	Relayed	Check the platform’s regional rules
United States	New York	Direct	Check the platform’s regional rules
Canada	Vancouver	Relayed	Check the platform’s regional rules
Canada	Toronto	Direct	Check the platform’s regional rules
Mexico	Mexico City	Direct	Check the platform’s regional rules
Europe
United Kingdom	London	Relayed	Check the platform’s regional rules
Germany	Frankfurt	Relayed	Check the platform’s regional rules
France	Paris	Direct	Check the platform’s regional rules
Netherlands	Amsterdam	Direct	Check the platform’s regional rules
Italy	Milan	Direct	Check the platform’s regional rules
Sweden	Stockholm	Direct	Check the platform’s regional rules
Other Regions
Brazil	São Paulo	Direct	Check the platform’s regional rules
Chile	Santiago	Direct	Check the platform’s regional rules
South Africa	Johannesburg	Direct	Check the platform’s regional rules
United Arab Emirates	Dubai	Relayed	Check the platform’s regional rules
Türkiye	Istanbul	Direct	Check the platform’s regional rules
India	Mumbai	Direct	Check the platform’s regional rules

Connection Types Explained

Understanding route types

IEPL, relayed and direct describe how a route is organized, not a simple ranking of the experience you can expect. Your local network, connection entry point, exit location and the destination website all affect performance. The notes below explain common technical differences; they are not promises about end-to-end performance on any specific route.

IEPL

A dedicated segment in the route

IEPL generally refers to an international Ethernet private line. In a route design, a dedicated transport segment connects network locations in different regions, reducing reliance on changes in public internet routing along that segment. However, the connection from your device to the entry point and the exit’s connection to the destination service may still use the public internet. The route name does not mean the entire connection is private.

This route type may be worth comparing when connection consistency matters, such as for long video calls, continuous streaming or interactive work. Test it on your own local network and at the times you use it; a private-line label is no substitute for checking performance.

From a network infrastructure perspective, dedicated transport resources generally involve more procurement and maintenance than a public-internet exit alone. This describes how the network is organized, not an extra private-line fee from 4BVPN. Check your dashboard for available routes and eligible plans.

Relayed Route

Forwarded from an entry point to the exit

A relayed route sends your connection to an entry point, which then forwards it to an exit in the destination region. The exit region shown in the client may differ from the location your device first connects to. This setup can make use of peering between networks and offer more flexibility for adjusting specific access paths.

A relayed route is worth comparing when the public-internet path to a particular exit is poor. It can suit everyday browsing, work and streaming, but an extra relay does not automatically make a connection faster or slower. The actual path is what matters.

A relayed route requires coordination between the entry point, relay and exit, and uses different resources from a direct route. For a fair comparison, keep the destination region and app the same, then check page loading, session stability and playback continuity. Don’t judge a route by the word “relayed” alone.

Direct Route

A public-internet connection to the route entry point

A direct route generally means the client connects to the route’s entry point over the public internet, without an additional relay entry point operated by the service. “Direct” describes the route relative to a relayed setup; it does not mean there are no other network devices between your device and the destination website, or that data travels along the shortest geographic path.

A direct route can be a useful baseline. If the peering between your local network and the exit is favorable, it may work well for everyday access. If performance varies at certain times, compare a relayed or dedicated route using the same exit region.

Compared with dedicated transport, a direct public-internet route generally uses a more straightforward resource setup. The overall cost still depends on the exit region, network resources and maintenance. 4BVPN prices are listed by plan; don’t infer the price of an individual route from these general technical notes.

Choose an exit based on the destination service

Choose a route by use case

Choose a route in this order: the region allowed by the service, your day-to-day experience, then account-session consistency. First rule out regions that don’t meet the destination service’s requirements, then compare routes within a suitable region. If the service has no regional requirements, try a nearby exit first—but distance is only one factor, not a substitute for checking access.

Everyday Browsing

For search, research and regular websites, start with a route in a suitable region that loads consistently. Don’t check only whether the homepage opens: sign-in, images, attachments and site search may use different domains. A working homepage doesn’t mean every request takes the same path. In your client’s rules mode, check the relevant requests and confirm that the resources the site needs use the intended exit.

Once you’ve chosen a regular route, keep an alternative in the same region. This usually makes issues easier to diagnose than frequently switching between regions. If just one page is acting up, try another browser window or check the website’s status before changing routes; a cache or site issue can look like a regional problem.

Streaming and Content Libraries

First check which region offers the content you want, then choose an exit in that region. Netflix, Disney+, HBO Max and other services each apply their own content licensing and account rules. Being able to access a platform’s website does not mean you’re eligible to play a particular title. To check, open the title’s details and try playback; note any error message from the platform.

For longer viewing sessions, focus on consistent playback and picture quality. Video quality also depends on your account plan, playback device, browser and the content itself, so don’t attribute every change to the route. After switching exits, an existing session may retain the previous region. End that session before checking again, and avoid repeatedly switching regions.

AI Tools

Before using ChatGPT, Claude, Gemini or similar tools, check the service’s supported regions and account requirements. Regional policies vary, so a route that works with one tool may not work with another. The web app, desktop client and API requests may also follow different rules; check each separately.

When permitted by the platform, try to keep your usage region consistent. Frequent region changes may trigger additional checks and make access issues harder to reproduce. If an existing session is having trouble, note the platform’s message, check your exit and routing rules, then try an alternative route in the same region. Route selection cannot replace account eligibility or payment requirements. See the AI guide for more information.

Gaming and Interactive Use

Choose a route based on the region of the game server you connect to, not just the exit closest to your device. Sign-in services, downloads and gameplay may use different network paths, so normal browser access does not confirm that game traffic is using the intended route. First check that your client’s network mode is compatible with the game, then verify that the relevant traffic uses your selected route.

Gameplay is also affected by your local wireless network, background tasks on your device and the game server’s status. Compare connection consistency outside a live match, and troubleshoot your local network first if something seems off. 4BVPN’s international route information does not guarantee compatibility or performance with any particular game. Results from ordinary websites may not apply to gameplay.

Work and Collaboration

For cross-border work, follow your organization’s access policies first, then choose an exit region supported by the work service. Company sign-in, identity verification, shared documents and meeting media may each use different domains. Test the full workflow: sign in, open a document and join a meeting. If your organization requires a specific network channel, follow its instructions.

If you need to stay signed in for extended periods, keep to one region where possible and avoid changing exits during file transfers or meetings. When a work tool disconnects, note what you were doing, your client’s rules and the route type in use. This helps distinguish sign-in, file-transfer and media-connection issues. Changing routes affects the network path, not your organization’s permissions or file access.

What to Check After Connecting

Check Your Exit and Access

A connected status means the client has established a connection. To confirm that a destination service uses the expected exit, also check routing rules and actual requests. Keep the same app, local network and destination service while testing; changing one thing at a time makes it easier to identify the cause.

Check the exit, then the app

After connecting, use Network Check to see the exit your browser is using and confirm that the region is as expected. This result applies only to the browser request that ran the check, not to other apps. If the browser works but a client does not, check the app’s proxy mode and routing rules rather than switching regions right away.

Keep Conditions the Same When Comparing

If access is inconsistent, first compare different route types within the same region, then consider changing the exit region. Change one factor at a time, keeping the destination page, error message and client mode consistent. This helps distinguish route changes from website regional rules or account-session effects. You can also describe the issue through a support ticket in your account dashboard.

Keep the Directory in Sync with Your Subscription

This static directory helps you understand regions and route types before choosing a route. For actual use, refer to the dashboard and subscription list after signing in. If the names in your client don’t match this guide, update your subscription and check the groups again. Don’t manually edit subscription URLs or use configurations from unknown sources. New to the service? Follow the Quick Start Guide to import your subscription, then return here to choose an exit for your needs.