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) 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) Singapore (asia-southeast1) Jakarta (asia-southeast2) Sydney (australia-southeast1) Hong Kong (asia-east2) Taiwan (asia-east1) Tokyo (asia-northeast1) Osaka (asia-northeast2) Seoul (asia-northeast3)
Component billed Price (USD)
Per tunnel (per hour).

For 99.99% availability for HA VPN, you must configure two tunnels, or, if working with an AWS peer gateway, four tunnels.
IPsec traffic Charged as if the traffic were regular egress traffic:
  • If the Cloud VPN tunnel connects to a Cloud VPN gateway, egress pricing to the region containing that gateway applies; see General network pricing.
  • If the Cloud VPN tunnel connects to a VPN gateway outside of Google Cloud, see Internet egress rates.
Cloud VPN gateways are regional resources. If VPN gateways are in the same Google Cloud region, egress traffic is billed as traffic between zones in the same region. If VPN gateways are not in the same region, traffic is billed as traffic between different regions.

If the Cloud VPN tunnel connects to a gateway outside of Google Cloud, Internet egress rates apply.
External IP address for VPN gateway Charged according to IP address pricing.

Google does not charge for forwarding rules that send traffic to the VPN gateway.

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.