Vultr Still Charging After Stopping Server

How to fix it

Try these in order — the most common fix is first.

1. 1. Destroy the instance

   Copy steps
   1. Download backups or snapshot if you need the data
   2. Open the instance in the Console and choose Destroy
   3. Confirm it no longer appears in the list
   Did this fix it? Yes No

2. 2. Audit remaining items

   Copy steps
   1. Check Snapshots, Backups, Block Storage and Reserved IPs
   2. Review billing history for line items
   3. A card charge may also be a temporary authorization hold
   Did this fix it? Yes No

Symptoms

Invoices keep arriving for a powered-off server.

Why it happens

• Stopped instances still reserve CPU, RAM, disk and IP
• Billing starts at deploy, not power-on
• Forgotten snapshots, backups or reserved IPs

This guide also covers

• vultr still charged after stopping
• vultr stopped server billing
• vultr billing destroy

Other Vultr errors

• Vultr SSH Connection Timed Out
• Vultr SSH Permission Denied
• Vultr Firewall Blocking Connections
• Vultr Server Stuck Pending or Installing
• Vultr Account Suspended or Needs Verification
• Vultr SMTP Port 25 Blocked
• Vultr Server Null Routed (DDoS)
• How to Cancel Vultr Account and Stop Billing