# Telnyx Compute: Network — Full Documentation
> Complete page content for Network (Compute section) of the Telnyx developer docs (https://developers.telnyx.com).
> This file: https://developers.telnyx.com/docs/development/llms/compute-network-llms-full-txt · Root index: https://developers.telnyx.com/llms.txt

## Network

### Overview

> Source: https://developers.telnyx.com/docs/network/overview.md

The user's dedicated Telnyx resources join a **Network** from any product suite that offers an attachment. Cloud VPCs, data centers, and hosts outside Telnyx join the same *Network*. Each *Network* has its own [routes](/docs/network/routes) and is isolated from every other *Network*.

  The diagram shows traffic entering a *Network* from devices over WireGuard,
  applications via an Edge Compute network binding, and SIM fleets via a
  Private Wireless Gateway. An Agent Gateway for agents is coming soon. The
  *Network* is the user's VRF and holds its interfaces. Routing tables, IP
  rules, and firewall rules on the *Network* are coming soon. Traffic leaves for
  the user's networks outside Telnyx via WireGuard, a Virtual Cross Connect, or
  a Tunnel to the user's site with no change to its router or firewall. A
  Tailscale Subnet Router lets a Tailscale network reach the *Network* the
  other way. IPsec connections are coming soon.

---

### Networks

> Source: https://developers.telnyx.com/docs/network/networks.md

A [*Network*](/docs/network/overview) connects the user's dedicated Telnyx resources to the networks the user runs outside Telnyx. Each *Network* has its own routes and is isolated from every other *Network*.

## Create a *Network*

Send a name for the *Network*:

```http
POST /v2/networks
```

```json
{
  "name": "acme-prod"
}
```

The response contains the stable *Network* ID:

```json
{
  "data": {
    "name": "acme-prod",
    "created_at": "2026-10-12T18:00:54.022171Z",
    "updated_at": "2026-10-12T18:00:54.022171Z",
    "id": "264fe95b-73a8-4a26-a979-2d875e934f4e",
    "record_type": "network"
  }
}
```

Store `data.id`. Attachment APIs use this UUID as their `network_id`.

## List and retrieve *Networks*

List the *Networks* associated with the account:

```http
GET /v2/networks
```

Retrieve one *Network* by ID:

```http
GET /v2/networks/{id}
```

Use `filter[name]` with the list operation to find a *Network* by name.

## Rename a *Network*

Renaming a *Network* does not change its ID or its attachments:

```http
PATCH /v2/networks/{id}
```

```json
{
  "name": "acme-production"
}
```

## Inspect attached interfaces

List the interfaces attached to a *Network*:

```http
GET /v2/networks/{id}/network_interfaces
```

Filter the result by `name`, `type`, or `status`. WireGuard Interfaces have the type `cloud_vpn`, and Tailscale Subnet Routers `tailscale_subnet_router`:

```http
GET /v2/networks/{id}/network_interfaces?filter[type]=cloud_vpn
```

```json
{
  "data": [
    {
      "name": "acme-prod-wg",
      "status": "provisioning",
      "created_at": "2026-10-12T18:00:54.274991Z",
      "region_code": "ashburn-va",
      "id": "df98c084-da39-4dd3-9134-da38d1990eec",
      "updated_at": "2026-10-12T18:00:56.362170Z",
      "network_id": "264fe95b-73a8-4a26-a979-2d875e934f4e",
      "type": "cloud_vpn",
      "region": {
        "code": "ashburn-va",
        "name": "Ashburn VA, US",
        "record_type": "region"
      },
      "record_type": "network_interface"
    }
  ],
  "meta": {
    "total_pages": 1,
    "total_results": 1,
    "page_number": 1,
    "page_size": 25
  }
}
```

## Delete a *Network*

Delete the *Network*'s interfaces first. A *Network* that still has interfaces returns `409` with error code `10021`, Resource in use. Then delete the *Network* by ID:

```http
DELETE /v2/networks/{id}
```

---

### Routes

> Source: https://developers.telnyx.com/docs/network/routes.md

A [*Network*](/docs/network/overview) holds two kinds of route:

- A `static` route is one the user adds. Its next hop is a [Tunnel](/docs/network/tunnel/features/routes).
- An `attachment` route is one that an attachment installs, such as the subnet of a [WireGuard Interface](/docs/network/wireguard-interfaces). It cannot be deleted on its own.

The routes of `acme-prod` hold one of each. The attachment route carries the ID of its WireGuard Interface:

```http
GET /v2/network_routes?filter[network_id]=d8a7e0b1-2d64-4d62-aeb2-b77465835059
```

```json
{
  "data": [
    {
      "id": "38aa69b4-9a4a-4181-bb92-e1571cc14533",
      "cidr": "10.20.0.0/16",
      "next_hop": { "type": "tunnel", "id": "6afe50f3-bcff-48e9-93e8-4a906a91067e" },
      "origin": "static",
      "status": "active",
      ...
    },
    {
      "id": "03aefa24-609b-4fce-b88a-0dc9afeed95d",
      "cidr": "172.27.0.0/24",
      "next_hop": { "type": "wireguard_interface", "id": "03aefa24-609b-4fce-b88a-0dc9afeed95d" },
      "origin": "attachment",
      "status": "active",
      ...
    }
  ]
}
```

## CIDRs

Each route takes a canonical IPv4 CIDR, such as `10.20.0.0/16`. A *Network* holds each CIDR once, and the API refuses a second route for the same CIDR. It also rejects a route that overlaps a subnet already on the *Network*, such as the subnet of its WireGuard Interface.

## Reserved Ranges

Telnyx reserves these ranges on every *Network*. The API rejects a route that overlaps any of them, and so does a [Tailscale Subnet Router](/docs/network/tailscale-subnet-router/concepts/routes) for the subnets it advertises:

- `0.0.0.0/8`, and with it the default route
- `127.0.0.0/8`, loopback
- `169.254.0.0/16`, link-local
- `224.0.0.0/3`, multicast and reserved
- `100.64.0.0/10`, shared address space. Telnyx uses it on the *Network*, for example for [Private Wireless Gateway](/docs/network/gateways/private-wireless-gateway) ranges, and Tailscale uses it for tailnet addresses.
- `172.27.254.0/24` and `198.18.0.0/20`, the addresses of Tailscale Subnet Routers

---

### Coverage

> Source: https://developers.telnyx.com/docs/network/coverage.md

Networking resources are not available at every Telnyx location. `GET /v2/network_coverage` lists each location and the resources that can be created there.

## Locations

Each result has a `location` object:

| Field    | Value                                                     |
| -------- | --------------------------------------------------------- |
| `region` | `AMER`, `EMEA`, or `APAC`                                 |
| `site`   | An area within the region, for example `ORD` in `AMER`    |
| `pop`    | A data center within the site, for example `CH1` in `ORD` |
| `name`   | A readable name, for example `Chicago IL, US`             |
| `code`   | The location's ID, for example `chicago-il`               |

A WireGuard Interface takes the location's `code` as its `region_code`.

`available_services` lists the resources that can be created at the location. Values include `virtual_cross_connect`, `cloud_vpn` (WireGuard Interface), `tailscale_subnet_router`, and `private_wireless_gateway`.

## Query coverage

Filter by resource:

```http
GET /v2/network_coverage?filter[available_services][contains]=cloud_vpn
```

Filter by resource and region:

```http
GET /v2/network_coverage?filter[available_services][contains]=cloud_vpn&filter[location.region]=AMER
```

Filter by region:

```http
GET /v2/network_coverage?filter[location.region]=EMEA
```

The second query returns the two AMER locations that offer WireGuard Interfaces:

```json
{
  "data": [
    {
      "available_services": [
        "private_wireless_gateway",
        "virtual_cross_connect",
        "cloud_vpn",
        "ng_private_wireless_gateway"
      ],
      "location": {
        "region": "AMER",
        "site": "IAD",
        "pop": "DC2",
        "name": "Ashburn VA, US",
        "code": "ashburn-va"
      },
      "record_type": "network_coverage"
    },
    {
      "available_services": [
        "virtual_cross_connect",
        "cloud_vpn"
      ],
      "location": {
        "region": "AMER",
        "site": "ORD",
        "pop": "CH1",
        "name": "Chicago IL, US",
        "code": "chicago-il"
      },
      "record_type": "network_coverage"
    }
  ],
  "meta": {
    "total_pages": 1,
    "total_results": 2,
    "page_number": 1,
    "page_size": 25
  }
}
```

## Virtual Cross Connect coverage

A Virtual Cross Connect has two ends: a Telnyx PoP and a cloud provider region. `GET /v2/network_coverage` covers only the Telnyx end. `GET /v2/network_agents_gateway/vxc/coverage` lists the pairs a Virtual Cross Connect can join, with the bandwidths available for each.

List the cloud provider regions that a Virtual Cross Connect from the Telnyx `CH1` PoP can reach:

```http
GET /v2/network_agents_gateway/vxc/coverage?filter[location.pop]=CH1
```

List the Telnyx PoPs that a Virtual Cross Connect to AWS can use:

```http
GET /v2/network_agents_gateway/vxc/coverage?filter[cloud_provider]=aws
```

The first query returns:

```json
{
  "meta": {
    "page_size": 50,
    "page_number": 1,
    "total_pages": 1,
    "total_results": 3
  },
  "data": [
    {
      "cloud_provider": "aws",
      "cloud_provider_region": "us-east-2",
      "location": {
        "region": "AMER",
        "site": "ORD",
        "pop": "CH1",
        "name": "Chicago IL, US",
        "code": "chicago-il"
      },
      "available_bandwidth": [50, 100, 200, 500, 1000]
    },
    {
      "cloud_provider": "gcp",
      "cloud_provider_region": "us-central1",
      "location": {
        "region": "AMER",
        "site": "ORD",
        "pop": "CH1",
        "name": "Chicago IL, US",
        "code": "chicago-il"
      },
      "available_bandwidth": [50, 100, 200, 500, 1000]
    },
    {
      "cloud_provider": "azu",
      "cloud_provider_region": "northcentralus",
      "location": {
        "region": "AMER",
        "site": "ORD",
        "pop": "CH1",
        "name": "Chicago IL, US",
        "code": "chicago-il"
      },
      "available_bandwidth": [50, 100, 200, 500, 1000]
    }
  ]
}
```

`available_bandwidth` is in Mbps.

---

## API Reference (Network)

### Networks

- [List all Networks](https://developers.telnyx.com/api-reference/networks/list-all-networks.md): Returns a paginated list of the private networks on your account, with support for filtering.
- [Create a Network](https://developers.telnyx.com/api-reference/networks/create-a-network.md): Creates a new private network, the container that links your WireGuard interfaces, gateways, and cross connects.
- [Delete a Network](https://developers.telnyx.com/api-reference/networks/delete-a-network.md): Permanently deletes the specified network from your account.
- [Retrieve a Network](https://developers.telnyx.com/api-reference/networks/retrieve-a-network.md): Returns the details of a single network by its identifier.
- [Update a Network](https://developers.telnyx.com/api-reference/networks/update-a-network.md): Updates the specified network's attributes and returns the updated network.
- [List all Interfaces for a Network.](https://developers.telnyx.com/api-reference/networks/list-all-interfaces-for-a-network.md): Returns a paginated list of the interfaces attached to the specified network, with support for filtering.
- [Delete Default Gateway.](https://developers.telnyx.com/api-reference/networks/delete-default-gateway.md): Removes the default gateway from the specified network.
- [Get Default Gateway status.](https://developers.telnyx.com/api-reference/networks/get-default-gateway-status.md): Returns the status of the default gateway configured on the specified network.
- [Create Default Gateway.](https://developers.telnyx.com/api-reference/networks/create-default-gateway.md): Creates a default gateway on the specified network, directing the network's outbound traffic through the chosen gateway.

### Network Routes

- [List all Network Routes](https://developers.telnyx.com/api-reference/network-routes/list-all-network-routes.md): Lists the routes of the account's Networks. A Network's list is its effective route table: the routes added with `POST /network_routes` (`origin` `static`) and…
- [Create a Network Route](https://developers.telnyx.com/api-reference/network-routes/create-a-network-route.md): Adds a route to a Network. Traffic on the Network to an address in `cidr` goes via `next_hop`. With a tunnel as the next hop, functions on the Network reach th…
- [Retrieve a Network Route](https://developers.telnyx.com/api-reference/network-routes/retrieve-a-network-route.md): Retrieves a route and its status.
- [Delete a Network Route](https://developers.telnyx.com/api-reference/network-routes/delete-a-network-route.md): Deletes a route that was added with `POST /network_routes`. Traffic to its CIDR stops going via the next hop at once. Routes that an attachment installs (`orig…