--- title: "Resize" description: "Change your NAT Gateway plan to raise or lower its bandwidth ceiling, and know when the resize is available." category: "Deployment" language: en source: https://cubepath.com/docs/products/deployment/nat-resize updated: 2026-11-17 --- # Resize Open the gateway → **Resize** tab in [my.cubepath.com](https://my.cubepath.com). Switch to a different plan in the same location. Each option is marked **Upgrade** or **Downgrade** by bandwidth, with its monthly and hourly price, so the trade-off is on screen before you commit. ## When to resize up The bandwidth ceiling is shared by **every server on the private network**, so hitting it slows the whole fleet at once, with nothing on any individual server to explain it. Check the [Metrics](/docs/products/deployment/nat-metrics) chart against the plan's Mbps. Traffic sitting near the ceiling at your busy hour is the signal: resize before it becomes the thing everyone is complaining about. ## When to resize down If the gateway has run for weeks well below its ceiling, a smaller plan costs less and changes nothing else. Egress needs are usually far more modest than people assume: private servers pulling package updates and calling a few APIs don't need much throughput. ## Do the resize Select the plan, click **Resize** and confirm in the dialog. The gateway is briefly unavailable while it resizes, so servers that reach the internet through it lose that access for a moment. > Note: Resizing is only available while the gateway is **Active** or **Stopped**. If another operation is running, wait for it to finish. > Tip: The gateway's public IPs don't change when you resize, so anything that whitelists your egress address keeps working. That's the difference between resizing and recreating the gateway: recreating it gets you a new address and breaks every whitelist that references the old one.