Pricing

Stay organized with collections Save and categorize content based on your preferences.

At a high level, your Cloud VPN charges consist of the following:

  • An hourly charge for each Cloud VPN gateway; this charge is determined partly by the number of tunnels attached to the gateway, as well as the location of the gateway
  • A monthly charge for IPsec traffic
  • An hourly charge for any external IP address assigned to a VPN gateway but not used by a tunnel

For more information about Cloud VPN, see the Cloud VPN overview.

Pricing table

To view pricing, select the location of the Cloud VPN gateway. Except where otherwise noted, all details apply to both Classic VPN and HA VPN.

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.

Pricing scenarios

For help understanding Cloud VPN pricing, refer to the following examples.

us-central1 gateway to data center

Suppose you have a VPN gateway in us-central1. That gateway uses two tunnels to connect with an on-premises data center in Iowa.

Each month, you send 2 terabytes (TB) of data through the tunnel, from your Virtual Private Cloud (VPC) network to your data center. At the same time, you send 2 TB in the other direction—from the data center to your VPC network.

Additionally, your gateway uses a reserved external IP address.

The following table shows the charges that you'd incur during a 30-day month with this setup.

Gateway Egress traffic Ingress traffic IP address Total
us-central1 gateway ($0.050) x 2 tunnels x 720 hours = $72.00 2 TB (or 2,048 GB) x $0.11 = $225.28 No charge for ingress traffic. No charge for a reserved external IP address that is used by a tunnel. $297.28

asia-northeast1 gateway to data center and another VPC network

Suppose your project has a VPC network called Network A, which includes a VPN gateway in asia-northeast1. This gateway uses two tunnels to connect with an on-premises data center in Tokyo. Additionally, this gateway uses two tunnels to connect with Network B, another VPC network in your project. Network B's gateway is located in europe-west6.

Each month, your data usage is as follows:

  • Users in Network A download 10 TB of data from Cloud Storage and send it to the Tokyo data center.
  • Networks A and B send each other about 20 TB of data.

Both the asia-northeast1 and europe-west6 gateways use reserved external IP addresses.

Additionally, you have a third VPN gateway in southamerica-east1. You created this gateway several months ago and assigned it a reserved external IP address. However, you never set up a tunnel for this gateway.

The following table shows the charges that this setup would incur during a 30-day month.

Gateway Egress traffic Ingress traffic IP address Total
asia-northeast1 gateway ($0.075), with four tunnels x 720 hours = $216.00 Traffic to the data center:
10 TB (or 10,240 GB) x $0.14 = $1,433.60		 No charge for ingress traffic. No charge for a reserved external IP address that is used by a tunnel. $3,288.00
Traffic to Network B:
20 TB (or 20,480 GB) x $0.08 = $1,638.40		 No charge for ingress traffic.
europe-west6 gateway ($0.065) x 2 tunnels x 720 hours = $93.60 Traffic to Network A:
20 TB (or 20,480 GB) x $0.08 = $1,638.40		 No charge for ingress traffic. No charge for a reserved external IP address that is used by a tunnel. $1,732.00
southamerica-east1 gateway ($0.075) x 0 tunnels x 720 hours = no charge No egress traffic. No ingress traffic. One unused external IP address in southamerica-east1 ($0.015) x 720 hours = $10.80. $10.80
Grand total $5,030.80

What's next