Vultr DocsLatest Content

How to Destroy a Vultr Cloud GPU Instance

Updated on 28 August, 2025

Destroying an instance removes the public IP address and deletes the server from your Vultr account. Destroying an instance cannot be reversed and any instance data cannot be recovered unless a backup or snapshot is available in your Vultr account.

Follow this guide to destroy a Vultr Cloud GPU instance using the Vultr Customer Portal, API, CLI, or Terraform.

  • Vultr Customer Portal
  • Vultr API
  • Vultr CLI
  • Terraform
  1. Navigate to Products and click Compute.
  2. Click your target Cloud GPU instance to open its management page.
  3. Click Destroy Server on the top-right navigation menu to destroy the server instance.
  4. Check the confirmation prompt and click Destroy Server to apply changes.

  1. Send a GET request to the List Instances endpoint and note the target instance's ID.

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

  2. Send a DELETE request to the Delete Instance endpoint to destroy the instance.

    console 
    $ curl "https://api.vultr.com/v2/instances/{instance-id}" \
  -X DELETE \
  -H "Authorization: Bearer ${VULTR_API_KEY}"

  1. List all instances in your Vultr account and note the target instance's ID.

    console 
    $ vultr-cli instance list

  2. Destroy the instance.

    console 
    $ vultr-cli instance delete <instance_id>

  1. Open your Terraform configuration and locate the Cloud GPU instance resource.

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

    terraform 
    resource "vultr_instance" "gpu" {
    label    = "gpu-instance-1"
    region   = "ewr"
    plan     = "vcg-1c-8gb"
    os_id    = 2284
    hostname = "gpu-instance-1"
}

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

  3. Apply the configuration and observe the following output:

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

Comments

No comments yet.