> ## 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.

# Routes

> How a route on a Network sends a subnet to a tunnel.

A tunnel belongs to no [*Network*](https://developers.telnyx.com/docs/network/overview.md). A route attaches it, and so does a [private service](https://developers.telnyx.com/docs/network/tunnel/features/private-services.md) Preview. A route names a *Network*, a CIDR, and the tunnel as its next hop, and traffic on that *Network* to an address in the CIDR goes via the tunnel.

This route sends `10.20.0.0/16` on `acme-prod` to `chicago-dc`:

```bash Workstation theme={null}
telnyx-edge network route add acme-prod 10.20.0.0/16 --tunnel chicago-dc
```

The CIDR follows the [route rules](https://developers.telnyx.com/docs/network/routes.md) of the *Network*.

* One tunnel serves routes on several *Networks*. Each *Network* reaches only the CIDRs that its own routes send to the tunnel, and traffic never passes from one *Network* to another through it.
* A function on the *Network* picks up a new route within about a minute, without a redeploy.

## Decided on the *Network*

The route is the decision, and it is made on the *Network*, not at the edge of the user's network. Deleting the route cuts the CIDR off. The tunnel stays connected, and nothing changes within the user's network:

```bash Workstation theme={null}
telnyx-edge network route delete 1a826484-8bfe-4346-b9fc-26aa70a22ccc && telnyx-edge tunnel get chicago-dc
```

```text Output theme={null}
Deleted route 1a826484-8bfe-4346-b9fc-26aa70a22ccc
NAME         STATUS    CONNECTIONS
----------   -------   -----------
chicago-dc   healthy   2
...
```

Both tunnel processes stay connected, and the function's requests to `10.20.3.7:8080` then fail with `TypeError: fetch failed`.