Reserved IPs

The reserved IP feature is designed for the reservation of individual public IPv4 addresses within a specific region.

Reserved IP addresses offer a persistent, static public IPv4 entry point or egress point for your cloud infrastructure. Because a reserved IP is bound to a specific datacenter, it can't be moved across regions. Unlike ephemeral IPs, which the network assigns and recycles automatically, a reserved IP stays linked to your account until you release it.

Features

  • Reserve public IPv4 addresses on‑demand via Cloud Manager, CLI, Terraform, and Linode API.
  • Keep the same address even if you delete the underlying Linode, NodeBalancer, or NAT Gateway (BETA).
  • Assign reserved IPs to NAT Gateways (BETA) in manual scaling mode to provide fixed, known outbound IP addresses.
  • Rebuild or migrate Linode and NodeBalancers , or NAT Gateways (BETA) within the same region without changing your public-facing IP.
  • Eliminates the need to update allowlists, firewall rules, automation scripts, or DNS records during deployments.
  • Maintain ownership of the address during failovers or maintenance windows when it may be temporarily unassigned.

Availability

You can reserve public IPv4 addresses to use for your Linodes, NodeBalancers, and NAT Gateways (BETA) across all regions.

Pricing

Reserved IPs are billed at a flat hourly rate per IP, whether or not the address is assigned to a resource. The hourly rate is displayed when you create a reserved IP in Cloud Manager. You can also use the get reserved IP pricing API operation to view hourly rates.

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 is recycled, making it unavailable for recovery.

Pricing for NAT Gateways is separate from Reserved IPs.

Limits and considerations

  • Assigning an existing unassigned reserved IP to an existing Linode is currently only supported using the Linode API and CLI. Cloud Manager supports selecting reserved IPs only during new resource creation.
  • You can use reserved IPs only for Linode, NodeBalancer, and NAT Gateway IPv4 addresses.
    Automating NodeBalancer provisioning with reserved IPs using Linode Kubernetes Engine (LKE) or LKE-Enterprise is supported for IAM Service Accounts. However, this feature is currently not supported for IAM restricted users. NodeBalancers deployed by restricted users using Kubernetes services will allocate an ephemeral public IP address instead.
  • Users must have unrestricted access to fully interact with the reserved IPs feature. Restricted users may encounter limitations when reserving or viewing IPs.
  • This feature is used for reserving individual public IPv4 addresses, not CIDR blocks. You can reserve only one public IPv4 at a time, not all 256 IPs in the subnet.
  • Akamai Cloud applies account-level IPv4 allocation limits in each data center to help maintain IPv4 address availability. Reserved IPv4s count toward your account's per-data center public IPv4 quota limit. Existing Reserved IPs are unaffected, but new creation requests exceeding your quota will be denied. To request a higher limit, open a Customer Support ticket and include the data center, the requested limit, a brief business justification, and your expected growth over the next 6–12 months, if available. The following do not count toward your IPv4 limit:
    • IP addresses in your sticky IP pool. A sticky IP is an IPv4 address that, after being released, is temporarily held in your account to prevent immediate reassignment to other users.
    • Virtual Private Cloud (VPC) allocations.
  • Reservations for IPv6 addresses are not supported at this point.
  • Since reserved IPs are specific to a single region, they won't move with your Linode or NAT Gateway during a migration across data centers. To maintain a reserved IP in your new location, reserve a new address in the target region and assign it to your resource.
  • Reserved IPs assigned to Linodes can use the IP Sharing feature. IP Sharing is not applicable to NAT Gateways.

Developer resources


Did this page help you?