GLOBAL ROUTE DIRECTORY

Global Locations and Route Structure

CacaVPN provides cross-border network acceleration subscriptions covering 90+ countries and 200+ routes. The directory is organized by destination and transport structure, making it easier to choose based on the target service, local network, and time of use.

Start Free View Plans
90+ countries 200+ routes Unlimited devices 60-day refunds

Regional directory

Featured Routes by Region

The table below explains how the route directory is organized by region and connection structure. Actual availability is determined by the subscription list in the client after signing in. Streaming platforms continually update regional detection rules, so if results change, switch to another route in the same destination region and test again.

Coverage 90+ countries
Route count 200+ routes
Supported platforms Windows / macOS / iOS / Android / Linux
Country or region City Route type Streaming support
Asia-Pacific
Japan Tokyo IEPL Supported
Japan Osaka Transit Supported
Hong Kong, China Hong Kong IEPL Supported
Singapore Singapore IEPL Supported
South Korea Seoul Transit Supported
Taiwan, China Taipei Transit Supported
Malaysia Kuala Lumpur Direct Supported
Thailand Bangkok Direct Supported
North America
United States Los Angeles IEPL Supported
United States San Jose Transit Supported
United States Seattle Direct Supported
United States New York Direct Supported
Canada Toronto Transit Supported
Canada Vancouver Direct Supported
Europe
United Kingdom London Transit Supported
Germany Frankfurt Transit Supported
France Paris Direct Supported
Netherlands Amsterdam Direct Supported
Italy Milan Direct Supported
Spain Madrid Direct Supported
Other regions
Australia Sydney Transit Supported
New Zealand Auckland Direct Supported
United Arab Emirates Dubai Direct Supported
Brazil São Paulo Direct Supported
South Africa Johannesburg Direct Supported

Route architecture

IEPL, Transit, and Direct Connections

Route names describe how a cross-border connection is structured, not a single speed tier. To determine whether a route suits the task, consider the local network, destination region, time of access, and the target service’s connection behavior together.

IEPL

IEPL: More Controlled Paths

IEPL uses a relatively fixed cross-border path between the entry point and destination. Its main benefit is reducing unpredictable routing changes on public networks. For sustained transfers, video meetings, file synchronization, or work that depends on a stable session, predictable routing is often more important than a peak speed measured in a single connection test. It suits tasks that are sensitive to continuity and costly to interrupt.

Dedicated-route resources generally cost more to deploy and maintain than ordinary public paths, so they are best reserved for important tasks rather than selected permanently by name alone. For services in Asia, first test a nearby IEPL route. For North American services, compare the actual page response and session behavior of a North American IEPL route with a local transit route.

RELAY

Transit Routes: Adjusting the Path Between Entry and Exit

A transit route first connects to an intermediate access point before continuing to the destination region. Its purpose is not simply to add another hop, but to avoid an underperforming public path between the local carrier and the remote data center. When the transit point is well chosen, the access and international segments can use better-suited paths, reducing the effect of route instability on the overall session.

These routes suit everyday browsing, common online services, and tasks that require an exit in a particular region. Different local networks may perform differently with the same transit entry, so keep alternative routes in the same region available. If a route connects but page resources do not load completely, first switch to another transit entry in the same region before deciding whether to try IEPL or direct access.

DIRECT

Direct Routes: Simple Paths, More Exposure to Public Routing

A direct route connects from the local network straight to a server in the destination region, without a dedicated transit entry. Its structure is straightforward and works well when the local network already has good connectivity to the destination. It also serves as a useful comparison against IEPL or transit routes in the same region. Fewer hops do not guarantee better speed in every environment; results still depend on the carrier’s international exit and the remote return path.

Direct resources typically cover more countries and cities and have a different cost structure from dedicated routes, making them useful for expanding regional choices. For distant services, if pages load slowly, sessions drop, or resources remain incomplete, try a transit route in the same region. If the issue affects only one application, also check the client’s split-routing rules instead of changing countries immediately.

