---
agentTools:
  siteIndex: https://techdocs.akamai.com/llms.txt
  projectIndex: https://techdocs.akamai.com/linode-api/llms.txt
---

# Sep 30, 2026 — NodeBalancers and flexible backend connectivity

This release introduces Premium NodeBalancers for enterprise-grade workloads and expands backend connectivity options to include VPC and public IPv6, in addition to the existing private IPv4 (Legacy) support.

For more information, see:

* [Premium NodeBalancers](https://techdocs.akamai.com/linode-api/reference/premium-and-flexible-backend-connectivity#premium-nodebalancers)
* [Flexible backend connectivity](https://techdocs.akamai.com/linode-api/reference/premium-and-flexible-backend-connectivity#flexible-backend-connectivity)

## Premium NodeBalancers

NodeBalancers are now offered in both premium (new) and basic versions. The following table compares these options. Use this information to help determine which version best meets your application’s requirements for performance, scalability, and protocol support.

[block:parameters]
{
  "data": {
    "h-0": "Feature / Specification",
    "h-1": "Premium (`premium`)",
    "h-2": "Basic (`common`)",
    "0-0": "Maximum backend nodes per configuration",
    "0-1": "Up to 2,000",
    "0-2": "Up to 1,000",
    "1-0": "Backend node connectivity",
    "1-1": "Supports either VPC or public IPv6 backends.  \n  \nDoes not support legacy private IPv4.",
    "1-2": "Supports legacy (private IPv4), VPC or public IPv6 backends.",
    "2-0": "Maximum concurrent connections (TCP/HTTP/HTTPS)",
    "2-1": "Up to 100,000",
    "2-2": "Up to 10,000",
    "3-0": "Maximum concurrent connections (UDP)",
    "3-1": "Up to 80,000",
    "3-2": "Not supported",
    "4-0": "UDP (Beta) layer 4 load balancing",
    "4-1": "Supported when UDP protocol is enabled on your account. (Configured using APIs only)",
    "4-2": "Not supported",
    "5-0": "TCP (layer 4) load balancing",
    "5-1": "Supported",
    "5-2": "Supported",
    "6-0": "HTTP/HTTPS (layer 7) load balancing",
    "6-1": "Supported (HTTP/1.1 only)",
    "6-2": "Supported (HTTP/1.1 only)",
    "7-0": "Maximum inbound network bandwidth",
    "7-1": "10 Gbps",
    "7-2": "10 Gbps",
    "8-0": "Assigned for LKE-E clusters",
    "8-1": "Automatically assigned",
    "8-2": "Not automatically assigned",
    "9-0": "Infrastructure and performance",
    "9-1": "Dedicated for consistent, predictable capacity",
    "9-2": "Shared, may experience resource contention",
    "10-0": "Reserved IPs",
    "10-1": "Supported (Except when provisioned by IAM restricted users for LKE-Enterprise).",
    "10-2": "Supported"
  },
  "cols": 3,
  "rows": 11,
  "align": [
    "left",
    "left",
    "left"
  ]
}
[/block]

## Flexible backend connectivity

NodeBalancers no longer require a private IP in the `192.168.255.0/24` range to communicate with backend nodes. Instead, the connectivity between the NodeBalancer and its backend nodes now depends on its `backend_connectivity` setting. Depending on this setting, IP addresses outside the private range can be used.

The NodeBalancer's `backend_connectivity` setting applies to all its backend nodes and can't be changed after the NodeBalancer is created. You can choose from `legacy`, `ipv6`, or `vpc` for this setting.

### NodeBalancer connectivity to backend nodes

[block:parameters]
{
  "data": {
    "h-0": "Value",
    "h-1": "When to use",
    "h-2": "Example IP used for connectivity",
    "0-0": "`legacy`",
    "0-1": "For basic NodeBalancers communicating with non-VPC backend nodes over private IPv4.  \n  \nThe NodeBalancer's frontend IPv4 communicates with the backend node's private IPv4 address.  \n  \n**Note:** Limited quantities of private IPv4s are available.",
    "0-2": "192.168.255.10  \n  \nOther types of node addresses (IPv6, VPC IPs) are not allowed.",
    "1-0": "`ipv6`",
    "1-1": "For basic or premium NodeBalancers communicating with non-VPC backend nodes using a public IPv6.  \n  \nThe NodeBalancer's frontend IPv6 communicates with the backend node's IPv6 address.",
    "1-2": "2600:3c1f:51:1::1  \n  \nOther types of node addresses (private IPv4, VPC IPs) are not allowed.",
    "2-0": "`vpc`",
    "2-1": "For basic or premium NodeBalancers communicating with backend nodes assigned to a VPC.  VPCs support IPv4 and IPv6 (BETA).",
    "2-2": "10.0.250.4/30  \n  \nNon-VPC IPs are not allowed.",
    "3-0": "`undefined`  \n(Read-only)",
    "3-1": "This value is assigned only when you create a NodeBalancer without specifying a `backend_connectivity ` type, node configuration, or VPC.  \n  \nAfter you add the first backend node to the NodeBalancer using the Create a node operation, this value updates to either `legacy` or `ipv6`.",
    "3-2": " —"
  },
  "cols": 3,
  "rows": 4,
  "align": [
    "left",
    "left",
    "left"
  ]
}
[/block]

> 📘
>
> Data transferred between services like NodeBalancers and Linodes in the same data center (using either a private IPv4, public IPv6, or VPC) is free and it doesn’t count against your monthly bandwidth allowance.

## Protecting backend nodes from unauthorized access and maintaining secure communication

The NodeBalancer's backend IPs are used for communication between the NodeBalancer and the backend nodes. Your backend nodes should be configured to block direct traffic from external sources or clients, accepting requests only through these NodeBalancer backend IPs.

To secure backend nodes, assign the Linodes to a VPC or use Cloud Firewalls and configure firewall rules to allow only NodeBalancer traffic. Add the NodeBalancer IP access control list (ACL) to the backend node's firewall rules. This setup is typically performed once.

NodeBalancer backend IP addresses differ by data center. You can obtain the ACL using the [GET NodeBalancer's backend ACL](https://techdocs.akamai.com/linode-api/reference/get-node-balancer-backend-acl) operation.

# NodeBalancers - API changes

## NodeBalancers

Added new fields:

* `type`. With the following options: `premium` and `common`.
* `backend_connectivity`. With the following options: `legacy`, `ipv6`, and `vpc`. If `backend_connectivity` is not specified and neither a VPC nor a node is provided, a new common NodeBalancer will have `undefined` assigned, while a new premium NodeBalancer will have `ipv6` assigned.
* `backend_ipv6_prefix`. Read-only. The backend ACL for this NodeBalancer that can be used for firewall rules on their backend Linodes, allowing traffic only from that NodeBalancer backend source range.
  > 🚧
  >
  > The `backend_connectivity` setting can't be changed after you create the NodeBalancer. All backend nodes must use the same IP addressing supported by the selected `backend_connectivity` type. For example, if you set `backend_connectivity` to `legacy`, all backend nodes must use private IPv4 addresses.
* **Create a NodeBalancer** ([POST /nodebalancers](https://techdocs.akamai.com/linode-api/reference/post-node-balancer))
* **List NodeBalancers** ([GET /nodebalancers](https://techdocs.akamai.com/linode-api/reference/get-node-balancers))
* **Get a NodeBalancer** ([GET /nodebalancers/{nodeBalancerId}](https://techdocs.akamai.com/linode-api/reference/get-node-balancer))
* **Update a NodeBalancer** ([PUT /nodebalancers/{nodeBalancerId}](https://techdocs.akamai.com/linode-api/reference/put-node-balancer))
* **Get a NodeBalancer's backend IPv6 prefix** ([GET /nodebalancers/{nodeBalancerId}/backend\_acl](https://techdocs.akamai.com/linode-api/reference/get-node-balancer-backend-acl) )

## Nodes

Updated the `address` field.  This field now accepts private IPv4 (legacy), public IPv6, or VPC IP addresses depending on the NodeBalancer's `backend_connectivity` setting.

* **Create a node** ([POST /nodebalancers/{nodeBalancerId}/configs/{configId}/nodes](https://techdocs.akamai.com/linode-api/reference/post-node-balancer-node))
* **List nodes** ([GET /nodebalancers/{nodeBalancerId}/configs/{configId}/nodes](https://techdocs.akamai.com/linode-api/reference/get-node-balancer-config-nodes))
* **Get a NodeBalancer's node** ([GET /nodebalancers/{nodeBalancerId}/configs/{configId}/nodes/{nodeId}](https://techdocs.akamai.com/linode-api/reference/get-node-balancer-node))
* **Update a node** ([PUT /nodebalancers/{nodeBalancerId}/configs/{configId}/nodes/{nodeId}](https://techdocs.akamai.com/linode-api/reference/put-node-balancer-node))
* **Rebuild a config** ([POST /nodebalancers/{nodeBalancerId}/configs/{configId}/rebuild](https://techdocs.akamai.com/linode-api/reference/post-rebuild-node-balancer-config))