type / path
Dedicated routes, relayed, and direct connections
Route types describe how traffic reaches the exit, not a performance ranking or client protocol. Routes labeled “relayed” may use different entry points, and a “dedicated” route still includes your local connection and the target service's network. Compare the full connection path.
type=iepl
IEPL
IEPL typically refers to an international Ethernet private line, with dedicated resources used for the cross-border segment. This can make that part of the route more controllable and reduce reliance on changes to public internet routing across borders. “Dedicated” describes the transport method; it does not mean one provider controls the entire path from your home network to the target website.
Worth considering when continuity matters, such as for longer work sessions. These routes typically involve higher resource procurement and maintenance costs than direct connections. That cost difference does not mean VPNQS charges an additional route fee; check the dashboard plans for availability and billing.
What to check: whether meetings, file transfers, or ongoing access feel more consistent through exits in the same region—not what the route label suggests.
type=transit
Relayed routes
A relayed route adds an entry node between you and the exit. The entry node forwards traffic to the target exit. This separates local access from the international exit, allowing routes to be selected for different network conditions. An extra hop does not necessarily mean a slower connection; what matters is whether the full route works better.
A good option for everyday browsing, media access, and comparing different entry points. Relayed routes require entry resources and onward connections, which typically cost more to maintain than a simple direct route with only an exit. The difference depends on the resources used. “Relayed” does not describe one standardized route.
What to check: whether your local connection is stable and whether you can complete your actual tasks after connecting to the target app.
type=direct
Direct routes
With a direct route, the client connects straight to the exit-side service without passing through a relay entry configured by VPNQS. The setup is relatively simple, and the cross-border path depends mainly on your local carrier and the public networks along the way. “Direct” does not mean the physical route is the shortest or that no other network equipment is involved.
A suitable option when the path from your local network to the target exit works well and you want an alternative connection method. Direct routes generally require no extra relay resources and have a simpler resource setup, but peak-time routing changes can affect performance more directly. If a direct route works for you, there is no need to switch just because of its label.
What to check: whether it meets your needs during your usual hours and provides a useful alternative to other route types if problems arise.
Compare route type and data plan separately
Route type determines the connection path; data plans determine how much you can use. Monthly plans are ¥9.9/month for 60GB, ¥18/month for 250GB, and ¥28/month for 500GB. Data resets monthly on your activation date; mid-cycle upgrades are prorated for the remaining days. A larger data plan does not make an individual route faster, and a connection issue does not necessarily come from your plan tier. See plan pricing for full billing details.