Server Nodes - QSVPN | Global VPN Routes by Region

ROUTE DIRECTORY

Global routes by region

Use the table below to quickly find representative regions. Route entries may change based on network conditions and service compatibility; the user panel is the source of truth for available options.

Country or region	City	Route type	Streaming
Asia-Pacific
Hong Kong, China	Hong Kong	IEPL private line	Supported
Japan	Tokyo	IEPL private line	Supported
Japan	Osaka	Transit	Supported
Singapore	Singapore	IEPL private line	Supported
South Korea	Seoul	Transit	Supported
Taiwan, China	Taipei	Transit	Supported
Thailand	Bangkok	Direct	Choose by platform
Malaysia	Kuala Lumpur	Direct	Choose by platform
Philippines	Manila	Direct	Choose by platform
Indonesia	Jakarta	Direct	Choose by platform
India	Mumbai	Transit	Choose by platform
North America
United States	Los Angeles	IEPL private line	Supported
United States	San Jose	Transit	Supported
United States	Seattle	Transit	Supported
United States	New York	Transit	Supported
United States	Dallas	Direct	Choose by platform
Canada	Toronto	Transit	Supported
Canada	Vancouver	Direct	Choose by platform
Europe
United Kingdom	London	IEPL private line	Supported
Germany	Frankfurt	Transit	Supported
France	Paris	Transit	Supported
Netherlands	Amsterdam	Transit	Supported
Italy	Milan	Direct	Choose by platform
Spain	Madrid	Direct	Choose by platform
Poland	Warsaw	Direct	Choose by platform
Sweden	Stockholm	Direct	Choose by platform
Other regions
Australia	Sydney	Transit	Supported
Australia	Melbourne	Direct	Choose by platform
New Zealand	Auckland	Direct	Choose by platform
Brazil	São Paulo	Direct	Choose by platform
United Arab Emirates	Dubai	Transit	Choose by platform
South Africa	Johannesburg	Direct	Choose by platform

ROUTE TYPES

Route types explained

Route names describe how data travels from the access point to the destination region. Different types are not a simple ranking; distance, the entry network and the destination service also shape the experience.

IEPL

IEPL private line

An IEPL private line places cross-region traffic on a relatively independent transport path, with fewer sections relying on the public internet. Its value is not a fixed speed figure, but a path that is easier to manage and typically less exposed to changes in public-network congestion. For sustained transfers, remote meetings, cloud document sync and concentrated evening use, this type is often the preferred entry.

Building and maintaining private lines requires more network resources and usually costs more than ordinary direct connections, so deployment is concentrated in commonly used regions. Confirm the destination service region first; “private line” does not mean you should choose a farther route. For services in Asia-Pacific, a nearby transit entry may be a better fit than a long-distance private line.

Best for: persistent connections, sustained transfers, work collaboration and stable access to commonly used regions.

RELAY

Transit route

A transit route first connects to a selected access point, then uses an intermediate network to deliver traffic to the destination region. This can avoid public-network segments with noticeable quality fluctuations and allows the exit point to be adjusted by region. Actual performance depends on the access-point location, the onward path and the destination service—not just the final city name.

These routes balance coverage, resource cost and connection quality, making them suitable for everyday browsing, AI tools, code repositories, streaming and routine downloads. For cross-continent access, transit is often easier to control than taking the entire public-internet path directly; however, adding intermediate hops means a poor entry choice can create unnecessary detours.

Best for: everyday primary connections, cross-continent access, AI tools, streaming and general use.

DIRECT

Direct route

A direct route establishes a connection from the current network straight to an entry in the destination region, with a simple topology and fewer intermediate scheduling steps. Performance depends more heavily on the local network and the current quality of the international public-internet path. When conditions are favorable, direct access provides a clear route; congestion or routing changes can also cause performance to fluctuate.

Direct connections generally require fewer resources than private lines, making them useful for extending regional coverage, temporary access to less common regions or backup paths alongside transit. Choose a geographically closer city when possible, rather than judging by country alone. Different cities in the same country may still follow different transmission directions.

