Multi-hop uses more than one authorized node. Public route availability and end-to-end leak acceptance remain unverified.
Before you start
Use the access and features actually assigned to your account. Keep a rollback or recovery route before changing existing service settings.
Steps
- Confirm that the specific route is approved and currently available.
- Record its entry, intermediate hop and intended egress without exposing keys.
- Use the supplied route controls; do not improvise gateways or public proxies.
- During an authorized test, verify traffic path, DNS, IPv6 handling and behavior when a tunnel is lost.
Verify the result
The intended path and failure behavior are demonstrated. More hops alone do not establish anonymity or a stronger privacy guarantee.
Help and related information
Contact support, service status, and Customer Access. Never send passwords or recovery codes.