Regional cross-border route guide
Coverage spans 110+ countries and 170+ routes. The table below shows selected locations; see the user dashboard after signing in for the full list, city names and available routes.
| Country / region | City | Route type | Streaming support |
|---|---|---|---|
| Asia-Pacific | |||
| Singapore | Check the dashboard | Check the dashboard | Depends on service region and testing |
| Japan | Check the dashboard | Check the dashboard | Depends on service region and testing |
| Hong Kong | Check the dashboard | Check the dashboard | Depends on service region and testing |
| Australia | Check the dashboard | Check the dashboard | Depends on service region and testing |
| North America | |||
| United States | Check the dashboard | Check the dashboard | Depends on service region and testing |
| Canada | Check the dashboard | Check the dashboard | Depends on service region and testing |
| Europe | |||
| Netherlands | Check the dashboard | Check the dashboard | Depends on service region and testing |
| Germany | Check the dashboard | Check the dashboard | Depends on service region and testing |
| United Kingdom | Check the dashboard | Check the dashboard | Depends on service region and testing |
| Other | |||
| See the dashboard for other covered regions | Check the dashboard | Check the dashboard | Depends on service region and testing |
Directory listings vs. available routes
A region indicates the general location of the exit, a city narrows down its location, and a route type describes the connection path. These fields answer different questions: the number of regions is not the number of physical servers, and a city name alone says nothing about connection quality. Specific cities aren’t listed here because this public directory doesn’t replace the actual configurations in the dashboard. Check the full route name in the client or dashboard before choosing.
The directory doesn’t promise fixed streaming availability. Whether content plays depends on the platform’s service regions, your account region, content licensing and how the platform identifies the current exit. Reaching a homepage doesn’t guarantee access to a specific title, live stream or resolution. Follow the platform’s rules and test the content you plan to watch before deciding which route to keep.
This directory explains the range of options. Check the user dashboard and client for currently available cities, route types and configurations.
IEPL, relay and direct routes
The following describes general principles and cost structures for different route types. It doesn’t guarantee a particular configuration in every region or describe additional CPUVPN plan charges.
IEPL routes
Focus on the cross-border segmentIEPL generally refers to an international private Ethernet circuit. In network acceleration, the label usually means dedicated resources are used for the cross-border segment rather than relying entirely on the public internet. The connection from your device to the entry point and from the exit to the destination still involves other network segments, so an IEPL label doesn’t guarantee an uninterrupted end-to-end experience.
These resources typically cost more to build and lease, and may suit use cases where maintaining long connections, video calls or ongoing work sessions is a priority. Assess whether the route actually improves reliability for your target app instead of relying on the label alone. A congested local Wi-Fi network, a busy service or an unsupported exit region may still cause problems.
Relay routes
Focus on how the entry and exit work togetherA relay route sends the connection to an entry point first, then forwards it to an exit. Separating entry and exit points can help organize connections across regions, but performance depends on the entry point, forwarding capacity, exit resources and how these parts work together. A relay isn’t automatically a dedicated line, and the word “relay” doesn’t tell you what cross-border infrastructure it uses.
In general, a relay requires maintaining entry, forwarding and exit resources, so its setup can be more involved than a simple direct connection. Actual costs depend on the infrastructure. You can compare relay routes for browsing, streaming and work. If multiple entry points are available, keep the target region the same and compare routes to see more clearly what changes.
Direct routes
Focus on the path from your network to the exitA direct route generally connects your client to the corresponding exit without an additional service-provided relay entry point. With fewer routing layers, the setup is relatively simple, but the connection still passes through multiple parts of your carrier’s network and the public internet. “Direct” describes the connection setup; it doesn’t promise a particular physical distance, route length or app response time.
Direct routes generally have lower infrastructure costs and may work well when your local network and the target exit are a good match. They’re also useful as a baseline when comparing route performance. Results can be sensitive to local carrier routing and time of day. If your work depends on a persistent connection, test it in your actual work environment rather than assuming results from another network will apply.
Infrastructure costs don’t determine plan prices
These cost notes explain network resources. They don’t mean CPUVPN charges separately for route labels or guarantees that a particular plan includes a specific route type in a specific region. See the plans page for pricing and data rules, and check the dashboard for route access and availability. Monthly plan data resets each month on the activation date; if you upgrade mid-cycle, the price difference is prorated for the remaining days. Data add-ons don’t expire and remain available until used. Choose a plan based on your usage frequency and data needs rather than the route name alone.
Set your route selection priorities by use case
Rule out regions that don’t fit first, then compare connection performance. Change one setting at a time and keep the route that completes your task reliably.
Everyday browsing
If the service doesn’t require a specific region, start with a location that fits its rules and offers a suitable route. Proximity can help narrow down options, but geographic distance doesn’t necessarily reflect the actual network path. After connecting, check that everyday sites load their text, images, sign-in pages and downloads correctly. Opening a homepage alone doesn’t confirm that all related resources are reachable.
If only one site has problems, first check whether the site itself is working and whether your client’s routing rules send it through the selected route. Don’t switch through every region because of an isolated issue; it makes the results harder to interpret and may trigger repeated sign-in checks.
Streaming and live video
Check the content provider’s regional licensing first, then choose an exit in the relevant region. A title’s availability, your account eligibility and playback permissions are separate issues, so test playback even when you’ve selected the right region. Check whether the content starts, plays consistently, offers the expected subtitles and audio, and resumes after seeking. Don’t judge by the preview or homepage recommendations alone.
While watching, keep the same region and route where possible to avoid interrupting the session. If buffering tends to happen during your usual viewing hours, compare route types under similar network and usage conditions, and pause large local downloads. Network acceleration can’t replace a platform subscription or change its content licensing rules.
AI Tools
Before using ChatGPT, Claude, Gemini or Midjourney, check the service’s regional and account requirements. Opening the website is only the first step: test sign-in, task submission, continued output and file uploads. For text tools, check that a response completes; for image tools, test both submitting a task and retrieving the result.
For everyday use, keep the exit region consistent instead of switching routes whenever there’s a brief delay. A region and route can’t replace account eligibility, usage limits or platform review. If the platform displays a specific account notice, follow its instructions before troubleshooting the connection; assuming every error is route-related can obscure the real cause. For more scenarios, see the AI tools access guide.
Gaming connections
Start with the region where the game’s servers are located, not just the client language or account region. Check that the game allows the connection method, then test sign-in, matchmaking, joining a match and sustained play. A smooth game update download doesn’t guarantee stable gameplay; the two may use different services and connection methods.
This page doesn’t guarantee compatibility with any specific game. Connecting the client to a route doesn’t mean all game traffic will automatically use it. Check your routing rules and in-game connection status, and test outside important matches. Follow the game’s official guidance if it has specific connection requirements.
Work and remote collaboration
For work, first confirm your organization’s requirements for exit region, access permissions and security, then choose a route. Video meetings, shared documents, remote desktops and code repositories can behave differently, so test each one. Check sign-in and file operations before work begins, and try to keep the exit unchanged during meetings. Follow your organization’s required connection process if it has one.
CPUVPN allows unlimited simultaneous devices and supports Windows / macOS / iOS / Android / Linux. Unlimited devices doesn’t mean every device has the same local network conditions; check routing settings on computers and mobile devices separately. Get the client from the dashboard and sign in to retrieve your subscription. The iOS option is available when the dashboard shows an active eligible plan.
Test and adjust after connecting
Keep the region; compare routes
When something goes wrong, note the app, selected region, route type and what happened. A successful sign-in followed by a failed file upload points to different areas than a site that won’t load at all. Keep the region fixed and compare other routes available in the dashboard. If that doesn’t help, check client rules and your local network. Change one variable at a time so the results are comparable.
Check the exit, then test the app
Use the IP lookup tool on this site to check your browser’s exit, then return to the target app and test it. Browsers and standalone apps may use different proxy settings, so a browser result doesn’t necessarily reflect other programs. Even if the detected region looks right, check whether the app follows system settings and whether an old session or cached data could be affecting it.
Report issues with reproducible steps
For help, submit a support ticket from the user dashboard with the platform, target service, route name and steps to reproduce the issue. You can include the error text or a screenshot with sensitive details obscured, but never share your password, subscription link or account credentials. Distinguish between “can’t connect to the route” and “connected, but the target app isn’t working” to help narrow down the cause. See Frequently Asked Questions for common fixes, or follow the quick-start guide to set things up.
Choose a plan based on your long-term usage habits, not a brief test alone. CPUVPN offers a 60-day no-questions-asked refund policy; see the refund policy for details. Use the route directory to compare options, then choose a connection that follows the target service’s rules and works for your needs.