Google Cloud5 min read

Stopping a Google Cloud VM doesn’t stop the bill

A stopped Compute Engine VM stops vCPU and memory charges, but its disks, static IP and snapshots keep billing. What Google still charges, in us-central1.

Team VeriKost · prices checked 16 Oct 2026
ShareinX
Card: Stopped. Still billing. A stopped e2-standard-2 VM in us-central1 (state TERMINATED) bills $0.00 for vCPUs and memory, but $10.00 a month for its 100 GiB pd-balanced boot disk and $3.65 for its static external IP: $13.65 a month.

Key takeaways

  • Stopping a Compute Engine VM ends the vCPU and memory charge. Google then shows it as TERMINATED, but its disks are still there and still billing.
  • Persistent disks bill per GiB provisioned: $0.10 per GiB-month for pd-balanced in us-central1, $0.17 for pd-ssd, $0.04 for pd-standard.
  • A static external IP on a stopped VM counts as in use and bills $0.005 an hour. Delete the VM but keep the IP, and it doubles to $0.01.
  • A stopped e2-standard-2 with a 100 GiB pd-balanced boot disk and a static IP still costs $13.65 a month.
On this page

Stopping a VM in Google Cloud works a lot like stopping one on AWS. The server shuts down, the compute charge stops, and several other lines on the bill carry on as if nothing happened. Here is what Google still charges for, at us-central1 list prices, and when to delete instead.

01What does Google stop charging for when you stop a VM?

vCPUs and memory. Once the stop completes, the VM moves to the TERMINATED state. Despite the name, nothing is deleted: Google’s word for a stopped VM is TERMINATED, and you can start it again. Google bills CPU only while a VM is RUNNING (or shutting down gracefully), so for an e2-standard-2 that is the $48.92 a month it costs to run, gone.

02What keeps billing on a stopped Compute Engine VM?

Google’s docs are blunt about it: you pay for attached resources like disks and external IP addresses regardless of the VM’s state. Here is a stopped e2-standard-2 with a 100 GiB pd-balanced boot disk and a static external IP, at us-central1 list prices:

What a stopped Compute Engine VM still costs per month, us-central1
Line itemWhile stoppedPer month
vCPUs and memory (e2-standard-2)Not billed$0.00
Boot disk (pd-balanced, 100 GiB)100 GiB × $0.10$10.00
Static external IP$0.005/hr × 730 h$3.65
TotalStill billed$13.65

Persistent disks bill for every GiB you provisioned, not what is written on them. The same 100 GiB costs $4.00 a month as pd-standard ($0.04 per GiB-month) and $17.00 as pd-ssd ($0.17). Every extra data disk on the VM adds its own line. Ten forgotten VMs like this one come to $136.50 a month.

03Does the static IP keep billing?

Yes, and it is the part people get wrong. Google counts a static external IP as in use while it is assigned to a VM, whether the VM is running or stopped, and bills it at the in-use rate: $0.005 an hour, $3.65 a month. An ephemeral IP is different: Google releases it when the VM stops, and you get a new one on start.

The trap comes when you clean up. Delete the VM but keep its static address, and the address becomes RESERVED, unattached to anything. Google bills that at the higher rate: $0.01 an hour, $7.30 a month.

04Do snapshots keep costing money?

Yes, for as long as they exist, including after the VM and its disks are gone. A standard snapshot bills for the compressed data on the disk, not its provisioned size. Unless you change the default, a snapshot of a us-central1 disk is stored in the us multi-region at $0.065 per GiB-month; stored in us-central1 itself it is $0.05. The AWS version of this story is in what a stopped EC2 instance still costs.

05Should you stop, suspend or delete the VM?

  • Back tomorrow? Stop it. Overnight you only pay for the disks and the static IP.
  • Back in a few days, and want it exactly as it was? Suspend it. Google saves the memory and bills it at $0.000232876 per GiB-hour in us-central1, about $1.36 a month for an e2-standard-2’s 8 GB, on top of the disks and IP. A VM can stay suspended for up to 60 days, and VMs with GPUs or more than 208 GB of memory can’t be suspended.
  • Not needed for weeks? Take a snapshot of the disk, or a machine image of the whole VM ($0.05 per GiB-month), then delete the VM. Check that its disks went with it, and release the static IP so it doesn’t start billing $7.30 a month on its own.

06How do you find them in your project?

In the console: Compute Engine → VM instances, look at the status column for stopped VMs; Compute Engine → Disks, look for disks with nothing in In use by; VPC network → IP addresses, look for external addresses that are reserved. Or with the gcloud CLI:

# Stopped VMs, and when they were stopped
gcloud compute instances list --filter="status=TERMINATED" \
  --format="table(name,zone.basename(),machineType.basename(),lastStopTimestamp)"

# Disks attached to nothing
gcloud compute disks list --filter="-users:*" \
  --format="table(name,zone.basename(),sizeGb,type.basename())"

# Static IPs: RESERVED is attached to nothing; IN_USE shows which VM holds it
gcloud compute addresses list --format="table(name,address,status,users)"

Each command covers the whole project, every region and zone. Disks attached to a stopped VM won’t show in the second list: they still count as attached. For the other things Google Cloud bills while idle, from stopped Cloud SQL to empty GKE clusters, see five Google Cloud resources that bill you while doing nothing.

Frequently asked questions

Do you pay for a stopped Google Cloud VM?

Not for its vCPUs and memory. You keep paying for its persistent disks, any static external IP assigned to it, and any snapshots or machine images you have taken.

What does TERMINATED mean in Compute Engine?

It is the state of a stopped VM. The VM still exists, with its disks, configuration and static IP, and you can start it again. It is not deleted.

Does a static IP cost money when the VM is stopped?

Yes. Google counts a static external IP as in use while it is assigned to a VM, running or stopped, and bills it $0.005 an hour, $3.65 a month at list price. If you delete the VM and keep the address, it bills $0.01 an hour instead.

Is a snapshot cheaper than keeping the disk?

Usually. A snapshot bills for the compressed data actually on the disk, at $0.065 per GiB-month in the us multi-region (the default for a us-central1 disk) or $0.05 in us-central1 itself. The disk bills for every GiB you provisioned.

Sources

  • Cloud Billing Catalog API, Compute Engine, us-central1: E2 core and RAM, Balanced, Standard and SSD PD capacity, External IP Charge on a Standard VM, Static Ip Charge, PD snapshot storage (regional and US), machine image storage, suspended VM RAM
  • Google Cloud docs: Compute instance life cycle (instance pricing), Stop and start an instance, Suspend and resume an instance, Delete an instance, Disk and image pricing, VPC network pricing (external IP addresses)
Team VeriKostWe build read-only tooling that finds idle cloud resources and shows the math behind every saving. AWS and Google Cloud today, Azure next.

Keep reading

Find this waste in your own cloud account.

VeriKost scans read-only and shows the metric, the threshold and the price behind every saving.

Request early access AWS and Google Cloud · invite-only