Location Directory · Route Selection

Global Route List

Choose a service region, then a connection type.

A single region may offer different route types. For everyday browsing, look for a reliable connection; for streaming, consider sustained playback; work and AI tools often benefit from stable sessions. Locations are not ranked by performance, and route types are no guarantee of speed.

View Plans Connection Guide

Location Directory

Browse Route Examples by Region

These static examples illustrate locations and route types. They are not a complete list or an indication of current connection status. Available routes, names, and types are shown in the user dashboard and client.

Swipe horizontally to view the table on smaller screens. Streaming availability depends on the platform's supported regions, your account location, and content licensing.

Regional route examples: country or region, city, route type, and streaming availability notes
Country or Region	City	Route Type	Streaming Availability
Asia-Pacific
Singapore	Singapore	IEPL	Check the region and platform requirements
Japan	Tokyo	IEPL	Check the region and platform requirements
Japan	Osaka	Relay	Check the region and platform requirements
Hong Kong	Hong Kong	IEPL	Check the region and platform requirements
South Korea	Seoul	Relay	Check the region and platform requirements
Australia	Sydney	Relay	Check the region and platform requirements
New Zealand	Auckland	Direct	Check the region and platform requirements
Malaysia	Kuala Lumpur	Relay	Check the region and platform requirements
North America
United States	Los Angeles	IEPL	Check the region and platform requirements
United States	New York	Relay	Check the region and platform requirements
Canada	Vancouver	Relay	Check the region and platform requirements
Canada	Toronto	Direct	Check the region and platform requirements
Europe
United Kingdom	London	Relay	Check the region and platform requirements
Germany	Frankfurt	IEPL	Check the region and platform requirements
France	Paris	Relay	Check the region and platform requirements
Netherlands	Amsterdam	Relay	Check the region and platform requirements
Sweden	Stockholm	Direct	Check the region and platform requirements
Switzerland	Zurich	Relay	Check the region and platform requirements
Italy	Milan	Direct	Check the region and platform requirements
Spain	Madrid	Relay	Check the region and platform requirements
Other Regions
United Arab Emirates	Dubai	Relay	Check the region and platform requirements
South Africa	Johannesburg	Relay	Check the region and platform requirements
Brazil	São Paulo	Relay	Check the region and platform requirements
Chile	Santiago	Direct	Check the region and platform requirements

Connection Types

IEPL vs. Relay vs. Direct Routes

Route types describe how a connection is arranged. Your experience also depends on your local network, carrier routing, exit status, and the destination service. A route's name alone cannot establish a fixed ranking.

IEPL

Cross-border traffic carried over a dedicated circuit

For use cases that need sustained connections

IEPL routes typically use carrier-provided dedicated Ethernet circuits for the cross-border segment, reducing reliance on changes in public internet routing along that segment. “Dedicated” describes how the link is carried; it does not mean the entire route is reserved for one user, nor can it eliminate issues with home networks, wireless signals, or the destination website. Traffic still travels from the exit point to the destination service.

Dedicated circuits generally have higher procurement and maintenance costs, making them better suited to streaming, remote collaboration, and long-running sessions that need sustained data transfer. When choosing a route, check how it performs during the times you usually use it rather than assuming the IEPL label means identical performance across all regions and times. Long-distance connections are still affected by distance and routing.

Relay

Forwarded through an intermediate connection point

A balance of route options and regional coverage

A relay route connects to an intermediate node first, which then forwards traffic to the destination exit. Its value is not simply that traffic “passes through one more place,” but that it may offer a more suitable access and exit path. If the direct route from your local network to the destination region is poor, a relay may improve access. Congestion on the intermediate segment can have the opposite effect.

The cost of this type of route includes access, intermediate forwarding, and exit resources. It generally falls between basic public routes and dedicated circuits, though the specifics depend on the carrier and region. Relay routes can suit everyday access, research, and tasks that need an exit in a particular region. To compare them, keep the destination region the same and check page loads, file transfers, or session stability; avoid changing several variables at once.

Direct

Connect directly to the destination exit

Simple route structure, dependent on public internet paths

A direct route typically connects the client to the exit over the public internet, without an additional relay node. Its relatively simple structure can help you assess direct access from your local network to a destination region. “Direct” does not mean that every destination website is reached without a proxy, nor does a shorter geographic distance guarantee greater speed. The actual path depends on the networks along the way.

