NET-02 · Link Categories
IEPL, Relay, and Direct Routes
Route names describe the general way data is organized from the local entry point to the target exit. Each type has its own use cases, and the name alone cannot predict performance across every time, region, or network environment.
TYPE-A
IEPL
Entry
Dedicated Link
Exit
IEPL routes use international dedicated links provided by carriers to organize cross-border transmission, with relatively less reliance on the public network and generally more predictable routing. Their main value is greater control over the link: the arrangements between the entry, international segment, and exit are more consistent. They suit long video conferences, remote work, continuous transfers, and tasks that require connection continuity.
Dedicated links usually cost more to build and maintain than ordinary public-network paths, so providers must allocate resources across capacity, regions, and demand. IEPL is not automatically the best choice for every situation. If the target service is nearby and the local path to a direct exit is already suitable, routing through a dedicated link may add distance. Confirm the target region first, then consider the route type.
TYPE-B
Relay Routes
Entry
Relay Point
Exit
Relay routes first send the connection to a more suitable relay entry point, then use the relay network to reach the target region. They help improve less suitable public-network paths between the local network and a remote exit, so cross-regional access does not depend entirely on default routing. The relay location, entry network, and subsequent exit together determine the final path, which means different relay routes in the same country may suit different access environments.
These routes balance coverage and resource costs, making them suitable for everyday browsing, streaming, AI tools, and general office work. Their operational focus is the combination of entry and exit points, not just the exit city. If a relay route performs poorly on the current network, try another entry in the same region first. This keeps the target region while changing the first part of the route.
TYPE-C
Direct Routes
Local Network
Public-Network Path
Exit
Direct routes use the public-network path between the local carrier and the exit data center without an additional dedicated relay entry. Their structure is more straightforward and their regional coverage is easier to expand, making them suitable for less frequently accessed regions, web research, lightweight communications, and backup connections. When the local path to the target region is already good, a direct route may be the simplest effective option.
Direct routes are more sensitive to changes in local-carrier routing, and different access networks may take different paths. Results from other users should therefore not be treated as conclusions for your own network. Judge the route by the real task: whether pages keep loading, login sessions remain stable, and file transfers stay continuous. If direct access is unsuitable, switch to a relay or IEPL entry in the same region.
ROUTE-TYPE / DECISION RULE
Cost Differences and Use Cases
Route costs come from entry resources, international transmission, exit resources, and ongoing maintenance. IEPL requires a more clearly managed dedicated link and usually has higher resource costs; relay routes maintain a combination of entries and exits, balancing cost and coverage; direct routes mainly use public-network paths and help extend regional coverage. These differences explain why one subscription may include multiple route types rather than using one structure for every exit.
Users do not need to treat route types as a fixed ranking. The practical approach is to define candidates based on the target service, its region, and the current access network, then compare them using the same real task. For work, test meetings and file transfers; for streaming, observe playback; for AI tools, check login and continuous conversations; for browsing, check commonly used sites. The criteria should match the intended use.