Skip to main content
A new tunnel is inactive. It turns healthy when its first process connects, and inactive again when its last process stops. telnyx-edge tunnel get shows the status and the number of connected processes.

​
Replicas

Any number of hosts can run the same token. Every process serves the same routes, private services Preview, and public hostnames Preview. Telnyx spreads requests across the connected processes in turn. When one process stops, the next request goes via another, and no request fails. With dc1-tunnel-a stopped, the tunnel stays healthy on the one process left:
Workstation
Output
A process whose connection drops reconnects on its own and serves again within seconds.

​
Routes

A function on the Network picks up a route within about a minute of its creation. A route that is inactive turns active again when a process connects.

​
Tunnel Token

The token is the only credential the tunnel process holds. Telnyx returns it once, when the tunnel is created or its token is rotated, and stores only a hash of it. telnyx-edge tunnel get and telnyx-edge tunnel list never print it. The token lets a process serve the tunnel and nothing else. It is not an API key. The Telnyx API answers a request that carries it with 401 Unauthorized, so a host that holds it cannot create, change, or delete resources. Rotating the token issues a new one and invalidates the old one:
Workstation
Output
A process on the old token stays connected and keeps serving. When it reconnects, Telnyx refuses it, and the process exits:
Tunnel host

​
Deletion

A tunnel that a route names cannot be deleted. telnyx-edge tunnel delete lists the routes instead:
Output
Once the tunnel is deleted, Telnyx refuses its token.