Skip to main content

Network Service Tiers

Exam guide§2.3

Two tiers decide how traffic reaches the internet: over Google's private backbone (Premium) or via the public internet through your region's ISP (Standard). It is a performance-vs-cost tradeoff.

Premium vs Standard tier

DECISIONPremium or Standard tier?
Premium (default)Standard
PathGoogle's global backbone end to endPublic internet (ISP) as far as possible
ScopeGlobalRegional
PerformanceHighest, lowest latencyBest-effort, more variable
CostHigher egressLower egress
Global external Application LBSupportedNot supported
Pick this when: Premium for global reach and performance; Standard to cut egress cost for regional traffic
GotchaStandard tier cannot use global load balancing

The global external Application LB and global external IPs require Premium tier. If a workload needs one anycast IP serving users worldwide, you must be on Premium. Standard tier only offers regional LBs and regional IPs.

FactsTier facts
  • Premium is the default.
  • Premium: traffic stays on Google's network until the closest edge to the user - egress point near the destination ("cold potato").
  • Standard: traffic exits to the public internet near the source region ("hot potato") - cheaper, but leaves Google's network sooner.
  • Tier can be set at the project default level or per-resource (per IP / per forwarding rule).
DECISIONWhen is Standard the right call?
Global user base, latency-sensitivePremium
Batch/backups, cost-sensitive egressStandard
Users in the same region as the resourceStandard
Needs global LB or global IPPremium (mandatory)
Pick this when: regional, cost-sensitive, users near the resource region

What network traffic costs

Ingress is free; egress is where the meter runs. Incoming traffic is not charged - unless a resource such as a load balancer processes it (and the response counts as billable egress).

TrafficCharged?
Ingress (no processing resource)Free
Ingress processed by a load balancerCharged (as egress)
Egress to same zone via internal IPFree
Egress to Google products (YouTube, Maps, Drive)Free
Egress to another Google Cloud service in the same regionFree
Egress between zones in the same regionCharged
Egress within a zone via external IPCharged
Egress between regionsCharged
GotchaExternal IP defeats the free same-zone egress

Same-zone egress is free only through the instance's internal IP. Over an external IP, Compute Engine cannot tell the VM's zone, so it bills the traffic like cross-zone egress in the same region.

NumbersEgress rates (illustrative, `us-central1`)
  • Cross-zone in the same region: ~$0.01/GB.
  • Same-zone via an external IP: ~$0.01/GB (internal IP is free).
  • Between US ↔ Canada regions: ~$0.01/GB; other inter-region rates vary.
  • Rates change - confirm with the calculator (below).
NumbersExternal IP address pricing
  • Static and ephemeral external IPs are charged; ordered high → low ($/hr, us-central1): unused static ~$0.010 > in-use standard VM ~$0.004 > preemptible ~$0.002.
  • A reserved static IP not attached to any resource costs more than one that is in use - unused reservations are penalized.
  • Free when attached to a forwarding rule, Cloud NAT gateway, or VPN tunnel.
  • External IPs on preemptible VMs are cheaper than on standard VMs.
GotchaPrices change - confirm with the calculator

Rates and exceptions change over time. Use the Google Cloud Pricing Calculator (web tool) to estimate cost of a resource set: pick instance type, region, and expected egress; adjust currency and time frame; then email the estimate or save it to a URL. Each service has its own pricing model, so always verify against current docs.

0%0 of 147 pages studied