ROUTE TYPES
How Route Types Work
The name describes only the entry point. What affects the experience is which network segments carry data from the local network, where it enters the international link, and which exit region the target service sees.
IEPL
Stability first
IEPL Dedicated Line
An IEPL dedicated line places key cross-border transmission segments on a more controllable enterprise-grade network. Compared with paths that rely entirely on the public internet for each hop, it generally prioritizes consistent routing and more predictable performance during congested periods. The client still connects through the local network, while core transmission segments are designed to avoid volatile public paths where possible.
This route type suits long meetings, remote desktops, repository synchronization, cloud consoles, and work tasks that require persistent sessions. Its value is not a better-looking momentary result in one test, but fewer disruptions caused by frequent path changes. Resource allocation and network maintenance generally cost more than ordinary relay and direct routes, so reserve it for tasks with high stability requirements.
RELAY
Balanced path
Relay Route
A relay route first sends the connection to an intermediate node with better access quality, then forwards it toward the target region. The relay acts as a path organizer: one segment runs from the local network to the entry point, and another runs from the entry point to the exit. This can avoid some less suitable direct paths and provide more flexibility when choosing an exit region.
It suits everyday browsing, file collaboration, streaming, and access to most AI tools. More relays are not always better; extra hops also increase routing complexity. Choose based on whether the actual task can complete consistently, not just on the route name. If a relay entry performs poorly on the current network, try another entry in the same region before changing the exit country.
DIRECT
Simple path
Direct Route
A direct route connects the current network straight to an exit in the target region without a dedicated access relay in between. Its structure is simple and works best when the local network already has a good path to the target region. Because public-internet paths vary by provider, time, and location, the direct experience depends more heavily on the user’s current access conditions.
This route type suits temporary access to content for a specific region, ordinary browsing, or use as a backup alongside IEPL and relay entries in the same region. Direct routes organize network resources more simply and generally cost less than dedicated lines, but cost alone does not determine suitability. If an app is sensitive to persistent connections, complete a full task once before making the route a regular entry point.
PATH MODEL
Entry Point, Transit Segment, and Exit
Local network
→
Access entry
→
Cross-border transit
→
Regional exit
→
Target service
The entry point determines where the connection begins, the transit segment determines how data reaches the exit, and the exit determines which region the target website identifies. Separate these stages when choosing a route. A failed request does not necessarily mean the entry is unavailable; the target service may still be using an old account region, cache, authorization catalog, or app routing rule.