Z4M family · General Purposex86_64 · Intel/AMD

z4m-highmem-192

The z4m-highmem-192 machine type has 192 vCPUs and 1488 GB of memory. Pricing for this instance starts at $39.54 per hour and $28864.08 monthly in the us-central1 region.

Updated November 21, 2026
vCPUs
192
Memory
1488 GB
Network
Up to 400 Gbps
Storage
Local SSD

Save up to $17318/mo on every z4m-highmem-192

Connect Google Cloud — we'll find the optimal pricing model for your workload.

All pricing options

us-central1 · USD · monthly = 730 hrs
Prices exclude local taxes
Term / TierHourlyMonthlySavings
On-Demand
$39.5398$28864.08 Baseline
1-Year Committed Use Discount (CUD)
$26.8870$19627.53 -32%
3-Year Committed Use Discount (CUD)
$17.3975$12700.17 -56%
Preemptible / Spot
$15.8159$11545.63 -60%
You could save $17318.45/mo on this instance with the right pricing model.
Find my savings

Monthly cost estimator

Estimate your spend based on actual usage.
730 h
1h365h730h (24/7)
1
Estimated monthly
$28864.08
730 hrs × $39.5398/hr × 1

Compute

x86_64 · Intel/AMD
vCPUs i192
Memory i1488 GB
Physical processorIntel Emerald Rapids
Nested VirtualizationNot supported
Sole TenantNot supported
GPUNone
Within Z4M family
z4m-highmem-16
16 vCPU
z4m-highmem-32
32 vCPU
z4m-highmem-48
48 vCPU
z4m-highmem-192
192 vCPU
z4m-highmem-192-metal
192 vCPU

Lock in this rate across your fleet — typically save 30–40%

Connect your Google Cloud account to apply this pricing logic to every running instance automatically.

Networking

Max egress bandwidth400 Gbps
Tier 1 bandwidthN/A
Enhanced networking iYes (gvnic/virtio)
IPv6 supportYes (Dual-stack VPC)

Storage

Max persistent disks128
Max disk size512 TB
Local SSDsSupported (Scratch Disk)

Compare with another instance

vs.
Specz4m-highmem-192z4m-highmem-16Δ
vCPUs19216-92%
Memory1488 GB122 GB-92%
Hourly Price$39.5398$3.2871-92%
Monthly Price$28864.08$2399.59-92%
Cost optimization

GCP recommender alerts can cut this bill ~30-40%.

Connect your GCP account. We'll identify every underutilized z4m.* instance and show exactly where downsizing, cleaning up orphaned disks, or shifting to CUDs saves money — with zero code changes.