IEPL, Relay, and Direct Routes
Route names describe how a connection is organized. Consider cost, stability, and local access conditions together rather than ranking routes by name alone.
IEPL
IEPL: A dedicated international connection
IEPL generally refers to an international Ethernet private line that carries connections between regions over a dedicated link. Compared with routes that rely mainly on public internet routing, this approach puts more emphasis on managing the connection path. It may suit use cases sensitive to sustained connectivity, such as remote work, longer video calls, or recurring web tasks during busy evening hours.
Dedicated-line resources typically cost more to procure and maintain, but that does not mean every part of the path—from your device to the destination website—uses a dedicated line. Your local wireless network, ISP, entry connection, and destination service all affect performance. Test with the apps you actually use during your usual hours, and check whether sessions stay connected and pages load without repeated retries. “Dedicated line” is not a guarantee for every connection.
Example: Singapore · IEPL
Example: Hong Kong · IEPL
RELAY
Relay: Routing through an intermediate node
A relay route sends the connection to an intermediate access point before forwarding it to the destination exit. It is not necessarily a shorter route; it uses inter-network connections to improve routing in some access environments. If the path from your local ISP to the destination region is less than ideal, a relay may be worth comparing.
Relay routes use access, forwarding, and exit resources. They typically involve more coordination and operating costs than a simple direct connection, though actual costs depend on routing and resource procurement. The extra hop also means more path conditions to consider. When browsing, streaming, or using AI tools, keep the exit region the same and change only the route type to see whether the difference comes from the route or the destination region.
Example: Japan · Relay
Example: Switzerland · Relay
DIRECT
Direct: Primarily using public internet routing
A direct route generally connects the client to the destination exit over the public internet, without an additional dedicated relay link. Its path is more straightforward and may suit locations with good connectivity to the exit region. Use it as a starting point for everyday reading, web searches, or general file access, then decide whether to keep it based on how your apps perform.
Compared with routes that use an additional relay or dedicated line, direct routes typically require simpler path resources. This does not indicate a separate price for any particular route in a VPNAct plan. Direct connections are not necessarily slower than relays; performance can vary by ISP and time of day. If a route works during the day but performs poorly in the evening, compare other paths on the same device and app rather than assuming the device is at fault.
Example: United States · Direct
Check the panel for available routes
These cost differences explain how route types work; they do not mean that each type is priced separately. See the plans page for plan pricing, included data, and billing details. Do not infer unlisted charges from route names.