Best for: nearby regions, less common locations, backup connections and route comparisons.

How they differ

Private lines emphasize independent transport, transit emphasizes path management, and direct routes emphasize a simpler topology. A route name describes only its main structure; it cannot replace judgment based on the actual use case. The entry point, local network, destination location and time of use all affect the result.

Cost considerations

Private lines require more network resources, transit requires maintained access and forwarding paths, while direct routes have a relatively simple structure. Cost differences affect where routes can be deployed and how they are scheduled, but they do not mean the most expensive type is always the best choice.

Switching principle

Choose a route near the destination region first, then compare types. When the connection fluctuates, switching route types within the same region is easier for isolating the issue than jumping to a distant region, and it reduces unnecessary detours.

USE CASE GUIDE

Use-case route recommendations

There is no need to seek one permanent route choice. Identify the application type first, then assess the region, route structure and connection continuity.

A

Everyday browsing

For web browsing, research and ordinary online services, start with a nearby region. Page loads consist of many short connections, so a direct path usually matters more than whether the exit is in a popular city. For Asia-Pacific access, try Hong Kong, Tokyo, Singapore or Seoul first; transit and direct routes are both candidates.

If pages open normally but images, attachments or sign-in repeatedly stall, switch to another route type in the same region. Avoid frequent cross-continent switching, as a website may treat rapid regional changes as an unusual sign-in environment.

B

Streaming and content platforms

For streaming, let the content region determine the exit first, then choose an entry marked as supported in the route table. Opening a platform homepage does not mean specific content has loaded for the target region; after entering the app, check the library, subtitles or content details.

Continuous playback depends more on steady transmission. If playback starts normally but buffers later, keep the country unchanged and switch to a private-line or transit entry in the same region. This preserves the content region while reducing re-identification caused by changing regions.

C

AI tools

AI chats, document analysis and coding assistance usually rely on persistent connections. Confirm the supported region for the service first and keep the exit region stable where possible. For recurring tasks, prefer transit or private lines and avoid changing countries repeatedly in one session to reduce re-logins, interruptions or renewed regional checks.

If a page opens but generation stops, check the browser session and route connection first, then try another entry in the same region. Command-line tools, editor extensions and browsers may use different network settings, so verify each one separately.

D

Gaming connections

Match the game server’s region first rather than choosing the most familiar country name. If the server is in Japan, compare Tokyo and Osaka; if it is in the western United States, compare Los Angeles, San Jose and Seattle. Greater distance adds transmission hops and increases exposure to changes in intermediate networks.

Choose the route before entering a match and avoid repeatedly changing the exit during play. Game updates and live matches have different network needs: update files can use a general-purpose transit route, while matches prioritize path continuity and stable response.

E

Remote work

Remote meetings, business dashboards, cloud documents and code repositories often run at the same time. Choose a private line or transit route based on the region of the main work system, and test the connection before work begins. Switching regions mid-meeting may trigger a reconnect, while business systems may require sign-in confirmation again.

When uploading attachments or syncing project files, focus on whether the transfer completes consistently rather than only on how quickly the page first opens. If a route works for browsing but is unstable for large-file sync, keep the same region and change the route type.

F

Multi-device use

QSVPN has no device limit and works on Windows, macOS, iOS, Android and Linux. Devices do not need to use the same region: a work computer can stay near the business service, a tablet can use the content platform’s region, and a development device can choose the entry best suited to AI tools or a code repository.

Troubleshoot one device at a time. A working connection on one device does not prove that another has the same system proxy, client mode or subscription status. Update the subscription on the affected device first, then compare routes in the same region.

REGION INDEX

Global coverage by region

QSVPN covers 100+ countries / 180+ routes. Regional badges indicate common access directions and do not mean you must always choose a particular city when connecting.

APAC

Asia-Pacific

