ClipVPN / NETWORK DIRECTORY

Global Nodes and Routes

110+ countries and 230+ routes. Start with your destination, then choose an exit region and connection path.

Unlimited simultaneous devices Bank-grade encryption 14-day no-questions-asked refund

This page is a static route reference, not a live status dashboard. Route names describe combinations of regions and paths. Check the dashboard and subscription after signing in for currently available options.

REGION / CITY / PATH

Browse routes by region

The country or region identifies the exit location, the city narrows it down, and the route type describes how the connection is routed. The list below shows selected region and route combinations. It is not a complete inventory, and availability of a route type may vary by city.

Static route reference · Check the dashboard and subscription for available routes
Country / region	City	Route type	Streaming availability
Asia-Pacific
Hong Kong	Hong Kong	IEPL	Depends on actual access results
Singapore	Singapore	Direct	Depends on actual access results
Japan	Tokyo	IEPL	Depends on actual access results
Japan	Osaka	Relay	Depends on actual access results
South Korea	Seoul	Relay	Depends on actual access results
Australia	Sydney	Direct	Depends on actual access results
New Zealand	Auckland	Relay	Depends on actual access results
Malaysia	Kuala Lumpur	Direct	Depends on actual access results
North America
United States	Los Angeles	Relay	Depends on actual access results
United States	Seattle	Relay	Depends on actual access results
United States	New York	Direct	Depends on actual access results
Canada	Vancouver	Relay	Depends on actual access results
Canada	Toronto	Direct	Depends on actual access results
Europe
United Kingdom	London	Relay	Depends on actual access results
Germany	Frankfurt	Relay	Depends on actual access results
France	Paris	Direct	Depends on actual access results
Netherlands	Amsterdam	Relay	Depends on actual access results
Switzerland	Zurich	Relay	Depends on actual access results
Sweden	Stockholm	Direct	Depends on actual access results
Other regions
Brazil	São Paulo	Relay	Depends on actual access results
Chile	Santiago	Relay	Depends on actual access results
South Africa	Johannesburg	Relay	Depends on actual access results
United Arab Emirates	Dubai	Relay	Depends on actual access results
Turkey	Istanbul	Direct	Depends on actual access results

How to read route names

For example, “Japan · Tokyo · IEPL” identifies the exit region and city first, followed by the route type. The entry point and exit location are not the same thing. After connecting locally, traffic may pass through intermediate links before reaching the exit. Don’t assume a route will perform well just because the cities look close on a map.

Coverage indicates the range of available regions; it doesn’t mean every destination will perform the same way. Even within one region, results can vary with carrier interconnections, where the destination service is hosted and the time of day. Check that the region suits your needs separately from whether the task runs smoothly, rather than judging by the node name alone.

PATH NOTES

Route types and cost differences

IEPL, relay and direct routes describe different network setups, not a universal performance ranking. The notes below explain how each type works; assess the actual route using the dashboard and your own use case.

Using a dedicated link

IEPL

IEPL generally refers to an international Ethernet private line. For cross-border access, a provider may use a dedicated line for the international segment, so that part of the journey does not rely entirely on ordinary public internet peering. This describes only part of the connection; it does not mean every link from your device to the destination website uses a private network. Local access and the route from the exit to the destination can still affect your experience.

Dedicated lines typically involve leasing, access and maintenance costs, which often means more resources are invested than with a public internet exit alone. They may be worth testing for sustained video meetings, remote desktops and extended collaboration. Choose one because it works better for your tasks, not because the name promises a lag-free connection. Check performance during the hours you actually use it, including evenings.

path: IEPL / check: performance in your actual workflow

Routing through an intermediate node

Relay

A relay adds a forwarding node between your device and the exit, separating the access path from the exit path. Choosing an entry point and adjusting the peering route can help accommodate different local networks. Passing through an intermediate node does not necessarily mean a worse experience; avoiding poor public internet peering may make your actual tasks run more smoothly.

Relay routes require additional entry points, forwarding resources and connections to be maintained. Costs depend on resource procurement and route design, so the name alone cannot tell you how a relay compares in price with every dedicated-line product. Relays may be worth trying for everyday browsing, document collaboration and streaming. To compare them, keep the exit region fixed and change only the route type. Check whether pages load, playback stays uninterrupted or file transfers improve, rather than changing several things at once.

path: Relay / check: how the entry and exit work together

Connecting directly to a public internet exit

Direct

Direct usually means the client connects to the exit service over the public internet without an additional relay entry point provided by the service. “Direct” describes the deployment, not a shorter physical distance or a guaranteed speed boost. Carrier routing may take a longer path, and international peering can vary by time of day. An exit that looks close on a map may not be the best fit for your current network.

