Vultr DocsLatest Content

How to Delete a Reserved IP

Updated on 12 September, 2025

Permanently removes a resource from your Vultr account.

Deleting a reserved IP detaches it from any linked instances and removes it from your Vultr account. You can re-create a reserved IP after deletion if it's available in the specific Vultr location.

Follow this guide to delete a reserved IP using the Vultr Customer Portal, API, CLI, or Terraform.

  • Vultr Customer Portal
  • Vultr API
  • Vultr CLI
  • Terraform
  1. Navigate to Products, expand the Network drop-down and select Reserved IPs from the list of options.
  2. Click your target reserved IP to open its management page.
  3. Click Remove Reserved IP in the top-right corner.
  4. Click Remove Reserved IP in the confirmation prompt to delete the reserved IP.

  1. Send a GET request to the List Reserved IPs endpoint and note the target reserved IP's ID in your output.

    console 
    $ curl "https://api.vultr.com/v2/reserved-ips" \
   -X GET \
   -H "Authorization: Bearer ${VULTR_API_KEY}"

  2. Send a DELETE request to the Delete Reserved IP endpoint to delete the reserved IP.

    console 
    $ curl "https://api.vultr.com/v2/reserved-ips/{reserved-ip}" \
  -X DELETE \
  -H "Authorization: Bearer ${VULTR_API_KEY}"

  1. List all reserved IPs in your Vultr account and note the target reserved IP's ID.

    console 
    $ vultr-cli reserved-ip list

  2. Delete the reserved IP.

    console 
    $ vultr-cli reserved-ip delete <reserved-ip-id>

  1. Open your Terraform configuration where the Reserved IP is defined.

  2. Remove the vultr_reserved_ip resource block, or destroy it by target.

    terraform 
    resource "vultr_reserved_ip" "rip" {
    region  = "ewr"
    ip_type = "v4"
    label   = "web-rip"
}

# To delete, either remove this block from configuration
# or run: terraform destroy -target vultr_reserved_ip.rip

  3. Apply the configuration and observe the following output:

    Apply complete! Resources: 0 added, 0 changed, 1 destroyed.

Comments

No comments yet.