International Routes / Locations and Types

Choose a Server Location and Route

Start with the exit location, then check the route type. The location determines where your connection exits; the route type describes how it gets there. Your experience also depends on your local network and the service you access.

No email address required. Create an account with a username and password.

Locations

Browse Routes by Location

This is a static preview of known locations, not a complete coverage list or a report of current availability.

VPNText covers 100+ countries and 170+ routes. Countries and routes are not the same thing: a location may offer different connection paths, and the client may group routes by type or use case. Read each route's full name when choosing; the same location alone doesn't guarantee the same experience.

Cities and route types that haven't been confirmed are labeled “Check the client”; no deployment details are assumed. Japan's IEPL route and Singapore's relay route are examples. Check the updated route list in your account to see what's available to you. Streaming support isn't guaranteed; verify access for the platform, account region, and connection you're using.

Location Preview · Check the client for cities and available routes
Country / Region City Route Type Streaming Support
Asia-Pacific
Hong KongCheck the clientCheck the clientVerify by platform and region
SingaporeCheck the clientRelayVerify by platform and region
JapanCheck the clientIEPLVerify by platform and region
North America
United StatesCheck the clientCheck the clientVerify by platform and region
Europe
GermanyCheck the clientCheck the clientVerify by platform and region
Other Regions
AustraliaCheck the clientCheck the clientVerify by platform and region

How Routes Work

IEPL, Relay, and Direct Connections

These names describe how a route is set up, not how fast it is. The overview below explains the general principles; a route type is not a performance guarantee.

IEPL

A Dedicated International Route

IEPL generally refers to an international Ethernet private line. It can carry traffic across the international segment of a route, unlike paths that rely entirely on public internet routing. A private-line segment doesn't cover every step between your device and the destination. Your local connection, the network at each end, and the website's response all affect the experience.

This type of route may suit activities where a consistent connection matters, such as remote work, extended web sessions, or ongoing transfers. Dedicated transport resources typically cost more to procure and maintain, but that doesn't mean a particular route will always be faster than other types. No separate surcharge for dedicated routes is listed here. Check your account's route list for availability and configuration.

Relay

Connect Through an Entry Point

A relay route connects to an entry point first, which then forwards traffic to the corresponding exit. This reorganizes the connection path: your local network reaches a more suitable access point before continuing to the destination. An extra hop doesn't necessarily make the connection worse or better; what matters is how each segment works with your current network.

Everyday browsing, image loading, and streaming are useful ways to test a relay route. Costs depend on the entry point, intermediate transport, and exit—not just the exit location's name. If a direct route is unstable at a particular time, compare it with a relay route. Keep the destination and test steps the same so differences in website response aren't mistaken for route differences.

Direct

Check How Your Local Network Connects to the Exit

A direct route generally means the client connects to the relevant service entry point without an additional relay node at the product level. “Direct” doesn't mean there's only one connection between your device and an overseas website; routing still happens within the carrier's network. Direct routes are often more affected by your local carrier, international peering, and time of day.

When your local network connects well to the destination, a direct route can work for everyday websites and apps. Its path may be simpler, but that doesn't mean it has no associated costs or that the plan is cheaper based on the name alone. Test your usual services first, then compare other available types. If a connection stalls for a long time, trying another route type is usually more informative than repeatedly selecting the same route.

Choose by Use Case

Choose a Route for Your Needs

Start with what the service you want to use requires, then choose an exit location. A farther location or a more complex route name isn't necessarily a better fit.

Everyday Browsing: Check That Pages Load Consistently

For everyday browsing, check whether pages, images, and sign-in flows all work reliably. Start with a location that suits your current network, then open sites you visit often and test images, search, and navigation. Seeing the homepage alone isn't enough to judge the whole site: static content may be cached, while sign-in and search require new connections.

If only one site has a problem, test other sites before changing all your settings. If several sites stall, try another route type or location. Once you find a route that works, keep it as your usual option. Avoid switching without a reason; this makes later issues easier to diagnose.

Streaming: Check the Content Region First

For streaming, distinguish between a site that opens and the content you want to watch actually playing. Access depends on the platform's regional rules, your account status, and how it identifies the exit location. The same location label doesn't guarantee the same content will play every time. Choose a location for your target platform, then test playback on a specific title. A poster appearing on the homepage doesn't confirm support.

