> ## Documentation Index
> Fetch the complete documentation index at: https://developers.telnyx.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Lifecycle

> The statuses of a Tailscale Subnet Router, from enrollment on the tailnet to deletion.

| Status | Meaning |
| - | - |
| `provisioning` | Telnyx is creating the router or applying a change. |
| `provisioned` | The router is on the tailnet and advertises its routes. The tailnet still approves them. |
| `failed` | Enrollment did not complete. The router keeps its addresses, and `PATCH` with a new key retries it. |
| `deleting` | Telnyx is removing the router. The record disappears once removal completes. |

The auth key is used at enrollment. Telnyx stores it encrypted until then and never returns it. A router stays on the tailnet it enrolled in. To join another tailnet, create a new router. `device_id`, `tailnet_name`, and `tailscale_ips` record the enrollment. The router also appears in the [*Network*](/docs/network/overview)'s interface list.

Deleting a router logs its machine out of the tailnet. The machine stays listed, expired, until the admin removes it.

## For the Tailnet Admin

* Use a pre-approved, tagged [auth key](https://tailscale.com/docs/features/access-control/auth-keys). A key that is expired, revoked, or already used fails enrollment.
* A [tagged](https://tailscale.com/docs/features/tags) machine has [key expiry](https://tailscale.com/docs/features/access-control/key-expiry) disabled by default. An untagged router stops working when its key expires, unless the admin [disables key expiry](https://tailscale.com/docs/features/access-control/key-expiry#disabling-key-expiry).
* Remove a deleted router's machine with **Remove** in the machine's menu.