Service Plans
Last updated on
Service plans define the maximum capacity available for the NLB. The terminology differs depending on the network protocol used:
-
TCP: The capacity is expressed in connections.
-
UDP: The capacity is expressed in sessions.
-
Max. Capacity (Listener): Sets the theoretical maximum number of concurrent TCP connections (“up to”) on the listener side of the load balancer. For UDP sessions, this value does not scale with the service plan.
Important note on limitations:
- TCP (Connections): Although the theoretical maximum (“up to”) defined in the service plan is supported on the listener side, there is a limit of 28,000 TCP connections per target. To fully utilize the theoretical maximum of a larger plan (e.g., up to 250,000 for the
p250plan), load distribution must be ensured across a sufficient minimum number of targets.- UDP (Sessions): For UDP, there is a hard limit of 28,000 sessions per load balancer. This limit applies globally and is independent of the selected service plan or the number of targets. Scaling beyond 28,000 UDP sessions via a larger plan is not possible.
To set the service plan, the planId field is specified. If planId is omitted, p10 is used by default.
The following table shows the available service plans, the theoretical limits for TCP, and the minimum number of targets required for maximum TCP utilization. For UDP, the global limit of 28,000 sessions applies regardless of the chosen plan.
| Plan ID | Max. Connections (up to) | Min. Targets |
|---|---|---|
| p10 (Default) | 10,000 | 1 |
| p50 | 50,000 | 2 |
| p250 | 250,000 | 9 |
| p750 | 750,000 | 27 |
These plans are available in the following STACKIT regions:
- EU01
- EU02