NETWORK DIRECTORY

Global Nodes and International Routes

Coverage spans 120+ countries / 210+ routes. Start with the exit region, then compare route types, and finally choose based on the application. A farther node is not automatically better, and a premium route is not the right fit for every use case.

Start Free View Plans

No email address required—sign up with a username and password. Supports Windows / macOS / iOS / Android / Linux.

ROUTE / DIRECTORY

Browse Representative Routes by Region

The table lists static regions, cities and access types rather than substituting short-term measurements for real-world experience. The Streaming column indicates whether an exit can be used for content matching in the corresponding region; actual availability still depends on the platform account region, licensing rights and platform policies.

Country/Region	City	Route Type	Streaming Support
Asia-Pacific Routes
Hong Kong, China	Hong Kong	IEPL	Supported
Singapore	Singapore	IEPL	Supported
Japan	Tokyo	Relay	Supported
Japan	Osaka	Direct	Choose by Content Region
South Korea	Seoul	Relay	Supported
Taiwan, China	Taipei	Relay	Supported
Malaysia	Kuala Lumpur	Direct	Choose by Content Region
Thailand	Bangkok	Direct	Choose by Content Region
North America Routes
United States	Los Angeles	IEPL	Supported
United States	San Jose	Relay	Supported
United States	Seattle	Direct	Choose by Content Region
United States	New York	Relay	Supported
Canada	Vancouver	Direct	Choose by Content Region
Canada	Toronto	Relay	Supported
Europe Routes
Netherlands	Amsterdam	IEPL	Supported
United Kingdom	London	Relay	Supported
Germany	Frankfurt	Relay	Supported
France	Paris	Direct	Choose by Content Region
Sweden	Stockholm	Direct	Choose by Content Region
Spain	Madrid	Direct	Choose by Content Region
Other Regional Routes
Australia	Sydney	Relay	Supported
New Zealand	Auckland	Direct	Choose by Content Region
United Arab Emirates	Dubai	Relay	Supported
Brazil	São Paulo	Direct	Choose by Content Region

ROUTE / TYPES

Three Route Types, Different Paths

Route names are not decorative labels. The networks between entry and exit, whether an intermediate access point is used, and how the international segment is arranged can all affect stability, cost and suitability. The explanations below provide a framework for evaluation rather than treating any single label as universally decisive.

IEPL

IEPL routes use dedicated international transport and a more controlled path structure. Compared with routes that rely entirely on forwarding through the public internet, they are generally better suited to sustained transfers, cross-border work, remote collaboration and tasks that require connection continuity. Users still connect through their local network, so the final experience is also affected by the local carrier, wireless conditions and device status.

These routes typically cost more to build and maintain, making them a better fit when stability matters more than price. They do not mean every target website will be faster, nor do they replace the need to choose the right exit region. If the target service is in Japan, choosing a suitable Japanese exit is usually more meaningful than focusing only on the “IEPL” label.

RELAY

Relay Routes

A relay route first sends the connection to a selected access point, then from that point to the target exit. This can avoid poor direct paths between the local network and a distant data center while making the international route easier to adjust. For distant exits in the United States or Europe, relays are often used to balance connection quality, coverage and cost.

Relay performance depends on the combination of entry point, access point and exit; more hops are not automatically better. A well-designed relay consolidates the connection at key points before using a more suitable onward path, while a poor one may add unnecessary detours. Start with a recommended route, then compare other relays in the same region and keep the one that is more stable on your network.

DIRECT

Direct Routes

A direct route goes from the local network straight to the exit data center without an additional relay access point. Its simple structure suits everyday browsing, lightweight queries, backup connections and situations where the local carrier already has a good path to the target region. Direct exits in nearby regions are often worth trying first because the shorter geographic distance makes troubleshooting more straightforward.

Direct routes rely more heavily on the local carrier’s international routing. Performance may vary by region, access network and even time of day. They work well as a cost-conscious, coverage-friendly baseline and as a backup when an IEPL or relay route has issues. When the connection fluctuates, switching to a nearby city or another route type is usually more effective than repeatedly reconnecting to the same city.

ROUTE / SELECTION

Choose the Right Route for Your Use Case

There is no universally best node outside a specific use case. The target service’s location, whether it requires a fixed region, and whether the connection is for brief browsing or sustained transfers can all change the right choice. The common scenarios below break it down.

WEB

Everyday Browsing

For everyday browsing, check connection stability first and distance from the exit second. Start with nearby regions such as Hong Kong, Singapore or Japan, prioritizing routes that keep pages loading consistently, images complete and reconnects infrequent during extended use. Ordinary web requests are usually short and scattered, so optimizing for a single download matters less than reliable resolution and sustained connectivity.

