ROUTE PROFILES
How three route types work
Route names describe how data is organized between the local entry point and the international exit. Prices, stability and use cases vary, so do not choose based on city name alone.
IEPL
Dedicated entry
IEPL
An IEPL route places the local entry point and international exit on a relatively independent cross-border link. Compared with ordinary public-network paths, it passes through fewer public network nodes and offers more predictable routing. Its main value is not identical performance for every destination, but less route drift, congestion propagation and connection rebuilding during busy periods.
This type of route suits ongoing meetings, remote desktops, long file transfers, browser-based AI chats and other work that depends on connection continuity. When switching pages frequently, keeping multiple sessions open or submitting longer tasks, consistent connectivity is usually more important than a short-term peak.
Dedicated-link resources cost more to deploy and maintain than ordinary public-network paths, so they are often prioritized for common entry points such as Singapore and Hong Kong. If the target service is in North America or Europe, also consider whether the exit region matches; a closer entry point does not guarantee the account region will be identified correctly.
RELAY
Route optimization
Relay
A relay route first sends the connection to an intermediate entry point with more suitable location and network conditions, then connects to the target region from there. By splitting the cross-border path, it can avoid some public-network segments that are prone to congestion or frequent changes. Relay does not necessarily mean passing through more unrelated nodes; the key is whether the intermediate entry point improves the latter part of the route.
Relay routes suit everyday browsing, content streaming, software downloads, developer documentation and routine collaboration. They often balance coverage, cost and stability, and usually offer a wider choice of cities. When the destination is clear, choose a relay entry point in the same or a nearby region as the target service.
A relay connection consists of multiple segments, and a routing change in any one of them can affect the overall experience. If pages open normally but media repeatedly stalls, do not keep reconnecting to the same city; compare another route type in the same region instead.
DIRECT
Public-network direct
Direct
A direct route connects the current network straight to the international exit without adding a dedicated relay entry point. Its structure is simpler and suits destinations where the local network already has a smooth route. It also makes it easier to determine whether an issue comes from the local network, the cross-border path or the target website.
For everyday web access, text messaging, document searches and temporary region changes, start with a nearby direct entry point. If the connection is stable and the target service identifies the region correctly, there is no need to keep switching just because another route has a different label. A usable, sustainable entry point is more valuable than a complicated route name.
Direct routes are more exposed to changes in local carrier networks and international public-network routing. If the same entry point performs very differently at different times, switch to a relay or IEPL route in the same region instead of moving straight to a more distant country. This makes it easier to keep the account region and content region consistent.
Cost and use cases
Route cost does not directly determine suitability
Dedicated routes focus on predictable paths, relays on coverage and route optimization, and direct routes on simplicity. A higher-cost route is not suitable for every destination, and the closest entry point may not meet a platform's regional requirements. Judge the use case first, then choose the region and route type; this is usually more effective than sorting by name alone.