Routes - Telnyx

A Network holds two kinds of route:

A static route is one the user adds. Its next hop is a Tunnel.
An attachment route is one that an attachment installs, such as the subnet of a WireGuard Interface. 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:

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

{
  "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 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 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

​CIDRs

​Reserved Ranges

CIDRs

Reserved Ranges