DOCUMENTATION / PLATFORM
Understand the connection.
RouteLab separates the customer portal from the machines that manage networking. Your service has a desired configuration and a separately observed state. A saved change is pending until the network worker verifies it.
Connection model
- Transport
- WireGuard, using a public key you supply
- Routing
- eBGP between your private ASN and the RouteLab edge
- Inbound policy
- Only your exact allocated prefixes
- Source validation
- Peer-bound WireGuard AllowedIPs and nftables
- Global export
- Operator-authorized aggregates only
- Provisioning
- Asynchronous, after a verified Stripe webhook
Before ordering
Generate your WireGuard key pair locally and retain the private key. After payment and resource allocation, your dashboard provides the real tunnel addresses, RouteLab public key, peer ASN and allocated prefixes. Never paste a private key into RouteLab.
Products are available only when an operator has configured authorized inventory. Peering, labs and reverse DNS require their own infrastructure; an unconfigured feature does not imply a running service.
Products are available only when an operator has configured authorized inventory. Peering, labs and reverse DNS require their own infrastructure; an unconfigured feature does not imply a running service.
Reading service state
- SYNCHRONIZED
- The desired revision was verified on the edge
- PENDING
- A newer desired revision has not been applied
- STALE
- The most recent observation is more than three minutes old
- UNKNOWN / UNOBSERVED
- No current verified observation is available
- ONLINE
- A recent WireGuard handshake; not a guarantee of BGP reachability