Regions · Route types · How to choose

International routes and cross-border access

Choose a destination first, then compare route paths. VPNOQ covers 120+ countries / 250+ routes. This page is a location guide; see the user dashboard for routes currently available to you.

Unlimited simultaneous devices Anonymous, no logs 14-day money-back guarantee

A location tells you where traffic exits; a route type describes how it gets there. Consider both—location alone doesn't determine the experience.

Browse routes by location

The table below is a reference for locations and route types, not a complete availability list or a guarantee that every example is always available. Hong Kong IEPL, Japan relay, Singapore IEPL, US direct, and Germany relay routes illustrate different paths; the other cities show how to compare locations. Check the route names and groups shown in your dashboard for current availability.

Streaming support is reported according to current route checks. Video platforms determine access based on factors such as exit IP, account region, content licensing, and their own policies; a country name alone does not guarantee access to a particular catalog. The table does not rank latency, bandwidth, or load, since results vary by network environment.

On narrow screens, scroll horizontally within the table. The city column shows a reference exit location, not the location of the website's servers.

Location guide · Check the user dashboard for availability
Country / region City Route type Streaming support
Asia-Pacific
Hong Kong, ChinaHong KongIEPLBased on current route checks
JapanTokyoRelayBased on current route checks
SingaporeSingaporeIEPLBased on current route checks
South KoreaSeoulRelayBased on current route checks
AustraliaSydneyDirectBased on current route checks
New ZealandAucklandRelayBased on current route checks
MalaysiaKuala LumpurRelayBased on current route checks
ThailandBangkokRelayBased on current route checks
North America
United StatesLos AngelesDirectBased on current route checks
United StatesSeattleRelayBased on current route checks
CanadaVancouverRelayBased on current route checks
CanadaTorontoDirectBased on current route checks
Europe
GermanyFrankfurtRelayBased on current route checks
United KingdomLondonRelayBased on current route checks
FranceParisDirectBased on current route checks
NetherlandsAmsterdamRelayBased on current route checks
SwedenStockholmDirectBased on current route checks
SwitzerlandZurichRelayBased on current route checks
Other regions
BrazilSão PauloRelayBased on current route checks
ChileSantiagoDirectBased on current route checks
South AfricaJohannesburgRelayBased on current route checks
United Arab EmiratesDubaiRelayBased on current route checks

IEPL, relay, and direct routes

Route names can be confusing because they mix up exit locations with connection methods. Routes in the same region can reach their exits through different entry points and paths. The descriptions below explain general route characteristics and cost differences; they don't mean one type is always faster, nor do they promise bandwidth, dedicated resources, or a consistent experience.

Dedicated transmission paths

IEPL

IEPL generally refers to an international Ethernet private line. It uses a dedicated transmission path provided by a carrier to connect two endpoints, reducing reliance on public-internet routing across borders. The connection from your device to the service entry point, the international segment, and the exit to the destination website are separate stages. A private line on one segment does not mean every part of a visit uses a dedicated connection.

This type of route can suit tasks that benefit from a steady connection, such as work calls, remote collaboration, and extended content sessions. When choosing a route, check whether it handles your actual task consistently rather than relying on the “private line” label. Entry access, exit conditions, and the destination service's response can all affect results. If your local network is unstable, address that first.

Cost: Dedicated transmission generally requires ongoing investment in line capacity, so its cost structure differs from using the public internet directly. This is a general comparison, not an estimate of VPNOQ's procurement costs or per-route prices.

Routed through an intermediate node

Relay routes

A relay route sends your connection to an intermediate node, which then forwards it to the destination exit. This intermediate step allows the route to be adjusted and can be worth trying when a direct path to the exit is poor. The relay node and the final exit are not the same thing; websites typically see the exit, not every location along the route.

A relay adds a transmission step, but more steps do not automatically mean a worse experience. If the entry point is easier to reach and the onward path works well with your carrier, a relay may perform better than an unsuitable direct route. Congestion along the intermediate path can also affect page loads and sustained transfers, so compare routes during the times you actually use them.

Cost: Relay routes involve the entry point, forwarding node, and exit resources, so their structure is generally more complex than a single-exit route. Costs vary widely between providers and paths; the word “relay” alone doesn't indicate a price tier.

Connect directly to the destination exit

Direct routes

A direct route typically connects your device to the exit service over the public internet, without an additional service-side relay node. Its connection structure is straightforward and can work well when your local carrier has a good route to the destination exit. “Direct” describes the path, not a guarantee of speed, connection success, or peak-hour performance.

With a direct route, your local carrier's international routing choices can have a more noticeable effect. Results may differ between access networks connecting to the same exit. For everyday browsing, try a direct route in the destination region, then compare it with a relay or private line using the same task. Don't assume route names imply a fixed ranking.

Cost: The route structure is often simpler, but quality exit resources still cost money. A simple structure does not mean resources are equivalent, nor should every long-distance connection default to a direct route.

Choose an exit by use case

