Guides

Reading your first cloud invoice: line items that surprise new account holders

Data transfer, snapshots, unattached volumes and idle IP addresses: the invoice lines new cloud account holders rarely expect, explained.

Updated September 25, 2026

Reading your first cloud invoice: line items that surprise new account holders

The first invoice from a cloud provider is rarely the number you expected. Usually it is not far off, but it contains lines you never consciously ordered. This guide walks through the line items that most often puzzle new account holders and explains what each one is charging for, using DigitalOcean and Hetzner because both bill hourly with monthly caps and both make the individual items easy to see.

Compute: hourly accrual and the monthly cap

The largest line is normally the virtual machines. Both DigitalOcean Droplets and Hetzner cloud servers accrue at an hourly rate up to a monthly cap, so a server that ran all month shows the cap and a server that ran for a week shows a fraction of it. If you created and destroyed several test machines, each appears as its own short line rather than being folded together.

Hetzner’s dedicated servers follow a different pattern and bill on a fixed monthly model. Mixing cloud and dedicated on one account means two billing rhythms on one invoice, which is worth knowing before you compare months.

Storage you forgot existed

Three storage lines surprise almost everyone:

  • Snapshots. A snapshot is a stored copy of a disk and is billed on the space it occupies for as long as it exists. Snapshots taken before a risky change and never deleted accumulate quietly.
  • Block storage volumes. Volumes bill independently of the server they were attached to. Destroy the server and the volume keeps billing until you delete it separately.
  • Backups. Automated backup options on a server add a recurring charge that continues while the feature is enabled.

On DigitalOcean the Volumes and Snapshots sections of the control panel show what is still stored; on Hetzner the volumes and snapshots lists do the same. A monthly review of both catches most of this, and cleaning up unused cloud resources turns that review into a routine.

Idle IP addresses

Floating or reserved IP addresses are a classic surprise. On both platforms, an IP that is reserved but not assigned to a running server can still be billed, because the address is held for you regardless of use. The fix is simple: release addresses you are not using, and document the ones you are keeping for failover so nobody deletes them by mistake.

Data transfer and traffic

Outbound data transfer is the line with the widest range between providers. Hetzner includes generous traffic allowances in many locations, and DigitalOcean pools transfer across Droplets, so small applications often see nothing here at all. Bandwidth-heavy workloads, such as media delivery or large backups leaving the platform, can push past included amounts and generate overage.

Read this line carefully in the first month. If it is non-zero, find out which resource generated the traffic before the pattern repeats. Inbound transfer is normally not charged; outbound is where the cost sits.

Mid-cycle and partial-month charges

DigitalOcean bills monthly but may charge mid-cycle when usage exceeds a threshold, so a new account with heavy early use can see a charge before the month ends. Hetzner invoices monthly for usage in the prior period. Neither is an error; both are the provider protecting itself against unpaid usage while an account is new.

The Buy Digital Ocean Account page lists options by Droplet count, such as “Digital Ocean 3 Droplet Account” and “Digital Ocean 10 Droplet Account”, and the Buy Hetzner Account page lists “Hetzner 5 Server Limits Account” and “Hetzner 10 Server Limits Account”. Those limits cap how many servers can exist, which indirectly caps the compute line, but they do nothing to cap storage, snapshots or traffic.

Credits and how they appear

If the account carried a promotional balance, the invoice shows the full usage and then a credit line that offsets it. Watch the remaining balance rather than the amount due: the amount due can be zero for months and then jump when the credit runs out. The cost control guide for new accounts explains how to set alerts so the transition is not a surprise.

A five-minute invoice review

Line Question to ask Typical fix
Compute Did every listed server need to exist all month? Destroy test machines promptly
Snapshots Which snapshots are older than the change they protected? Delete or set a retention rule
Volumes Is every volume attached to a live server? Delete orphaned volumes
IP addresses Is every reserved address assigned? Release idle addresses
Transfer Which resource sent the outbound traffic? Cache, compress or relocate

Do this review with the first three invoices and the fourth will hold no surprises. If several projects or clients share the account, tagging and cost allocation shows how to split the same invoice by owner. Provider-specific billing questions are collected in the Hetzner section of the cloud FAQ.

Questions on this topic

Why am I charged for a server I already destroyed?

Usually you are seeing the hours it ran before deletion, or a resource that outlived it. Block storage volumes, snapshots and reserved IP addresses bill independently of the server they belonged to. Check the volumes, snapshots and networking sections of the control panel for anything left behind.

Do Droplet or server limits cap my bill?

Only partly. A limit such as the Digital Ocean 10 Droplet Account or Hetzner 10 Server Limits Account caps how many machines can exist, which bounds the compute line. It does not bound snapshots, volumes, backups or outbound transfer, so those lines still need a monthly review.

Why was I charged before the end of the month?

Some providers charge mid-cycle when a new account's usage passes a threshold, and others invoice monthly for the previous period. Both are normal and protect the provider while an account is new. The cost control guide for new cloud accounts explains how to set alerts around these events.

More from the Blog

All articles