GCP · per-regionUpdated 2026-04

GCP per-region internet egress

GCP charges internet egress based on the destination (where the user is), not the source region. All standard regions therefore have the same first-tier rate ($0.12/GB Premium, $0.085/GB Standard). Destination rates change for Australia, China, and India.

Source: cloud.google.com/vpc/network-pricing →

First-tier (worldwide ex Australia / China) rates by source region

Source region	Premium / GB	Standard / GB	Note
us-central1 (Iowa)	$0.12	$0.085	Cheapest US region. Default for many services.
us-east1 (S. Carolina)	$0.12	$0.085	Same as us-central1.
us-west1 (Oregon)	$0.12	$0.085	Closer to West Coast users.
europe-west1 (Belgium)	$0.12	$0.085	Most-used EU region for new deployments.
europe-west2 (London)	$0.12	$0.085	UK regulatory compliance.
europe-west3 (Frankfurt)	$0.12	$0.085	DE regulatory compliance, lower latency to central EU.
asia-east1 (Taiwan)	$0.12	$0.085	East Asia hub region.
asia-southeast1 (Singapore)	$0.12	$0.085	SE Asia hub. Premium for users in IN / TH / VN / ID.
asia-northeast1 (Tokyo)	$0.12	$0.085	Japan. Higher compute cost, same egress.
australia-southeast1 (Sydney)	$0.19	$0.110	Australia rates apply to destination, not source.
southamerica-east1 (Sao Paulo)	$0.12	$0.085	Brazil. Compute is higher cost; egress matches main rate.

Why source-region pricing is uniform

GCP's pricing model differs from AWS (which charges by source region) and Azure (which uses bandwidth zones). On GCP, the rate is set by where the user is (destination) and which tier you have selected, not by which region the workload lives in. This means:

Moving a workload from us-central1 to asia-southeast1 does not change egress costs for users in North America (the destination, not source, sets the rate).
Workloads in Sao Paulo and Sydney pay the same egress as Iowa for traffic to NA / EU users.
Cross-region traffic between GCP regions is priced separately ($0.02 to $0.12 per GB) and is the typical reason multi-region GCP deployments get expensive.