Start by identifying the service and task you need, then choose a location. A page loading only confirms access to that page; it doesn't verify video playback, file transfers, or real-time interactions. When comparing routes, change one thing at a time and keep the device, app, and task the same so the results are meaningful.

Everyday browsing: check that pages load fully

For reading news, viewing documents, and accessing code repositories, start with an easy-to-reach Asia-Pacific exit rather than switching repeatedly just to try distant locations. Check that text, images, login pages, and attachments all load. If the main page works but images are missing, related domains may not be using the same route. For everyday use, start with rule-based mode: send requests that need an international route through the appropriate exit and let the client handle other traffic according to its rules. If something goes wrong, check which rules matched before comparing route types.

Streaming: check location and playback eligibility separately

Access to Netflix, Disney+, and YouTube cannot be determined from the exit country alone. First confirm that your account can use the service, then check the page, content catalog, and actual playback. If you see a location message, note what it says rather than assuming every error is caused by the route. For content tied to a particular region, keep related requests on the same exit so the app and browser don't take different paths. For longer viewing sessions, check for repeated buffering; loading the page doesn't verify sustained playback. See streaming access for more details.

AI tools: check for consistent responses

ChatGPT, Claude, Gemini, and coding assistants may have separate location and account requirements in addition to needing a connection. Choose a region where the service is available, sign in, and check that it continues to return content during normal use. Command-line tools may not inherit your browser's connection settings, so if the browser works but the terminal doesn't, check how the tool reads proxy settings. Keep the same exit during a work session to reduce repeated sign-in checks. Avoid switching routes while generation or a transfer is in progress.

Gaming: distinguish downloads, sign-ins, and matches

Game downloads, account sign-ins, and live matches may connect to different servers. An international route may help you reach a download or sign-in service, but that doesn't mean every game will perform better in a match. First check whether the client supports the traffic-forwarding method you need, then watch for lag, disconnections, or inconsistent input response during play. The game server's region is more useful than your own location as a reference, but you'll still need to compare actual routes. For how these two tools differ, read Game Accelerators vs. VPNs.

Work: prioritize a stable connection

Video calls, remote desktops, code commits, and file syncing depend on completing tasks reliably. You can compare private-line and relay routes, but judge them with the apps you actually use—not just how quickly a page loads. Choose an exit before a meeting and keep your connection settings consistent during the call. When accessing company resources, follow your organization's network requirements and check for routing conflicts between its connection tools and your current client. If you see an account security warning, check the service's requirements rather than treating a route switch as a universal fix for sign-in issues.

What to check after connecting

Once your service is active, get your subscription from the user dashboard and import it into your client, then select a route and mode. The subscription contains currently available route information and may differ from this reference directory after an update. Get your subscription through the dashboard; don't share its contents in public documents, repositories, or screenshots.

First make sure the client is connected, then open the service you need. If the page doesn't change, check that the app is using the current connection settings and that the rules cover the relevant requests. Rule-based mode is useful for everyday traffic routing. Global mode can help compare how the current app performs through one exit, but changing modes won't resolve account permissions or a destination service's regional policies.

If the same task works on another route, note the affected route name and the app's message for troubleshooting. If all routes fail, first check your local network, whether the subscription is up to date, and your account plan status. Comparing results over different access networks can help identify an issue with the local path. Change one setting at a time so you can pinpoint the cause instead of changing the route, mode, and app configuration all at once.

For support, submit a ticket through the user dashboard. Include the platform, route name, time of the issue, destination service, and exact error. Hide account details and subscription contents in screenshots. VPNOQ supports Windows / macOS / iOS / Android / Linux; client downloads and subscription delivery are handled through the dashboard.

Read the getting started guide Get the client Open a support ticket

Route selection and data billing

Server location and billing method are separate choices. Start with your main use case, then choose a monthly plan or a data package based on how often you use the service. Monthly plans are ¥9.9/month for 60GB, ¥18/month for 250GB, and ¥28/month for 500GB. Data resets monthly on the activation date; mid-cycle upgrades are prorated for the remaining days. Data packages do not use the monthly plan reset schedule.

Data packages cost ¥158/300GB, ¥358/1000GB, and ¥658/3000GB. Data is available until used and never expires. If you regularly stream video, transfer files, or sync large projects, keep an eye on the remaining data shown in your dashboard. Confirm both that the route connects and that enough data remains. Choose a plan based on your actual usage rather than inferring billing rules from route names.

Use the service on as many devices at once as you like, but device count does not mean each device has a separate data allowance. When using multiple devices, plan downloads and syncs around the data shown in your account. No email address is required to get started; create an account with a username and password. Alipay / WeChat Pay / USDT are accepted, and a 14-day money-back guarantee is available. See the Terms of Service for usage and refund rules.

When comparing subscription services, look beyond location coverage: check whether route types are clearly explained, billing periods are easy to understand, and there's a support channel for reporting connection issues. Coverage gives you options; whether a route suits your network depends on how well it handles your actual tasks.

View plans Read the buying guide
Start Free