Suitable for Asian content platforms, regional work services and nearby cloud applications. Common entries include Hong Kong, Tokyo, Osaka, Singapore, Seoul, Taipei, Bangkok, Kuala Lumpur, Manila, Jakarta and Mumbai.

Available types: IEPL private line / Transit / Direct

NA

North America

Suitable for online services, development platforms, content platforms and business systems in the United States and Canada. Choose a city based on whether the target service is in the eastern or western region, then compare private-line, transit and direct routes.

Representative entries: Los Angeles / San Jose / Seattle / New York / Toronto

EU

Europe

Suitable for European content, work and data services. London, Frankfurt, Paris and Amsterdam work as general-purpose entries; Milan, Madrid, Warsaw and Stockholm serve more specific regional needs.

Available types: IEPL private line / Transit / Direct

EXT

Other regions

Entries in Australia, New Zealand, Brazil, the United Arab Emirates and South Africa support access to services in specific regions. Confirm the actual location of the target system first to avoid extra detours chosen solely for a region name.

Representative entries: Sydney / Melbourne / Auckland / São Paulo / Dubai

ROUTE CHECK

Route switching checklist

Follow a fixed sequence to avoid repeatedly testing multiple regions and to identify more clearly whether the issue comes from the device, entry point or destination service.

Confirm the destination region

First identify the main region of the website, content platform, AI tool, game server or business system. If it is unclear, start with a nearby region that fits the use case. Once the region is set, avoid switching continents for the moment.
Choose an entry in the same region

Choose a candidate from the private-line, transit or direct routes in the same region. Try a private line or transit route for sustained transfers and work collaboration; try direct access for temporary use, less common regions or a backup connection.
Verify the destination service

After connecting, open the service you need and check sign-in, page loading, content region and sustained transfers. Viewing the exit region alone only shows the connection direction; it does not replace verification inside the app.
Keep the region, change the type

If the result is unsatisfactory, first change the route type within the same country or between nearby cities. This reduces variables, helps determine whether the current path is the issue and preserves the regional environment required by the service.
Check device settings

If the issue persists, update the subscription and confirm the client’s current mode. Browsers, system apps, editor extensions and command-line tools may use different network settings and should be checked separately. For full import steps, visit Guides.

NODE QUESTIONS

Common node selection questions

These questions explain how regions, route types and application compatibility relate to one another.

Should I always use an IEPL private line?

No. IEPL private lines suit sustained transfers, work collaboration and commonly used regions, but the destination service location comes first. If the private-line entry is far from the service, a nearby transit route may be a better fit. Filter by region first, then compare route types.

Why are multiple cities available in the same country?

Different cities may connect to different regional networks and service entries. Game servers, content platforms and business systems can also be distributed across different areas within one country. Choosing a city closer to the destination service can reduce unnecessary routing detours.

Does a streaming “Supported” label work for every content platform?

“Supported” means the route is a preferred candidate for streaming; it does not mean every platform and content region will always produce the same identification result. Check the library and content details in the target app after connecting. If the result is not as expected, switch to another entry in the same region.

Which region should I choose for AI tools?

Confirm the regions supported by the target tool, then choose a transit or private-line entry in the corresponding area. Keep the exit region stable during use and avoid changing countries repeatedly in one session. Browsers, editor extensions and command-line tools also require separate network-setting checks.

When the connection is unstable, should I change countries or route types first?

Keep the country unchanged first and switch route types or nearby cities in the same region. This makes it easier to determine whether the current path is the problem and avoids requiring a new sign-in after a sudden regional change. Change countries only when the destination region itself was selected incorrectly.

Can different devices use different routes?

Yes. QSVPN has no device limit, and Windows, macOS, iOS, Android and Linux devices can choose entries for their own purposes. Work, streaming and development devices do not need to use the same region, but troubleshoot subscription and client mode separately on the device showing the issue.

How do I get the latest route list?

Sign in to the user panel, then retrieve and update the subscription in the client. Marketing pages show representative regions and route structures, not static subscription URLs. When route entries change, follow the updated subscription information in the user panel and client.