Regions
Global Server Locations
A region indicates the available exit location, not the full transmission path. The list below covers popular known locations. Sign in to the dashboard for other covered regions; examples shown here are not a complete route list.
| Country / Region | City | Route type | Streaming support |
|---|---|---|---|
| Asia-Pacific | |||
| Hong Kong | See route list in the dashboard | See labels in the dashboard | Verify on the target platform |
| Singapore | See route list in the dashboard | See labels in the dashboard | Verify on the target platform |
| Japan | See route list in the dashboard | See labels in the dashboard | Verify on the target platform |
| North America | |||
| United States | See route list in the dashboard | See labels in the dashboard | Verify on the target platform |
| Europe | |||
| France | See route list in the dashboard | See labels in the dashboard | Verify on the target platform |
| Switzerland | See route list in the dashboard | See labels in the dashboard | Verify on the target platform |
| Other | |||
| Other covered regions | Check the dashboard | Check each route | Check the target service |
Exit regions, cities and routes are different things
A country or region describes the exit location; a city gives a more specific location; and a route type describes how the connection is organized between your device and the exit. The same region may have different paths, and similar names do not mean the data takes the same route. Check both the region and route type in the list. A region name alone cannot tell you how stable a connection will be, and country coverage does not mean every country has the same route options.
Coverage figures describe the service as a whole; they do not mean every destination website accepts connections from every exit. Websites may also consider account region, content licensing, browser sessions and their own policies. Choosing a region can help match your access needs, but it does not guarantee access to specific content or account permissions. View complete route details in the user dashboard. New to the service? Start with the getting started guide.
How Routes Work
IEPL, Relay and Direct Connections
Here’s what these terms generally mean for network routing. They explain differences in path structure, but do not replace the route labels in the dashboard or guarantee a particular setup in every region.
IEPL: A dedicated international transmission segment
IEPL generally refers to an international Ethernet private line. This type of route uses dedicated resources for relevant transmission segments, organizing access and international transit more distinctly. Keep in mind that your device’s Wi-Fi, local access network and the destination website are still part of the connection. “Dedicated line” does not mean every segment from your device to the website uses exclusive resources.
This option may be worth considering when you prioritize continuity over a long connection, such as for work sessions, remote collaboration or continuous playback. Compare routes by how well they handle your actual tasks, not just by their labels. Dedicated resources typically involve specific capacity and maintenance costs, but those costs do not translate directly into VPNRD plan prices or prove that a particular route will be faster than another type.
Relay: Routing traffic through an intermediate node
A relay route sends the connection to an intermediate node before forwarding it to the exit. This separates the access segment from the onward path, so the entry point does not have to follow the exit location. The intermediate node links the path segments; the number of nodes alone does not determine performance. What matters is how well access, forwarding and exit work together on your network.
Relay routes are a useful starting point to compare for everyday browsing, app access and regular streaming. If an exit performs poorly on your current network, keep the target region the same and try another route in the list. Relays require additional forwarding resources and maintenance, with costs depending on how resources are configured. An extra hop is not automatically more stable or slower; judge performance by testing the same task.
Direct: Relying more directly on local international routes
A direct connection generally means the client connects to the corresponding remote service node without an intermediate entry point designated by the service. Network traffic still passes through carrier equipment, so “direct” does not mean a single physical hop. Performance depends more on routing between your local carrier and the target exit, and may vary with your access network or time of use.
If the route from your local network to the region you need works well, a direct connection can be an option for everyday use or comparison. This setup typically has no dedicated relay segment, but exit resources, international transit and maintenance still have costs. A relatively direct route is not cost-free and does not guarantee a lower price. If access issues occur, compare other routes in the same region to see whether the current path may be the cause.
Use Case Guide
Choose a Route for What You Need to Access
Choose a route based on the task. First check which regions the service accepts, then assess content loading, session continuity and how well the task works in practice. Route names help narrow down your options; they are not the final verdict.
Everyday browsing
If you do not need a specific region, start by trying a known location relatively close to you, then check how familiar websites load pages, images and attachments. Geographic distance is only a starting point; it does not guarantee a shorter route. If the main page loads but images do not, check other resource domains and client routing settings too. Don’t assume the exit has failed.
Once you find a route that works on your network, keep it as your usual option. Switch regions or paths only if problems persist. Changing routes every time you open a page can complicate browser sessions and make issues harder to diagnose.
Streaming and video playback
First check the target platform’s account requirements, content licensing and regional policies, then choose a corresponding exit. Loading the home page does not mean the content you want will play; starting playback does not guarantee the same experience over a long session. Test sign-in, the specific title and sustained playback—not just whether the page appears.
Playback also depends on device decoding, Wi-Fi, the platform and video quality settings. If buffering occurs, pause heavy data transfers on the same network, check your local connection, then try another route in the same region. This page does not label any country as universally supporting streaming; verify compatibility with the target platform.
Accessing AI tools
AI tools often have their own service regions, account eligibility and usage rules. An exit region is only one factor in access and does not change how the platform evaluates your account. Check the tool’s official policies first, then choose an eligible region and test the functions you need, such as signing in, submitting prompts, receiving ongoing responses and uploading files.
For ongoing work, stick with an exit you have verified rather than switching regions frequently. If an account notice appears, distinguish a network connection problem from a platform eligibility restriction; changing routes will not necessarily fix account issues. For more on checking access, see AI access guide.
Gaming connections
For gaming, start by checking the game’s service region and client connection requirements. Normal web browsing does not prove that a route will work well for gaming; connection methods and matchmaking can also vary by game. Confirm that the client is using the intended route, then test sign-in, matchmaking and session stability outside a critical match.
Do not judge gaming performance by exit country alone, and do not assume an international route service is a dedicated gaming accelerator. If the route does not suit your needs, check the client rules or the game’s network guidance. Switching exits during an active session may cause a reconnect, so make changes when an interruption is manageable.
Work and remote collaboration
For work, first confirm which access methods your organization permits and whether business systems require a specific region or network. Cross-border routes do not replace your organization’s authentication or access permissions. Test your actual workflow—including document collaboration, file transfers, meetings and remote sessions—instead of checking only a website’s home page.
If meetings are unstable, first check your local Wi-Fi signal, background uploads and app device settings, then compare routes. Follow your organization’s data-handling policies when working with business information. VPNRD allows unlimited simultaneous devices, but multiple devices sharing an account still use the plan’s data allowance. Device count and available data are separate limits.
Final checks
What to Check After Connecting
Following a consistent verification process reduces unnecessary route switching and helps you describe issues clearly if you need support.
Update your details, then test the task
First check your plan and data status in the dashboard, then update your client subscription so you are not relying on an outdated route list. Choose the region you need and a path listed in the dashboard, then confirm the client is connected. To check your exit, use the IP lookup tool. Exit information confirms the connection’s direction; it does not mean the target service has approved your account or content access.
Next, open the feature you actually need. For browsing, check pages and attachments; for streaming, test the title you want to watch; for AI tools, test submissions and responses; for work, run through the full collaboration workflow. If only one app has a problem, check its settings and routing rules too. Seeing a different exit in your browser does not prove every app on your device is using the same route.
Keep other conditions consistent when comparing routes
When comparing routes, use the same device, access network and task, and change only the route where possible. If you also change networks, apps and exits, it is difficult to tell what made the difference. Note the region, route name, network conditions and exact error message; there is no need to test every route.
If you need help, use a support ticket in the dashboard to describe where the issue occurs, and include a redacted error message. Do not share subscription links, account passwords or authentication details publicly. See the getting started guide for setup steps, or the beginner-to-advanced guide for subscription maintenance, client imports and further troubleshooting.