Routed VLAN Interfaces

Routed VLAN Interfaces allow you to route IPs and Subnets to one of your VLAN's via an IRB interface. Once routed to a VLAN, the subnet's IPs become available for use by any device in the VLAN. This is a typical setup for hypervisor-like environments, such as K8s deployments.

Routing IPs to a VLAN

Before you can route IPs to the VLAN interface, you need to Create a VLAN on your account. Once created, any subnet of IPs on your account that are unassigned can be routed to your VLAN.


The update endpoint changes the VLAN setup to match the exact state of values given. For example, if you have port 789 and 567 already in the VLAN and you want to route the IP assignment 123 to the VLAN interface you will need to pass in all 3 values. If you omit the port IDs, they will be remove from the VLAN. To update your VLAN use the PUT /vlan/{vlanId} endpoint.

curl --request PUT \
     --url{vlanId} \
     --header 'Accept: application/json' \
     --header 'Content-Type: application/json' \
     --header "X-API-KEY: $API_KEY" \
     --data '
     "portIds": [
     "ipIds": [

Using the IPs with your Server

Once routed to the VLAN, you need to run commands on the server(s) in your VLAN to finish making an IP available to those server(s). In hypervisor-like deployments, the hypervisor typically handles this for you. If you are manually routing the IPs yourself, you can use the interface IPs the same way you configure your server to accept statically routed IPs.

What’s Next