---
title: "Resize"
description: "Move your load balancer to a different plan to change its maximum targets, listeners and connections per second."
category: "Deployment"
language: en
source: https://cubepath.com/docs/products/deployment/lb-resize
updated: 2026-08-04
---

# Resize

Open the load balancer → **Resize** tab in [my.cubepath.com](https://my.cubepath.com).

Compares your current plan against the others available **in the same location**, showing each one's **max targets**, **max listeners** and **connections per second**, plus its hourly and monthly price. You can move up or down.

## Which limit are you actually hitting

The three limits fail in completely different ways, so identify the right one before you pay for a bigger plan:

| Limit | Symptom |
|-------|---------|
| **Connections per second** | New connections refused at peak while existing ones keep working. Users see intermittent failures that vanish when they retry |
| **Max targets** | You simply can't add another backend server |
| **Max listeners** | You can't add another port or service to this load balancer |

Check the connections-per-second chart on [Metrics](/docs/products/deployment/lb-metrics) against the plan's ceiling. If your peak isn't near it, a bigger plan won't make anything faster — the bottleneck is in your backends.

## Resize it

Select the new plan and confirm. The process takes a few minutes while resources are reallocated.

> Note: Downgrading to a plan whose limits are below what you're currently using isn't possible. Remove targets or listeners first.

> Tip: Resize ahead of a known traffic event, not during it. Connections-per-second limits bite exactly when you're least able to spend a few minutes reconfiguring.