PRIVATE CIRCUIT
IEPL Dedicated Line
IEPL usually refers to an international Ethernet private line. In a network architecture, an operator may use a dedicated line for a specific segment, distinguishing that segment from a typical public internet route. Keep in mind that your local network, access segment, and the path from the exit to the destination website may still use public networks. A “dedicated line” label does not mean the entire connection is reserved exclusively for you.
Best for: For work, extended interactive sessions, and streaming where a continuous connection matters, consider a dedicated line and assess its performance during your usual usage hours. Focus on whether you can complete tasks reliably, not just whether the connection starts. Evening congestion may occur on your local access network or at the exit; the label alone cannot pinpoint the cause.
Cost considerations: Dedicated lines typically require dedicated transmission resources and ongoing maintenance, so their infrastructure costs are generally higher than solutions using only public routes. Infrastructure costs do not directly determine your subscription price, nor do they mean every route performs the same. This page makes no promise of separate per-route pricing. Check the dashboard for availability.
RELAY PATH
Relay
A relay adds a forwarding step between you and the exit. Your client first connects to an access node, which then forwards the connection to the destination exit. This adjusts the access path; it does not change the destination website’s account rules. The relay entry location may differ from the final exit region, so distinguish entry and exit details in the dashboard.
Best for: A relay is worth comparing when the route from your local network to an international exit is poor. For international browsing, AI tools, or streaming, compare relay and other options in the same region. A relay adds a forwarding step, but may improve a route that would otherwise be congested or take a detour, so the number of hops alone does not determine which route is better.
Cost considerations: Relay routes require resources for the entry point, forwarding link, and exit, all of which need maintenance. Costs depend on the route design and resource quality, so relays are not always cheap or expensive. A relay is not automatically a dedicated line; count dedicated-line capacity only when the route details explicitly say so.
DIRECT PATH
Direct
Direct usually means your client connects to the exit server without a separate service-level relay entry. Direct does not mean the physical route is straight: data still passes through access networks and carrier routing. An exit that seems geographically close may take a detour because of peering arrangements. Map distance can offer context, but cannot replace testing the connection.
Best for: If the public route from your local network to the exit performs well, direct is a straightforward option to understand and troubleshoot. Try it first for everyday browsing, quick research, and file transfers. If it repeatedly stalls during your usual usage hours, compare a relay or dedicated line while keeping the target region the same, rather than cycling through countries.
Cost considerations: Direct routes have a relatively simple service topology and generally use fewer intermediate forwarding resources, but exit bandwidth, network peering, and maintenance still cost money. Direct does not mean low quality, nor does it imply a fixed performance ceiling. Consider your local network, the destination website, and the time of use together.