How much does an idle t2d-standard-2 cost on Google Cloud?
A t2d-standard-2 billed on-demand and left running around the clock costs about $62/mo at its cheapest listed region (us-central1). Scheduling it off outside business hours cuts that to roughly $18/mo — a $43/mo saving.
Cheapest on-demand
$0.0845/hr
us-central1
Running 24/7
$62/mo
730-hour month
Business-hours savings
$43/mo
70% off the 24/7 bill
Price by region
| Region | Hourly (on-demand) | Spot (typical) | ≈ Monthly (24/7) |
|---|---|---|---|
| us-central1 Cheapest | $0.0845/hr | $0.0286/hr | ≈ $62/mo |
| us-east1 | $0.0845/hr | $0.0286/hr | ≈ $62/mo |
| us-west1 | $0.0845/hr | $0.0286/hr | ≈ $62/mo |
| europe-west1 | $0.0929/hr | $0.0253/hr | ≈ $68/mo |
| asia-southeast1 | $0.1042/hr | $0.0270/hr | ≈ $76/mo |
| asia-northeast1 | $0.1084/hr | $0.0201/hr | ≈ $79/mo |
| europe-west2 | $0.1089/hr | $0.0199/hr | ≈ $79/mo |
| europe-west3 | $0.1089/hr | $0.0365/hr | ≈ $79/mo |
What a schedule saves
| Schedule | Monthly cost | Savings vs 24/7 |
|---|---|---|
| Running 24/7 | $62/mo | baseline |
| Weekdays only (off on weekends) | $44/mo | -$18/mo (29%) |
| Business hours only (10×5) | $18/mo | -$43/mo (70%) |
Assumes a 730-hour month at on-demand list price. Actual savings depend on when the instance is actually used.
About the t2d family
T2D is GCP's AMD EPYC (Milan) cost-optimized family, tuned for scale-out, horizontally distributed workloads — containerized microservices, web front ends, and batch fleets that scale by adding instances rather than making one instance bigger. Dev and staging clusters mirroring a scale-out production topology commonly run a handful of T2D nodes that are only actually serving traffic during testing sessions, with the rest of the week spent idling at full fleet size.
Regional pricing varies: t2d-standard-2 runs $0.0845/hr in us-central1, the cheapest region priced here, versus $0.1089/hr in europe-west2, the priciest — a 22% spread across regions for the identical instance type.
The next size up in the same family, t2d-standard-4 (4 vCPU / 16 GB RAM), costs about $123/mo running 24/7 at its cheapest region — roughly 100% more than t2d-standard-2's ~$62/mo — for 2x the vCPU.
Common questions
How much does an idle t2d-standard-2 cost per month?
At the cheapest listed region (us-central1), a t2d-standard-2 costs $0.0845/hr, or about $62/mo if it runs 24/7. That's the on-demand list price — an idle instance costs exactly the same as a busy one, since cloud billing doesn't know the difference.
How much can I save by scheduling it off outside work hours?
Restricting it to business hours only (10×5) saves about $43/mo (70%) versus running 24/7. A lighter schedule — on around the clock on weekdays, off on weekends — still saves about $18/mo (29%).
Does scale-out on t2d change how idle waste accumulates?
Yes — it multiplies it. Scale-out architectures idle as a fleet: five t2d nodes mirroring production topology idle five-for-five overnight. Scheduling the whole dev cluster as a unit, rather than per node, is what actually moves the number.
Other t2d sizes
Stop paying for idle Google Cloud servers
Idlefy runs a free audit of your fleet, then flips dev servers to stopped-by-default: lease one when you need it, and
when the lease ends it shuts itself off — stop, not terminate, persistent disks intact. Timers are set by your team, never
guessed, and Idlefy only manages instances tagged idlefy=enabled — on AWS that boundary is enforced by the IAM policy itself.
Prices are on-demand list price for standard instances and exclude storage, network, data transfer, and any negotiated or volume discounts. Actual bills vary by usage and account-level pricing. Prices as of 2026-07-20. Spot figures are indicative — AWS values are derived from AWS's published typical savings vs on-demand for the region; GCP values are the listed Spot price. Spot capacity can be reclaimed by the provider. Stopping preserves EBS and persistent-disk volumes; data on local instance-store or local-SSD drives does not survive a stop.