Direct routes have fewer relay deployment components and a simpler resource structure in many cases, but servers, exit traffic and maintenance still have costs. They may suit users with good local public internet peering and tasks that are not highly sensitive to brief fluctuations, and can serve as an alternative to other routes. If browsing and downloads meet your needs, don’t rule one out just because the route name sounds basic. If sustained tasks are unreliable, compare relay or dedicated-line routes.

path: Direct / check: local public internet peering

SELECT BY TASK

Choose an exit by use case

First choose a region that meets the destination service’s requirements, then compare connection paths. Keeping a suitable everyday route and a backup route is easier to manage than repeatedly browsing the entire directory.

Everyday browsing

For research, reading websites and messaging, start with a regular exit in a suitable region. Open sites you use often and check that images, scripts and attachments load properly. Seeing the homepage is only a basic check: page resources may come from different services, so test internal pages and familiar features for a more reliable assessment.

If you don’t need a specific region, compare nearby locations first, but don’t treat geographic distance as the deciding factor. If one site acts up, check whether other sites work before changing routes. An issue on just one page may be caused by the destination site, browser cache or account status.

Streaming

First check the content’s region and your account’s terms, then choose an exit accordingly. Opening the platform, viewing a title’s details and playing it continuously are separate checks. Test the specific content you plan to watch and keep playback running; access to the homepage alone doesn’t confirm availability.

If playback stops, pause large file transfers on other devices and compare other routes in the same region. If the platform shows a region or proxy notice, consider your account terms and the platform’s policies; changing the city name alone is no guarantee of a fix. Content licensing and exit detection can change, so this page does not guarantee ongoing access to any particular title.

Accessing AI tools

Before using tools such as ChatGPT, Claude or Gemini, check which regions the platform supports and whether your account is eligible. A network connection provides an access path; it does not replace the platform’s account, payment or usage rules. Once you reach the chat interface, test your usual workflow, including prompts, streaming responses and file uploads.

Keep the exit region consistent during longer tasks, and avoid switching frequently while generating, uploading or signing in. If a verification prompt appears, follow the platform’s process rather than repeatedly switching between regions. For help distinguishing connection issues from account issues, see AI tool access guide.

Gaming and interactive apps

Check the game server’s region, the client’s network requirements and the terms of service before choosing an exit. Sign-in, resource downloads and gameplay may connect to different destinations; reaching the launcher does not confirm that gameplay traffic is using the intended route. Check sign-in, matchmaking and gameplay separately.

Interactive apps usually depend more on a consistent response than on a fast one-off download. For testing, pause background updates, keep your local network conditions consistent and compare candidate routes to the same destination. ClipVPN’s region directory is not a compatibility list for individual games and should not be taken as a claim of game-specific optimization.

Work and remote collaboration

Video meetings, online documents, code repositories and remote desktops each have different network needs. For meetings, check that audio and video stay smooth; for documents, confirm edits sync; for code collaboration, try an actual pull or push. Test with tasks that reflect your work rather than relying on a webpage loading as the sole check.

If your organization has network policies, check device management and access requirements before changing personal client settings. Keep the route stable once a meeting or remote session starts; if you need to switch, allow time to reconnect. Unlimited simultaneous devices are supported, but devices sharing a network can still affect one another. First rule out local uploads, downloads and wireless interference.

VERIFY / KEEP / REVIEW

Connection checks and route maintenance

Record your test conditions clearly so you don’t have to guess from scratch when troubleshooting. The steps below apply both when importing a subscription for the first time and when checking again after changing local networks.

Update your subscription before comparing the route list

The website directory is a reference; routes available in the client come from your subscription. If the two differ, check your subscription details in the dashboard first, then use the client’s subscription update feature. Region names, grouping and client display formats may differ; a name mismatch alone does not indicate a connection problem. Get your subscription and client from the dashboard, and don’t post subscription contents in public discussions.

Keep conditions fixed and compare real tasks

Use the same device, local network and destination service while switching between candidate routes. If you also change devices, Wi-Fi and exit regions, it’s hard to tell which change made the difference. If something goes wrong, note the time, client message, route name and affected task. Share those details in a support ticket in the dashboard; don’t include your password or full subscription contents.

Separate a successful connection from a successful task

A connected status in the client only confirms that the relevant connection process has been established. The destination service may still be affected by account status, regional rules, website maintenance or the browser environment. First check whether only one app is affected; if other tasks work, start with that app’s message. If several tasks fail at once, check the local network, client settings and backup routes.

Keep a backup route, but avoid switching repeatedly mid-task

Once you find a suitable everyday exit, keep another route with a different path as a backup. There’s no need to chase changing node names; compare routes again only when task performance changes. Switching exits during an upload, meeting or remote session may require reconnecting, so save your work first. For platform-specific setup, read the Getting started guide; for general troubleshooting, visit the Help center.