If playback fails, read the platform's message to identify whether the issue concerns content region, your account, or the connection. Keep the exit location consistent and reopen the playback page. If buffering continues, compare other available routes in the same location. For tips on choosing a location and checking platform access, see the Streaming Guide. Changing locations isn't a universal fix for playback problems.

AI Tools: Keep the Session and Location Consistent

AI tools may rely on different connections for the website, sign-in, file uploads, and ongoing responses. To check whether a route works, don't just see if the chat page loads—submit a task and confirm the response completes. Check the tool's supported regions and account requirements first. A working connection doesn't mean your account meets the platform's terms.

Keep the same exit location during longer tasks where possible. Frequent changes may trigger additional verification and make troubleshooting harder. If a response is interrupted, save the error message and check whether other websites work before switching routes. If you resubmit the task, keep the tool's own billing and task status in mind.

Gaming: Match the Game Region and Connection

Check where the game server is located before choosing an exit; the nearest location isn't automatically the best choice. Login and gameplay may use different connection paths, so being able to sign in doesn't mean the gameplay connection follows the same route. Check the client rules and the game's own connection status rather than relying on the location list alone.

This page makes no guarantees about gaming performance. If the client offers different routes, compare sign-in, updates, and connection behavior outside a match. Game updates can use significant data, so check your remaining allowance if you're on a monthly plan. If a specific game has a problem, check for platform maintenance and server-region issues first, then submit a support ticket with the details.

Work: Prioritize Connection Stability and Access Requirements

Remote work may involve company accounts, shared documents, meetings, and internal systems, each with different access rules. Confirm which connection methods your organization allows before choosing an exit location. If a company system requires a fixed region or a specific network environment, follow its requirements. A standard international route isn't a substitute for dedicated corporate access.

Before joining a meeting or editing an important document, check that sign-in, uploads, and saving work as expected. Avoid switching routes mid-task. If you need to switch, save your work and confirm it's synced first. VPNText allows unlimited simultaneous connections, but check the route and rules on each device individually. Using multiple devices doesn't mean they automatically share the same connection status.

Client Setup

From Route Name to Actual Connection

Check location, route, and access results separately to avoid repeated attempts and make troubleshooting easier.

Refresh the List Before Choosing a Route

Sign in to the user panel to get your subscription, then import it into the client. Steps vary across Windows, macOS, iOS, Android, and Linux, but first make sure the route list has refreshed successfully. Then look for the location and type you want. Sign-in is enough to get routes in non-iOS clients; on iOS, availability depends on your user panel account status. See the Quick Start Guide for instructions. Download clients through the user panel.

Change One Variable at a Time

Keep your local network and destination service the same, then compare different routes in one location or the same route type in different locations. If you change the network, location, and app settings at once, even if access returns, it'll be hard to tell what made the difference. If things slow down during peak hours, compare other available routes first. Don't draw lasting conclusions about a location from one good or bad test.

A connected status only confirms that the client completed its connection process; it doesn't mean every app is using the route as expected. If your browser works but one app doesn't, check the app's proxy settings, client rules, and system permissions. Avoid running multiple network-routing tools at once unless you know how they interact; conflicting settings can cause problems.

Check Traffic Rules Separately from Route Issues

Monthly plans: ¥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 by the remaining days. Data packages: ¥158/300GB, ¥358/1000GB, and ¥658/3000GB. Data lasts until used and never expires. If you have connection issues, check your plan status and remaining data in the panel instead of repeatedly changing exit locations.

VPNText offers a 30-day money-back guarantee. See the Refund Policy for application details. Compare plans on the Pricing page. This page doesn't tie locations or route types to unpublished extra fees, or guarantee specific access results based on your selection.

When in Doubt, Keep Details You Can Check

If you can't access multiple services, start with Troubleshooting and check the connection, rules, and app settings one by one. For help, use the support ticket form in the user panel. Include the platform, route name shown in the client, when the issue occurred, the service you were accessing, the exact error message, and what you've already tried.

Before sharing a screenshot, hide your subscription link, password, and other sensitive account details. The useful details are which route you selected and where you saw the error—not just “it doesn't work.” Share these specific, verifiable symptoms to help distinguish local network, destination-region, and client configuration issues, and avoid repeating steps that have already failed.