Direct routes generally do not require additional relay capacity or dedicated circuits, so their underlying link costs are easier to manage. They may be more affected by public routing and time of day. They can suit browsing that requires a particular region but has less stringent continuity needs. Resource costs provide context for understanding technical choices; they are not additional price tiers listed on this page. See the plans page for current pricing.

Use Cases

Choose a cross-border route for your needs

First check which regions the destination service supports, then compare route types within the same region. Once you find a route that suits your usual tasks, keep an alternative available rather than repeatedly chasing a label that looks better.

Everyday Browsing and Research

If a site has no specific regional requirements, start with a nearby exit that connects successfully in the client. Open familiar pages and check that text, images, and internal links load properly. Seeing the homepage alone is not enough to judge the experience; signing in, searching, and opening attachments are closer to everyday use.

If one site behaves unexpectedly, first check whether other sites work. An issue on just one page may be related to browser cache, site maintenance, or account status. Keeping the exit region the same and trying another route type can help identify whether the issue lies with the route or the site itself.

Streaming and Continuous Playback

Before streaming, confirm that the platform offers service in the exit region and check that your subscription tier, content, and device support the desired video quality. Then test whether playback continues smoothly, resumes after seeking, and has working subtitles and audio tracks. Briefly opening the player does not guarantee a smooth viewing session.

If video quality drops, compare IEPL and relay routes in the same region, and pause large transfers on other devices. I6VPN has no device limit, but unlimited devices do not mean unlimited local connectivity or route resources. Content licensing can also change; see the Streaming Guide for more information.

AI Tools and Coding Assistants

AI services often depend on account region, service availability, and network connectivity. Check the platform's officially supported regions first, then choose a matching exit. A page loading does not necessarily mean that chat, file uploads, editor plugins, or command-line requests will work; test each access method you use.

For ongoing content generation or long sessions in an editor, keep the same exit region throughout the task. Frequent region changes make troubleshooting harder and may prompt additional account checks. If ChatGPT will not open or a plugin times out, distinguish account messages from network errors first. For further troubleshooting, see the AI Tools Guide.

Gaming and Interactive Apps

When choosing a route for gaming, check the game server region, not the account's display language. An exit closer to the server may sometimes reduce detours, but a city name alone cannot guarantee responsiveness. Test in actual gameplay and check input response, character synchronization, and reconnection behavior. Menus and update downloads are not a substitute for testing a match.

Games vary in their proxy and connection requirements, and a general subscription service cannot replace game-specific support. Follow the game's terms of service and adjust routing only within the client's supported options. If web pages work but the game cannot connect, first confirm that the game process is using the intended route.

Remote Work and Meetings

For work, consider the region where company resources are hosted, access policies, and session continuity. Before signing in to company systems, confirm which connection methods your organization permits. If the system requires company-specific access, follow your organization's rules and avoid stacking network tools that could change existing routes.

Check meetings, remote desktops, and file sync separately. If voice works but screen sharing does not, the exit region may not be the cause; also check your local network and app permissions. Choose a route before starting a long task and avoid switching mid-session. After reconciling records, uploading files, or submitting a form, confirm that the service received the result before closing the page.

Connection Checks

What to Check Before Changing Routes

Change one setting at a time and note the client messages, exit region, and destination service behavior. A clear description of the issue is more useful for troubleshooting than switching through every route.

Check Your Local Connection First, Then the Exit

First confirm that your local network is working, the client configuration is up to date, and your account's subscription status and remaining data meet your needs. See the subscription setup guide for instructions on importing a configuration. Do not include subscription links or account passwords in public screenshots; keep only the error message when describing an issue.

Once connected, use Exit IP Lookup to check whether requests are going through the intended exit. IP geolocation databases may differ or be out of date, so consider the result alongside the region selected in the client and messages from the destination platform rather than treating one lookup as definitive.

Distinguish Route Issues from Service Issues

If several destinations are inaccessible, keep the region the same, change the route type, and check again. If only one platform has an issue, review its error message and check your account, region, and service status first. For ways to troubleshoot peak-hour fluctuations, see the Route Stability Guide.

If you still cannot identify the issue, submit a request through the support ticket portal in the user dashboard. Include your device platform, selected route name, what you were doing, and the steps you have tried. To get a client, visit the downloads section in the user dashboard. Available routes are shown in the client.