Choose an exit region, then pick a route for your needs.
Coverage spans 100+ countries and 210+ routes. Find regional route guidance and explanations of connection types. For current routes, names and availability, check the user dashboard after signing in.
First check which region your target service requires, then see which routes are available for that region in the dashboard. Distance is only a guide: your experience also depends on your local network, ISP routing and the target service's response.
For everyday browsing and remote collaboration, start with a nearby region. For content available in Japan, first check the Japanese exit location and your account's regional requirements.
Asia-Pacific route reference · Check the dashboard for current availability
Country / region
City
Connection type
Streaming availability
Hong Kong, China
Hong Kong
IEPL dedicated line
Verify by testing the service
Japan
Tokyo
Relayed
Verify by testing the service
Japan
Osaka
Direct
Verify by testing the service
Singapore
Singapore
Direct
Verify by testing the service
South Korea
Seoul
Relayed
Verify by testing the service
Australia
Sydney
Relayed
Verify by testing the service
North America
Suitable for services and collaboration environments that require a North American exit. Don't judge a route by its city name alone; test it with the target site or app.
North America route reference · Check the dashboard for current availability
Country / region
City
Connection type
Streaming availability
United States
Los Angeles
IEPL dedicated line
Verify by testing the service
United States
Seattle
Relayed
Verify by testing the service
United States
New York
Direct
Verify by testing the service
Canada
Toronto
Relayed
Verify by testing the service
Europe
Choose an exit based on the target service's regional requirements and your work environment. Nearby European cities can still have very different routes to your network.
Europe route reference · Check the dashboard for current availability
Country / region
City
Connection type
Streaming availability
United Kingdom
London
Relayed
Verify by testing the service
Germany
Frankfurt
IEPL dedicated line
Verify by testing the service
France
Paris
Direct
Verify by testing the service
Netherlands
Amsterdam
Relayed
Verify by testing the service
Italy
Milan
Relayed
Verify by testing the service
Switzerland
Zurich
Direct
Verify by testing the service
Other regions
Use this section to check access requirements for a specific region. If no region is required, there's no need to choose a more distant route just to change your exit. Prioritize a consistent experience with your apps.
Other regions route reference · Check the dashboard for current availability
Country / region
City
Connection type
Streaming availability
Brazil
São Paulo
Relayed
Verify by testing the service
South Africa
Johannesburg
Relayed
Verify by testing the service
United Arab Emirates
Dubai
Relayed
Verify by testing the service
India
Mumbai
Direct
Verify by testing the service
TOPOLOGY NOTES
Dedicated lines, relayed and direct connections
Connection types describe how traffic is routed, not a speed tier. Protocols define how a connection is established and carried; topology defines its path. Treat them as separate choices.
IEPL dedicated lines
Focus on how cross-border traffic is routed
IEPL usually refers to an international Ethernet private line. These routes use dedicated transmission resources for the cross-border segment, reducing reliance on the public internet along that part of the path. This describes the transmission resources and access setup; it does not mean every segment from your device to the destination website uses the same private line.
This option may suit users who value a consistent experience during peak hours, remote meetings or longer sessions. Keep in mind that your local Wi-Fi, access provider and the destination service beyond the exit can all affect performance. Congestion or failure on any segment may affect the result, so a dedicated-line label is not a performance guarantee for every website.
Cost trade-offs: Dedicated transmission resources generally cost more to provide, but infrastructure costs do not mean RFCVPN charges separately for a specific route. This page does not list route-level prices. Check the dashboard for available routes and how they relate to each plan.
Relayed connections
Use an entry point to shape the route
A relayed route connects to an entry node first, which then forwards traffic to the exit. The entry and exit can use different network resources, helping match the access segment to the international segment. An extra forwarding step does not necessarily mean a worse experience: a suitable entry point may make the overall route more stable than connecting directly to the exit.
This setup can work well for everyday browsing, streaming, or when a direct route from your local network to an exit performs poorly. Compare routes on the same network, at similar times, using the same destination. Check page loads, video buffering or session stability rather than relying on the word “relayed” in a route name.
Cost trade-offs: Relaying requires entry and exit resources, plus forwarding capacity; costs depend on procurement and routing arrangements. It often allows more flexible route combinations, but there is no fixed price or performance ranking. You cannot infer that a particular plan will be faster from the route type alone.
Direct connections
Connect from your local network straight to the exit
A direct connection generally means the client connects to the exit node without first passing through an additional relay entry point arranged by the service. “Direct” is relative to a relayed setup: traffic still passes through your local access network, ISP and international routes. It is not a dedicated physical connection between your device and the server.
When your local provider has a suitable route to the destination region, a direct connection may offer a simpler path for everyday browsing, research and general office work. Public routes can still become congested at peak times, so consider keeping another connection type in the same region as a backup instead of relying on one topology.
Cost trade-offs: Direct connections use fewer resources for additional relay entry points, but exit bandwidth, data center and network quality still affect costs. A simpler setup does not mean lower quality, nor does it guarantee the same connection performance in every region.
SELECTION NOTES
Choose a route by use case
Follow the same steps when choosing a route: confirm regional requirements, test the task you need to do, then compare connection types. A stable setup that gets the job done is more useful than repeatedly switching regions.
Everyday browsing
Avoid unnecessary route changes
For research, websites and documents, start with a nearby region. Open sites you use regularly and check that page content, images and sign-in pages all load. If one site doesn't open, that doesn't necessarily mean the whole route is down; the site may be under maintenance, your browser cache may be stale, or a routing rule may not have matched.
If the same destination repeatedly fails to load fully at a particular time, keep the region unchanged and compare another topology. This helps distinguish a region issue from a route issue, rather than switching between countries without knowing which change made a difference.
Streaming
Check the content library, then test playback
First make sure the content is available in your selected region and that your account meets the platform's requirements. Loading a page, seeing its artwork and playing a video are separate checks. After choosing a region, open the title you want and try playing it. Look for regional restrictions, playback errors or repeated buffering.
Streaming platforms can change content licenses and how they identify exits, so a static route list can't predict long-term results. “Streaming supported” does not mean every content library will be available. If only one platform has a problem, check your account region and content rights first, then try another route in the same region. For library differences, see the Disney+ regions and route guide.
AI Tools
Keep your region and session consistent
When using AI tools such as ChatGPT and Claude, first check the platform's service regions, account requirements and usage rules. A network connection provides an access route; it does not grant platform authorization or change your account's subscription benefits. Choose an exit within the service's supported region, then test the features you actually use, such as conversations and file uploads.
Long sessions benefit from a consistent network environment. If the service is working, avoid changing regions mid-task. If an access message appears, first distinguish a network error from an account notice or a busy platform. Keeping the original message for reference is usually more helpful than repeatedly switching exits.
Gaming
Prioritize server region and stability
For gaming, start with the game's server region and rules. Confirm the location of the server you want, then check that the client routes game traffic correctly. A website loading successfully does not prove game traffic follows the same route. If you use split routing, test sign-in, matchmaking and gameplay separately.
An international route subscription is not a dedicated service optimized for every game, and connection results are not guaranteed for all games. Focus on session stability, repeated disconnections and whether uploads or downloads on other devices are competing for local bandwidth. Avoid switching routes during gameplay, as this may interrupt the connection.
Remote work
Test the route with your full workflow
Work involves more than opening websites: check meeting audio, shared documents, file sync and corporate sign-in. Follow your organization's network requirements and confirm that international routes work with its access environment. If internal company resources aren't accessible, don't change security settings required by your organization on your own.
Before an important meeting, test audio, video and file tasks in the apps you use, and note the region and connection type that work best. RFCVPN allows unlimited simultaneous devices, but they still share your local network resources. If large file transfers affect a meeting, check local bandwidth usage before assuming the exit region is to blame.
CHECK & SWITCH
Test results and backup options
Set up a comparison you can repeat
Get your subscription from the user dashboard and import it into your client. First make sure the subscription has updated successfully, then choose a route actually listed in the dashboard. Keep your network environment the same and test the same site or app feature. Changing the exit, protocol and client settings all at once makes the results hard to interpret. A route name can help identify a configuration, but it doesn't prove the destination service is accessible.
If results are poor, check your local connection first, compare other routes in the same region next, and only then consider changing regions. Note when the issue occurred, which client and route you used, and what the service displayed. When contacting support, don't share subscription links, passwords or full account credentials; include only the troubleshooting details needed in your ticket.
A connected route doesn't mean the task is complete
When the client reports a successful connection, that means one part of the connection is established; the destination service still needs to respond. For streaming, test video playback; for work, test meetings and documents; for AI tools, test the features you need. Checking the actual task is more reliable than relying on a connection icon, and helps avoid mistaking an account access issue for a route failure.
Keep your regular route and a backup in the same region so you can switch methodically if something goes wrong. To import your subscription again, see Getting started. For persistent connection issues, check the Help Center first, then submit a support ticket through the dashboard. Get current route details from the dashboard; you don't need to create a connection configuration manually from the examples on this page.