Iowa (us-central1) Oregon (us-west1) Los Angeles (us-west2) Salt Lake City (us-west3) Las Vegas (us-west4) Northern Virginia (us-east4) South Carolina (us-east1) Montréal (northamerica-northeast1) Toronto (northamerica-northeast2) São Paulo (southamerica-east1) Belgium (europe-west1) Finland (europe-north1) Frankfurt (europe-west3) London (europe-west2) Netherlands (europe-west4) Zürich (europe-west6) Warsaw (europe-central2) Mumbai (asia-south1) Delhi (asia-south2) Singapore (asia-southeast1) Jakarta (asia-southeast2) Sydney (australia-southeast1) Melbourne (australia-southeast2) Hong Kong (asia-east2) Taiwan (asia-east1) Tokyo (asia-northeast1) Osaka (asia-northeast2) Seoul (asia-northeast3)
Component billed Price (USD)
Hourly charge for each tunnel attached to the gateway.

HA VPN only: For 99.99% availability, you must configure two tunnels, or, if working with an AWS peer gateway, four tunnels.
IPsec traffic You are charged as follows:
  • If the Cloud VPN tunnel connects to another Cloud VPN gateway, you are charged egress pricing as described in VM-VM egress pricing within Google Cloud. If the source and destination Cloud VPN gateways are in the same Google Cloud region, egress traffic is billed as traffic between zones in the same region.
  • If the Cloud VPN tunnel connects to a VPN gateway outside of Google Cloud, you are charged as described in Internet egress rates.
External IP address for VPN gateway You are charged as described in IP address pricing.

An external IP address is charged only if it is not being used by a VPN tunnel.