Reserved Public IPv4 Addresses

The Reserved IP feature is designed for the reservation of individual public IPv4 addresses within a specific region. Because a Reserved IP is tied to a specific datacenter's network infrastructure, it can't be moved between regions; however, it provides a persistent, static public IPv4 entry point for any cloud infrastructure within that same region.

Unlike ephemeral IPs, which the network assigns and recycles automatically, a Reserved IP stays linked to your account until you explicitly release it. This lets you keep the same address even if you delete or rebuild the underlying Linode or NodeBalancer. By separating your IP address from your servers, you can update or migrate your infrastructure within the region without changing your public-facing IP.

Reserved IPs also simplify management. Unlike ephemeral addresses that may change during automated deployments, Reserved IPs remove the need to manually update allowlists, firewall rules, automation scripts, and DNS records.

Reserved IPs are available at a flat hourly rate per IP, whether or not the address is currently assigned to a resource. This straightforward billing model provides predictable costs and supports operational safety during failovers or maintenance, when an IP might be temporarily unassigned. When you unreserve an IP, billing stops immediately and the address returns to the general pool, making it unavailable for recovery.

New Networking endpoints

• Reserve a public IPv4 address. POST /networking/reserved/ips
• List reserved IP addresses. GET /networking/reserved/ips
• Get a reserved IP address. GET /networking/reserved/ips/{address}
• Update reserved IP address tags. PUT /networking/reserved/ips/{address}
• Get reserved IP pricing. GET /networking/reserved/ips/types
• Unreserve an IP address. DELETE /networking/reserved/ips/{address}

Updated Networking endpoints

• List IP addresses. GET /networking/ips
• Allocate an IP address. POST /networking/ips
• Assign IP addresses. POST /networking/ips/assign
• Get an IP address. GET /networking/ips/{address}
• Update an IP address. PUT /networking/ips/{address}

Updated Linode endpoints

• Create a Linode. POST /linode/instances
• Delete a Linode. DELETE /linode/instances/{linodeID}
• Allocate an IPv4 address. POST /linode/instances/{linodeId}/ips
• Get networking information. GET /linode/instances/{linodeId}/ips

Updated NodeBalancer endpoints

• Create a NodeBalancer. POST /nodebalancers
• Delete a NodeBalancer. DELETE /nodebalancers/{id}

Updated Tag endpoints

• Create a tag. POST /tags
• List tagged objects. GET /tags/{tagLabel}
• Delete a tag. DELETE /tags/{tagLabel}

Updated Service transfers endpoints

• Request a service transfer. POST /account/service-transfers
• Accept a service transfer. POST /account/service-transfers/{token}/accept