DigitalOcean Unexpected Bill: Charged for Deleted or Powered-Off Droplets

How to fix it

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

1. 1. Find what is billing

   Copy steps
   1. Open Billing > Insights for a per-resource cost breakdown
   2. List all resources under Droplets, Volumes, Images (snapshots), Networking (reserved IPs, load balancers), Databases and Spaces
   Did this fix it? Yes No

2. 2. Destroy properly

   Copy steps
   1. Powering off does not stop charges; destroy the Droplet
   2. In the Destroy dialog tick snapshots and volumes to delete with it, they are not selected by default
   3. Or use doctl compute droplet delete <name> and then delete leftovers separately
   Did this fix it? Yes No

3. 3. Prevent surprises

   Copy steps
   1. Set a billing alert with percentage thresholds
   2. Note that invoices are issued on the 1st for the previous month, and auto-charges can occur mid-month when your balance hits your threshold
   3. Tag resources per project so you can review them
   Did this fix it? Yes No

4. 4. Dispute a charge

   Copy steps
   1. Open a billing support ticket listing the resource and dates
   2. Ask for a credit if you destroyed the resource and it kept billing
   Did this fix it? Yes No

Symptoms

Invoice is higher than expected, or you are charged after deleting a Droplet.

Why it happens

• Powered-off Droplets still reserve compute and bill
• Snapshots, volumes and volume snapshots are not destroyed by default when you destroy a Droplet
• Backups add a surcharge and remain until their retention ends
• Unused reserved IPs, load balancers, managed databases and Spaces keep billing
• Bandwidth overage beyond the included transfer
• Another team member created resources

This guide also covers

• digitalocean unexpected charge
• digitalocean billed for deleted droplet
• digitalocean charged after destroy
• digitalocean hidden costs

The same problem in other apps

All billing, cancellation & refunds guides →

• AWS Unexpected Charges: Why Is My AWS Bill So High? (AWS)

Other DigitalOcean errors

• DigitalOcean Droplet SSH Permission Denied (publickey)
• DigitalOcean Droplet SSH Connection Refused or Timed Out
• DigitalOcean Droplet 502 Bad Gateway (Nginx)
• DigitalOcean Droplet Out of Memory (OOM Killer)
• DigitalOcean App Platform Build Failed
• DigitalOcean App Platform Deploy Failed or 502 After Deploy
• DigitalOcean Account Locked or Verification Required
• DigitalOcean Droplet Locked Out: Reset Root Password and Recovery Console