T2A family · General Purposearm64 · Ampere

t2a-standard-16

The t2a-standard-16 machine type has 16 vCPUs and 64 GB of memory. Pricing for this instance starts at $0.62 per hour and $449.68 monthly in the us-central1 region.

Updated May 26, 2026
vCPUs
16
Memory
64 GB
Network
Up to 32 Gbps
Storage
Persistent Disk

Save up to $319/mo on every t2a-standard-16

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
TermHourlyMonthlySavings
On-Demand
$0.6160$449.68 Baseline
1-Year Committed Use Discount (CUD)
$0.6160$449.68 Baseline
3-Year Committed Use Discount (CUD)
$0.6160$449.68 Baseline
Preemptible / Spot
$0.1789$130.63 -71%
You could save $319.05/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
$449.68
730 hrs × $0.6160/hr × 1

Compute

arm64 · Ampere
vCPUs i16
Memory i64 GB
Physical processorAmpere Altra
Nested VirtualizationNot supported
Sole TenantNot supported
GPUNone
Within T2A family
t2a-standard-1
1 vCPU
t2a-standard-2
2 vCPU
t2a-standard-4
4 vCPU
t2a-standard-8
8 vCPU
t2a-standard-16
16 vCPU
t2a-standard-32
32 vCPU
t2a-standard-48
48 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 bandwidth32 Gbps
Tier 1 bandwidthN/A
Enhanced networking iYes (gvnic/virtio)
IPv6 supportYes (Dual-stack VPC)

Storage

Max persistent disks128
Max disk size257 TB
Local SSDsNo local SSD

Compare with another instance

vs.
Spect2a-standard-16t2a-standard-1Δ
vCPUs161-94%
Memory64 GB4 GB-94%
Hourly Price$0.6160$0.0385-94%
Monthly Price$449.68$28.11-94%
Cost optimization

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

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