If a website displays different content by region, choose an exit in the region associated with that website. For research or routine web tasks, there is no need to stay on a distant route. When a route has problems, try another type in the same region first, then a nearby region, making it easier to tell whether the issue is the specific exit or the local network.

MEDIA

Video and Audio Streaming

For video, first confirm the content’s region, then choose the corresponding exit marked as supported in the table. Opening the homepage does not guarantee smooth playback; library region, account settings, caching and platform policies can all affect the result. After changing regions, fully quit and reopen the app so it rereads the exit region instead of repeatedly refreshing a failed playback page.

Continuous playback depends more on steady transfer. When a region offers multiple route types, try a relay or IEPL route first and keep direct as a backup. If quality repeatedly drops after playback has continued for a while, also check the local wireless network and background downloads rather than attributing every change to the exit node.

AI Tools

AI tools often assess the exit region, account region and session state together. Choose a region explicitly supported by the target tool and keep the exit relatively stable during a session. Frequent region changes can make the login state, verification flow and API request origin inconsistent. For web use, keep one stable route; for development calls, avoid changing the exit mid-task.

If the site opens but requests fail to submit, first check whether the account itself is usable, then compare other routes in the same region. For long-running development tasks, consider the more controlled path of an IEPL or relay route and keep another exit in the same region as a backup. The right region and a continuous connection usually matter more than switching blindly to a distant node.

GAME

Gaming Connections

Choose a gaming route based on the server’s region, not the account’s registration region. If the game server is in Japan, start with a Japanese exit; for western North America, try nearby cities such as Los Angeles, San Jose or Seattle. Login, matchmaking and live gameplay may use different servers, so whether the launcher opens cannot determine the quality of the full connection.

Gameplay is sensitive to short-term fluctuations. After choosing a route, complete a full match before judging it instead of switching repeatedly at the login screen. Wireless interference, background updates and device power-saving settings can also cause lag. If a direct route in the same region is unstable, try a relay; if the relay does not suit the local network, compare an IEPL route or a nearby city.

WORK

Cross-Border Work

Cross-border work often combines web systems, file transfers, video meetings and remote terminals, placing sustained and mixed demands on one connection. Choose an exit near the region where the team system or cloud service is located and keep the route unchanged during work hours. Frequent switching can make enterprise systems see a changing session origin and may interrupt uploads or remote connections in progress.

For file sync and remote collaboration, compare IEPL and relay routes first, with direct as a backup. Before an important meeting or transfer, close unnecessary background updates and confirm that the local network is stable. GQVPN supports unlimited simultaneous devices, so work devices can keep their established exit while other devices test a backup route without interrupting the main task.

ROUTE / METHOD

A Repeatable Switching Method

Change only one variable at a time when troubleshooting. If the route, device, local network and target service all change together, it becomes difficult to know what actually helped.

Set the Target Region First
Use the region of the website, app, cloud service or team system to define the exit range. When content has a clear regional requirement, do not replace a regionally correct node with a closer one that does not match.
Choose the Route Type Next
For sustained work, file transfers and long sessions, compare IEPL and relay routes first; for general browsing, start with direct routes in nearby regions. Labels are filters, not final verdicts.
Keep Other Conditions Constant
During testing, use the same device, local network and target service. Turn off background updates before comparing results so unrelated traffic does not affect the assessment.
Keep a Backup in the Same Region
Do not save only one regular route. Keep different access methods in the same region so switching is straightforward when the primary route is under maintenance or local routing changes.
Confirm Before Committing
Complete a real task before deciding whether to keep a route, such as a full playback session, one meeting, a development call or a file sync. A change in the connection button alone is not enough to judge the full path.

ROUTE / COVERAGE

Global Coverage Is More Than a List

The value of 120+ countries / 210+ routes is having nearby regions, different cities and different access methods available for the same use case. Coverage answers “where can I connect?”, while route structure answers “how do I get there?” The final choice still depends on your local network and target service.

APAC

Asia-Pacific

Suitable for everyday browsing, regional content, collaboration with Asian teams and nearby-region access. Choose among exits in Hong Kong, Singapore, Japan, South Korea, Taiwan and Southeast Asia based on the target region.

North America

Representative cities across the United States and Canada support North American websites, cloud services, development tools and content platforms. Narrow the choice by east or west coast and by the service’s location.

Europe

Representative cities include Amsterdam, London, Frankfurt and Paris, supporting European business systems, regional content and collaboration across borders.

GLOBAL

Other Regions

Australia, New Zealand, the Middle East and South America broaden the available exit options. For long-distance routes, match the exit to a clear regional requirement rather than using it as the default entry point.

Start with the Target Region

No email address required—sign up with a username and password. All plans support unlimited simultaneous devices and include a 30-day money-back guarantee.

Start Free View Plans