Selection policy

Choosing Routes by Use Case

Do not choose a route based only on the country name. First identify the target service’s region, then select a route structure that matches the task’s needs for continuity, regional detection, and interactive response.

Everyday Browsing

Everyday websites, research, and common online services usually depend most on consistent page response. Start with a nearby transit route; if the public path from the local network to that region is stable, direct access may also work well. Avoid frequent cross-region switching, since search results, account security checks, and content language may change with the exit region. If one website fails to open, test another route in the same region before changing countries.

Streaming

For streaming, first choose an exit in the region associated with the content, then check whether the platform detects that region correctly. Opening the home page successfully does not mean all content has the same rights coverage; account region, content licensing, and device location can also affect the result. If playback buffers, test IEPL and transit routes in sequence within the same region rather than switching countries first. If the platform reports a regional change, re-establish the app session and check again.

AI Tools

AI tools often involve continuous requests for sign-in, chat, file uploads, and long responses. Choose a region supported by the target service, then compare IEPL and transit routes in that region for session continuity. If the sign-in page opens but chat requests fail, clear the old page session and reconnect. If only the desktop client is affected, check whether the app is included in the client’s proxy rules. Frequent region changes may also trigger account-side region checks, so keep the exit region consistent whenever possible.

Gaming Connections

For gaming, distinguish between the login service, matchmaking service, and actual game region first. After choosing a destination that matches or is near the game’s server region, test the route before starting a full match. IEPL or transit may improve some public-path issues, but final performance still depends on the local network, game server, and carrier interconnection. If login works but match connectivity fails, check whether the game process is covered by the relevant rule and avoid changing the exit during a session.

Cross-Border Work

Remote meetings, code repositories, corporate portals, and file synchronization depend more on sustained connectivity. Test an IEPL or transit route based on the region of the business service, and verify the connection before an important meeting or upload. Keeping the same exit region during work reduces repeated changes to the authentication environment. If the company system specifies an exit region, follow internal policy. For important files, keep a local copy and avoid switching routes during transfer.

Route diagnostics

Diagnosing Connection Issues

Switch routes in a reproducible order instead of randomly changing countries. Change only one condition at a time so you can distinguish differences caused by the local network, route structure, regional detection, or application rules.

Unable to establish a connection

Try another route in the same region

Keep the destination country unchanged and switch between IEPL, transit, and direct routes. If no route in the region connects, try another local network or restart the client. This first rules out a temporary issue with a single path and avoids changing the exit region too soon.

Connected, but pages behave unexpectedly

Check whether the app is using the new exit

After switching routes, reopen the browser or target app so the old connection is not reused. If only one app is affected, check the client mode and split-routing rules. If every page fails to load, test another route in the same region.

Regional detection is not as expected

Re-establish the account session

Some platforms use account details, session history, and device information to determine a region. After confirming the exit region, sign out of the old session and sign in again, then check the content catalog. Changing routes while keeping the old page open may not produce an immediate change in the detected region.

The connection drops during use

Prioritize routes with more predictable paths

When an ongoing task is interrupted, switch from direct access to a transit or IEPL route in the same region, and check whether the local wireless network is stable. Avoid frequent exit changes after a remote meeting or file transfer has started; save the current work before switching.

Coverage policy

Coverage and Usage Boundaries

CacaVPN’s route directory covers 90+ countries and 200+ routes, providing alternatives for different destinations and local networks. Route count cannot replace real-world testing: different entries in the same city may use different carrier paths, and the same route may perform differently across local networks. The client therefore keeps multiple options in each region so users can switch according to current conditions.

This service supports Windows / macOS / iOS / Android / Linux and allows use on unlimited devices. Devices may use routes in different regions, but keeping the same region is usually easier for managing sessions tied to one account or work task. No email address is required to get started; use a username and password. Review the plan terms before purchase. Paid services are eligible for a 60-day no-questions-asked refund.

View Quick Start Get the Client
Start Free