--- title: Load Balancer Actions --- # Load Balancer Actions Lifecycle actions for a load balancer are available from the three-dot **Actions** menu on the Load Balancers list and from the details page. This page covers each action, when it is available, and the confirmation each one requires. :::note All actions are disabled while the load balancer is **Creating**, **Deploying**, **Upgrading**, or **Deleting**. Actions also depend on your project permissions — running actions needs update permission, and deleting needs delete permission. ::: --- ## Start and Power Off The menu shows **Start** when the load balancer is Powered off, and **Power Off** otherwise. ### Power Off Select **Power Off**. The "Power Off Load Balancer" dialog explains: - Powering off does **not** stop billing — you keep paying until the load balancer is deleted. - If a disk-intensive system is running, powering off may cause data loss; the safest option is to power off from within the operating system. Tick "I understand the risk, and want to power off the Load Balancer: \." and select **Power Off**. ### Start Select **Start**. Confirm "Are you sure, you want to start the Load Balancer: \." with **Start**. The load balancer powers back on. :::warning Powering off keeps billing active. To stop charges, delete the load balancer (or, for committed plans, let the committed term end with the right setting). ::: --- ## Upgrade Plan Use **Upgrade Plan** to move the load balancer to a larger plan. 1. Power off the load balancer first — the upgrade dialog reminds you, "You need to power off your LB to upgrade plan." 2. Select **Upgrade Plan** and choose a target plan (the list shows plans larger than the current one). 3. Select **Apply**. The status changes to **Upgrading** and the upgrade completes in a few minutes. :::note Upgrade Plan is not available for **committed** load balancers or **private-cloud** load balancers. ::: --- ## Delete Select **Delete** to remove the load balancer. Automated traffic distribution stops as soon as it is deleted. The "Delete Load Balancer" dialog covers a few cases: - **Public IP** — if the load balancer's public IP can be reserved and you are within your limit, the dialog offers to **reserve the IP** so you can reuse it later (a monthly charge applies). If the IP is already reserved, it stays reserved after deletion. If you have hit your reserved-IP limit, the dialog explains this and links to [Reserved IP](/docs/myaccount/network/reserve_ip/). - **BitNinja** — if a BitNinja license is active, it is deleted along with the load balancer. - **Committed** — a committed load balancer can still be deleted; the dialog warns that it is reserved until the end date and recommends against it. Deleting before the term ends does not refund the committed amount. Confirm with **Delete**. --- ## Committed Load Balancer Most Load Balancer plans are billed hourly, but E2E also offers discounted **committed** plans for a fixed period (for example, 30 or 365 days). The longer the commitment, the more you save. Infra credits for a committed load balancer are deducted in full as soon as it is launched (postpaid customers see the full cost on the next bill). Committed plans are not available for every plan — contact sales if you need one for a specific load balancer. ### Convert to Committed The **Convert to Committed** action appears when committed plans are available for the load balancer and it is not already committed (and it is not a private-cloud load balancer). 1. Select **Convert to Committed**. 2. In the **Committed Conversion** window, choose a committed plan from the dropdown. 3. Read the confirmation text — it states how many infra credits will be deducted or billed for the committed period — and tick the agreement checkbox. 4. Select **Convert**. Auto-renewal is enabled by default; you can change it afterward in the committed settings. If you do not have enough infra credits, the dialog links you to buy more. ### Committed LB Settings The **Committed LB settings** action appears once a load balancer is committed. It controls what happens at the **end of the current committed period** — any change takes effect only after the current period ends. | Setting | Behavior at end of period | | ------------------------------- | -------------------------------------------------------------------------------------------------------------- | | Auto-renew the committed period | Renews automatically. You can pick a different committed plan to apply after the current one. | | Apply hourly billing | Switches to the plan's hourly rate. You can terminate the load balancer any time once it is on hourly billing. | | Auto deletion | Automatically terminates and deletes the load balancer. | The Info tab shows the active committed period, its end date, and the current setting. See [Info tab › Committed-Plan Details](/docs/myaccount/load-balancer/manage/info#committed-plan-details). --- ## Related Resources | Resource | Use it for | | ------------------------------------------------------------------------- | ---------------------------------------------------- | | [Info tab](/docs/myaccount/load-balancer/manage/info) | View details and committed-plan info; edit settings. | | [Reserved IP](/docs/myaccount/network/reserve_ip/) | Reserve a public IP before deleting. | | [Troubleshoot Load Balancers](/docs/myaccount/load-balancer/troubleshoot) | Why an action is disabled or an upgrade is blocked. | | [Manage Load Balancers](/docs/myaccount/load-balancer/manage) | The management hub. |