Oct 28, 2026 — IPv4 limits
Akamai Cloud now applies account-level IPv4 allocation limits in each data center. These limits help protect IPv4 address availability by preventing a single account from using up a data center's IPv4 inventory, ensuring reliable and predictable provisioning for all customer accounts.
Affected resources
IPv4 limits apply to new public and private IPv4 allocations, including allocations for:
- Linode instances
- NodeBalancers
- Linode Kubernetes Engine (LKE / LKE-E) nodes
- Managed Databases
- Reserved IPs
- Additional IP addresses
Existing resources and existing IPv4 assignments are not affected.
IPv4 quota limit exclusionsThe following don't 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.
Exceeding IPv4 limits
If a new allocation request causes your account to exceed its IPv4 quota in a given data center, the provisioning request will be denied and details such as the reason for the denial, current usage, the applicable limit, and the data center's region (for example, us-east) are provided.
If your application requires additional IPv4 capacity in a specific data center, you can request an account limit increase by opening a ticket with Customer Support and include the following details:
- The data center where you need the increase.
- The requested limit.
- A brief business justification.
- Expected growth over the next 6–12 months, if available.
Limit increase requests are reviewed based on your use case and available capacity in the requested data center.