Network Connectivity pricing
This page describes pricing for all Network Connectivity products.
Cloud VPN pricing
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 tebibytes (TiB) of data through the tunnel, from your Virtual Private Cloud (VPC) network to your data center. At the same time, you send 2 TiB 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 | Data transfer | Data transfer in | IP address | Total |
---|---|---|---|---|
us-central1 gateway ($0.050) x 2 tunnels x 720 hours = $72.00 |
2 TiB (or 2,048 GiB) x $0.11 = $225.28 | No charge for data transfer in. | 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 TiB of data from Cloud Storage and send it to the Tokyo data center.
- Networks A and B send each other about 20 TiB 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 | Data transfer | Data transfer in | IP address | Total |
---|---|---|---|---|
asia-northeast1 gateway ($0.075), with four tunnels x 720 hours
= $216.00 |
Traffic to the data center: 10 TiB (or 10,240 GiB) x $0.14 = $1,433.60 |
No charge for data transfer in. | No charge for a reserved external IP address that is used by a tunnel. | $3,288.00 |
Traffic to Network B: 20 TiB (or 20,480 GiB) x $0.08 = $1,638.40 |
No charge for data transfer in. | |||
europe-west6 gateway ($0.065) x 2 tunnels x 720 hours
= $93.60 |
Traffic to Network A: 20 TiB (or 20,480 GiB) x $0.08 = $1,638.40 |
No charge for data transfer in. | 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 data transfer out. | No charge for data transfer in. | One unused external IP address in southamerica-east1 ($0.015) x 720 hours =
$10.80. |
$10.80 |
Grand total | $5,030.80 |
Cloud Interconnect pricing
This document explains Cloud Interconnect pricing details.
If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.Dedicated Interconnect
Google charges you on an hourly basis for both Cloud Interconnect connections and VLAN attachments. The hourly charge for each resource, either Cloud Interconnect connection or VLAN attachment, is charged to the project that owns the resource.
Data transfer from your Virtual Private Cloud (VPC) networks through your Cloud Interconnect connections is discounted compared to general network pricing for Google Cloud. Data transfer out pricing depends on the number of gibibytes (GiB) transferred and the location of your Cloud Interconnect connection.
This discounted pricing applies only to traffic that originates in the region where the VLAN attachment is located. You can use VLAN attachments to access services located in a different region than the VLAN attachment. In this case, you are charged standard cross-region rates for traffic between the region where the VLAN attachment is located and the region where the service is located.
Cloud Interconnect data transfer out charges accrue to the project that owns the VLAN attachment. The project that owns the Cloud Interconnect connection is not billed for the data transfer. Specifically, costs for data transfer from a VLAN attachment in a Shared VPC service project, which travels through a Cloud Interconnect connection in a different host project, are attributed to the service project.
For HA VPN over Cloud Interconnect deployments, you are charged for your Dedicated Interconnect connections, VLAN attachments, HA VPN tunnels, and regional external IP addresses, if an IP address is assigned to a VPN gateway but not used by a tunnel.
In terms of HA VPN over Cloud Interconnect data transfer, you are charged only for Cloud Interconnect data transfer out. You are not charged for Cloud VPN data transfer.
For more information, see Cloud VPN pricing.
Pricing tables
Dedicated Interconnect pricing
Resource | Price |
---|---|
Cloud Interconnect connection | $2.328 per hour per 10-Gbps circuit |
Cloud Interconnect connection | $23.28 per hour per 100-Gbps circuit |
A 50-, 100-, 200-, 300-, 400-, or 500-Mbps VLAN attachment | $0.10 per hour per VLAN attachment |
A 1-, 2-, 5-, or 10-Gbps VLAN attachment | $0.10 per hour per VLAN attachment |
A 20-Gbps VLAN attachment | $0.20 per hour per VLAN attachment |
A 50-Gbps VLAN attachment | $0.50 per hour per VLAN attachment |
Data transfer from a VPC network through a Cloud Interconnect connection
North America
The following table shows the prices for the North America geographic area.Connection location | Region of VLAN attachment | Price |
---|---|---|
United States, Canada | United States, Canada | $0.020 per GiB |
Mexico | United States, Canada | $0.1107 per GiB |
Europe, Middle East, and Africa (EMEAR)
The following table shows the prices for the Europe, Middle East, and Africa (EMEAR) geographic area.Connection location | Region of VLAN attachment | Price |
---|---|---|
Europe | Europe | $0.020 per GiB |
Middle East | Europe | $0.100 per GiB |
Africa | Europe | $0.110 per GiB |
Middle East | Middle East | $0.090 per GiB |
Europe | Middle East | $0.100 per GiB |
Africa | Africa | $0.110 per GiB |
Asia
The following table shows the prices for the Asia geographic area.Connection location | Region of VLAN attachment | Price |
---|---|---|
Asia* | Asia* | $0.042 per GiB |
Indonesia | Asia* | $0.0594 per GiB |
Indonesia | Indonesia | $0.0484 per GiB |
Asia* | Indonesia | $0.0594 per GiB |
Manila | Indonesia | $0.1306 per GiB |
India | India | $0.045 per GiB |
Australia
The following table shows the prices for the Australia geographic area.Connection location | Region of VLAN attachment | Price |
---|---|---|
Australia | Australia | $0.042 per GiB |
South America
The following table shows the prices for the South America geographic area.Connection location | Region of VLAN attachment | Price |
---|---|---|
South America | South America | $0.110 per GiB |
South America | United States | $0.1107 per GiB |
Inbound data transfer through a Cloud Interconnect connection
Traffic type | Price |
---|---|
Data transfer in | Google does not charge for inbound data transfer. However, there might be a charge for resources that process the transferred data. For a list of these resources, see the VPC section of All networking pricing. Responses to requests count as outbound data transfer traffic and are charged. |
Pricing example
The following table shows an example usage pattern of Dedicated Interconnect connections for a single month.
Resources | Usage | Estimated cost |
---|---|---|
Cloud Interconnect connection | capacity 30 Gbps (3 x 10-Gbps circuit) | 3 x 10-Gbps circuit x 24 hrs @ $2.328 per hour x 30 days = $5,028.48 |
Redundant Cloud Interconnect connection | capacity 30 Gbps (3 x 10-Gbps circuit) | 3 x 10-Gbps circuit x 24 hrs @ $2.328 per hour x 30 days = $5,028.48 |
VLAN attachment | 6 (one per Cloud Interconnect connection circuit) | 6 x 10-Gbps attachment x 24 hrs @ $0.10 per hour x 30 days = $432.00 |
Data transfer (leaving from a Google Cloud region in the United States over a Cloud Interconnect connection in the United States) |
20 TiB | 20,480 GiB x $0.02 = $409.60 |
Total cost | $10,898.56 |
Partner Interconnect
Google charges you on an hourly basis for VLAN attachments, depending on their capacity. The hourly charges are billed to the project that owns the VLAN attachment. Your service provider might also charge you for services such as using their network, which isn't included in your Google Cloud bills. For information about their pricing, contact your service provider.
Data transfer from your VPC networks though your attachments is discounted compared to general network pricing for Google Cloud. Outbound data transfer pricing depends on the number of gibibytes (GiB) transferred and the location of your Cloud Interconnect connection.
This discounted pricing applies only to traffic that originates in the region where the VLAN attachment is located. You can use VLAN attachments to access services located in a different region than the VLAN attachment. In this case, you are charged standard cross-region rates for traffic between the region where the VLAN attachment is located and the region where the service is located.
Cloud Interconnect data transfer out charges accrue to the project that owns the VLAN attachment. The project that owns the Cloud Interconnect connection is not billed for data transfer. Specifically, costs for data transfer traffic from a VLAN attachment in a Shared VPC service project, which travels through a Cloud Interconnect connection in a different host project, are attributed to the service project.
For HA VPN over Cloud Interconnect deployments, you are charged for your VLAN attachments, HA VPN tunnels, and regional external IP addresses, if an address is assigned to a VPN gateway but not used by a tunnel.
In terms of HA VPN over Cloud Interconnect data transfer, you are charged only for Cloud Interconnect outbound data transfer. You are not charged for Cloud VPN data transfer.
For more information, see Cloud VPN pricing.
Pricing tables
Partner Interconnect pricing
Partner VLAN attachment capacity | Price |
---|---|
50 Mbps | $0.05417 per hour per VLAN attachment |
100 Mbps | $0.0625 per hour per VLAN attachment |
200 Mbps | $0.08333 per hour per VLAN attachment |
300 Mbps | $0.1111 per hour per VLAN attachment |
400 Mbps | $0.1389 per hour per VLAN attachment |
500 Mbps | $0.1736 per hour per VLAN attachment |
1 Gbps | $0.2778 per hour per VLAN attachment |
2 Gbps | $0.5694 per hour per VLAN attachment |
5 Gbps | $1.25 per hour per VLAN attachment |
10 Gbps | $2.36 per hour per VLAN attachment |
20 Gbps | $3.61 per hour per VLAN attachment |
50 Gbps | $9.02 per hour per VLAN attachment |
Data transfer from a VPC network through a Cloud Interconnect connection
North America
The following table shows the prices for the North America geographic area.Connection location | Region of VLAN attachment | Price |
---|---|---|
United States, Canada | United States, Canada | $0.020 per GiB |
Mexico | United States, Canada | $0.1107 per GiB |
Europe, Middle East, and Africa (EMEAR)
The following table shows the prices for the Europe, Middle East, and Africa (EMEAR) geographic area.Connection location | Region of VLAN attachment | Price |
---|---|---|
Europe | Europe | $0.020 per GiB |
Middle East | Europe | $0.100 per GiB |
Africa | Europe | $0.110 per GiB |
Middle East | Middle East | $0.090 per GiB |
Europe | Middle East | $0.100 per GiB |
Africa | Africa | $0.110 per GiB |
Asia
The following table shows the prices for the Asia geographic area.Connection location | Region of VLAN attachment | Price |
---|---|---|
Asia* | Asia* | $0.042 per GiB |
Indonesia | Asia* | $0.0594 per GiB |
Indonesia | Indonesia | $0.0484 per GiB |
Asia* | Indonesia | $0.0594 per GiB |
Manila | Indonesia | $0.1306 per GiB |
India | India | $0.045 per GiB |
Australia
The following table shows the prices for the Australia geographic area.Connection location | Region of VLAN attachment | Price |
---|---|---|
Australia | Australia | $0.042 per GiB |
South America
The following table shows the prices for the South America geographic area.Connection location | Region of VLAN attachment | Price |
---|---|---|
South America | South America | $0.110 per GiB |
South America | United States | $0.1107 per GiB |
Inbound data transfer through a Cloud Interconnect connection
Traffic type | Price |
---|---|
Data transfer in | Google does not charge for inbound data transfer. However, there might be a charge for resources that process the transferred data. For a list of these resources, see the VPC section of All networking pricing. Responses to requests count as outbound data transfer traffic and are charged. |
Pricing example
The following table shows an example usage pattern of Partner Interconnect connections for a single month.
Resources | Usage | Estimated cost |
---|---|---|
VLAN attachment | 6 100-Mbps attachments | 6 x $0.0625 x 720 hours = $270.00 |
Data transfer out (leaving from a Google Cloud region in the United States over a Cloud Interconnect connection in the United States) |
20 TiB | 20,480 GiB x $0.02 = $409.60 |
Total cost | $679.60 |
Cross-Cloud Interconnect
Google charges you on an hourly basis for both Cross-Cloud Interconnect connections and VLAN attachments. The hourly charge for each resource, either Cross-Cloud Interconnect connection or VLAN attachment, is charged to the project that owns the resource.
Data transfer from your Virtual Private Cloud (VPC) networks through your Cross-Cloud Interconnect connections is discounted compared to general network pricing for Google Cloud. Data transfer pricing depends on the number of gibibytes (GiB) transferred and the location of your Cross-Cloud Interconnect connection.
This discounted pricing applies only to traffic that originates in the region where the VLAN attachment is located. You can use VLAN attachments to access services located in a different region than the VLAN attachment. In this case, you are charged standard cross-region rates for traffic between the region where the VLAN attachment is located and the region where the service is located.
Cross-Cloud Interconnect data transfer out charges accrue to the project that owns the VLAN attachment. The project that owns the Cloud Interconnect connection is not billed for data transfer. Specifically, costs for data transfer from a VLAN attachment in a Shared VPC service project, which travels through a Cloud Interconnect connection in a different host project, are attributed to the service project.
For HA VPN over Cloud Interconnect deployments, you are charged for your Cross-Cloud Interconnect connections, VLAN attachments, HA VPN tunnels, and regional external IP addresses, if an IP address is assigned to a VPN gateway but not used by a tunnel.
In terms of HA VPN over Cloud Interconnect data transfer out, you are charged only for Cloud Interconnect data transfer. You are not charged for Cloud VPN data transfer.
For more information, see Cloud VPN pricing.
Pricing tables
Cross-Cloud Interconnect pricing
Resource | Price |
---|---|
Cross-Cloud Interconnect connection | $5.60 per hour per 10-Gbps circuit |
Cross-Cloud Interconnect connection | $30 per hour per 100-Gbps circuit |
A 50-, 100-, 200-, 300-, 400-, or 500-Mbps VLAN attachment | $0.10 per hour per VLAN attachment |
A 1-, 2-, 5-, or 10-Gbps VLAN attachment | $0.10 per hour per VLAN attachment |
A 20-Gbps VLAN attachment | $0.20 per hour per VLAN attachment |
A 50-Gbps VLAN attachment | $0.50 per hour per VLAN attachment |
Data transfer from a VPC network through a Cloud Interconnect connection
North America
The following table shows the prices for the North America geographic area.Connection location | Region of VLAN attachment | Price |
---|---|---|
United States, Canada | United States, Canada | $0.020 per GiB |
Mexico | United States, Canada | $0.1107 per GiB |
Europe, Middle East, and Africa (EMEAR)
The following table shows the prices for the Europe, Middle East, and Africa (EMEAR) geographic area.Connection location | Region of VLAN attachment | Price |
---|---|---|
Europe | Europe | $0.020 per GiB |
Middle East | Europe | $0.100 per GiB |
Africa | Europe | $0.110 per GiB |
Middle East | Middle East | $0.090 per GiB |
Europe | Middle East | $0.100 per GiB |
Africa | Africa | $0.110 per GiB |
Asia
The following table shows the prices for the Asia geographic area.Connection location | Region of VLAN attachment | Price |
---|---|---|
Asia* | Asia* | $0.042 per GiB |
Indonesia | Asia* | $0.0594 per GiB |
Indonesia | Indonesia | $0.0484 per GiB |
Asia* | Indonesia | $0.0594 per GiB |
Manila | Indonesia | $0.1306 per GiB |
India | India | $0.045 per GiB |
Australia
The following table shows the prices for the Australia geographic area.Connection location | Region of VLAN attachment | Price |
---|---|---|
Australia | Australia | $0.042 per GiB |
South America
The following table shows the prices for the South America geographic area.Connection location | Region of VLAN attachment | Price |
---|---|---|
South America | South America | $0.110 per GiB |
South America | United States | $0.1107 per GiB |
Inbound data transfer through a Cloud Interconnect connection
Traffic type | Price |
---|---|
Data transfer in | Google does not charge for inbound data transfer. However, there might be a charge for resources that process the transferred data. For a list of these resources, see the VPC section of All networking pricing. Responses to requests count as outbound data transfer traffic and are charged. |
Pricing example
The following table shows an example usage pattern of Cross-Cloud Interconnect connections for a single month.
Resources | Usage | Estimated cost |
---|---|---|
Cross-Cloud Interconnect connection | capacity 10 Gbps (1 x 10-Gbps circuit) | 1 x 10-Gbps circuit x 24 hrs @ $5.60 per hour x 30 days = $4,032 |
Redundant Cross-Cloud Interconnect connection | capacity 10 Gbps (1 x 10-Gbps circuit) | 1 x 10-Gbps circuit x 24 hrs @ $5.60 per hour x 30 days = $4,032 |
VLAN attachment | 2 (one per Cloud Interconnect connection circuit) | 2 x 10-Gbps attachment x 24 hrs @ $0.10 per hour x 30 days = $144.00 |
Data transfer (leaving from a Google Cloud region in the United States over a Cloud Interconnect connection in the United States) |
200 TiB | 204,800 GiB x $0.02 = $4,096.00 |
Total cost | $12,304 |
Pricing scenarios
This section describes different pricing scenarios for how Google Cloud calculates pricing for Cloud Interconnect outbound data transfer; that is, when a virtual machine (VM) instance or a non-VM Google Cloud product or service sends traffic to your on-premises location over a VLAN attachment located in the same or different geographical location:
- A VM in the same region as a VLAN attachment, using either regional or global VPC dynamic routing
- A VM in the same continent but different region than a VLAN attachment, using global VPC dynamic routing
- A VM in a different continent than a VLAN attachment, using global VPC dynamic routing
- A VM in a different continent than a VLAN attachment, using VPC Network Peering
- A non-VM Google Cloud product or service in a different location than a VLAN attachment, using global VPC dynamic routing
For more information about costs for each scenario, including data transfer charges between regions within a continent and between continents, see General network pricing.
A VM in the same region as a VLAN attachment, using either regional or global VPC dynamic routing
In this scenario, there are two regions within North America,
us-west1
and us-east1
. These regions use
VPC regional dynamic
routing provided by Cloud Router. In this scenario, it doesn't matter which dynamic routing mode you use.
You order a Cloud Interconnect connection running from your
on-premises location to San Jose (SJC)
and create two VLAN
attachments over that connection. One VLAN attachment goes to region
us-east1
, and the other VLAN attachment goes to region
us-west1
.
If you send traffic from a VM in us-east1
or from a VM in
us-west1
to your on-premises location over your
Cloud Interconnect connection in SJC, you are charged the following rates:
- Cloud Interconnect data transfer out charges for North America (because that is where the Cloud Interconnect connection is located).
- You are not charged region-to-region data transfer charges because the VMs are using a VLAN attachment in the same region.
A VM in the same continent but different region than a VLAN attachment, using global VPC dynamic routing
In this scenario, you have VMs in two regions located in North America,
us-west1
and us-east1
. You have enabled global
dynamic routing for your VPC network by using Cloud Router.
Global dynamic routing enables VLAN attachments in one region to be used
by one or more VMs located in another region.
You order a Cloud Interconnect connection running from your
on-premises location to San Jose (SJC)
and create one VLAN
attachment over that connection to us-west1
. You then send traffic
from a VM in us-east1
to your on-premises location through the
VLAN attachment located in us-west1
. You are then charged
the following rates:
- Region-to-region data transfer charges for forwarding traffic from
us-east1
to the VLAN attachment inus-west1
. The VLAN attachment inus-west1
is considered the source of traffic. - Cloud Interconnect data transfer charges for North America
for traffic from region
us-west1
to your on-premises location.
A VM in a different continent than a VLAN attachment, using global VPC dynamic routing
This scenario is the same as the preceding example, except that one region,
us-west1
, is located in North America, and the other region,
asia-east1
, is located in Asia. Sending traffic between regions on
different continents results in more expensive inter-region data transfer rates.
The only way to send traffic from asia-east1
over
Cloud Interconnect in North America is by enabling VPC
global dynamic routing. This makes the VLAN attachment in
us-west1
available to VMs in all regions in your VPC
network. You are then charged the following rates:
- Intercontinental region-to-region data transfer charges for traffic forwarded
from
asia-east1
tous-west1
. - Cloud Interconnect data transfer charges for North America for traffic
from region
us-west1
to your on-premises location.
A VM in a different continent than a VLAN attachment, using VPC Network Peering
This scenario is similar to the preceding example, except that there are two VPC networks connected through VPC Network Peering. Sending traffic between regions results in the same rates as the preceding example that uses global dynamic routing.
You send traffic from us-east4
to your on-premises network over
Cloud Interconnect in Asia by using VPC Network Peering.
You are then charged the following rates:
- Intercontinental region-to-region data transfer charges for traffic forwarded
from
us-east4
toasia-northeast1
. - Cloud Interconnect data transfer charges for Asia for traffic
from region
asia-northeast1
to your on-premises location.
A non-VM Google Cloud product or service in a different location than a VLAN attachment, using global VPC dynamic routing
In addition to the preceding scenarios, Cloud Interconnect data transfer charges apply to traffic sent from a Google Cloud product or service that is not a VM to your on-premises location over a VLAN attachment. You pay the product's data transfer charges to reach the region of the VLAN attachment, and then pay the Cloud Interconnect data transfer out charges based on the continent where the Cloud Interconnect connection is located.
The following example describes charges for traffic transferring out from a
Cloud Storage bucket in a different region in North America
than the region where the VLAN attachment is located.
In this scenario, you have resources in two regions located in North America,
us-west1 (Oregon)
and northamerica-northeast1 (Montreal)
. You have enabled
global
dynamic routing for your VPC network by using Cloud Router.
You order a Cloud Interconnect connection running from
your on-premises location to San Jose (SJC)
and create one VLAN
attachment over that connection to us-west1
. You then send traffic from a
Cloud Storage bucket in northamerica-northeast1
to your on-premises
location through the VLAN attachment located in us-west1
. You are
charged the following rates:
- The Cloud Storage data transfer cost for forwarding traffic from a
Cloud Storage bucket in
northamerica-northeast1
to a VLAN attachment inus-west1
. - Cloud Interconnect data transfer charges for
North America
for traffic from regionus-west1
to your on-premises location (because that is where your Cloud Interconnect connection is located).
If the Cloud Storage bucket is located in a different continent than
the VLAN attachment, you pay Cloud Storage intercontinental
data transfer charges to reach the VLAN attachment in us-west1
.
For a full list of pricing scenarios for Cloud Storage, see the Cloud Storage pricing page.
Cloud Router pricing
Cloud Router is provided free of charge. General networking costs apply to control plane (BGP) traffic. In most cases, these costs are negligible.
For more information about networking costs, see General network pricing in the Virtual Private Cloud (VPC) documentation.
Network Connectivity Center pricing
This document describes pricing for Network Connectivity Center.
Network Connectivity Center is a hub-and-spoke model for network connectivity management in Google Cloud. With this model, virtual private cloud networks and on-premises networks connect to a Network Connectivity Center hub by using spokes that have supported Google Cloud spoke resources attached to them.
For more information about Network Connectivity Center, see the Network Connectivity Center overview.
Current pricing
The following sections describe the current pricing for Network Connectivity Center.
Hubs and spokes
The following table describes charges for hubs and spokes. Spoke hours refers to the number of hours within a month that a spoke is active.
Spoke hour charges are waived for up to three VPN spokes and three Cloud Interconnect spokes.
Resource | Price per month |
---|---|
Hub | No charge |
Spoke hours (Cloud Interconnect, Cloud VPN and Cloud Router appliance spokes) | $0.075 per hour |
Spoke hours (VPC spokes) | $0.10 per hour |
Data transfer
Data transfer refers to region-to-region traffic that uses Google's network to connect non-Google Cloud networks.
Network Connectivity Center Data transfer traffic is different from data transfer in and data transfer out, which flows either into or out of Google's network. In contrast, Network Connectivity Center data-transfer does both: it flows into and out of Google's network, because it originates and terminates outside of Google's network.
Data transfer charges are based on gibibytes (GiB) of traffic per month.
Advanced Data Networking
Advanced Data Networking (ADN) refers to the processing fee charged for all traffic that is sent from a spoke through a hub.
The ADN charge is $0.02 per Gibibyte (GiB) per month.
This charge currently applies for traffic between VPC spokes. ADN charges for hybrid spokes are currently waived.
Pricing example
Advanced Data Networking
In this example, an enterprise has two Virtual Private Cloud (VPC) global networks, VPC-1 and VPC-2, which it connects via VPC spokes to their Network Connectivity Center hub. Each VPC is in its own project distinct from the hub project.
Each month, VPC-1 sends 10 TiB of data to VPC-2, and VPC-2 sends 5 TiB of data to VPC-1.
The following table describes the charges for one 30-day month.
Resources | Usage | Formula | Estimated monthly cost |
---|---|---|---|
Spoke hour charges |
2 spokes | 2 x 24 hours x 30 days at $0.10 | $144 |
Advanced Data Networking charges |
10 TiB of data 5 TiB of data |
10 TiB (10 * 1024 GiB = 10,240 GiB) at $0.02 per GiB 5 TiB (5 *1024 GiB = 5120 GiB) at $0.02 per GiB |
$204.80 + $102.40 |
Total cost | 15 TiB of data |
$451.20 |
Note that both the Spoke hour charges and Advanced Data Networking charges for VPC spokes accrue in their respective projects.
Data transfer
In this example, an enterprise connects two Router appliance spokes to their Network Connectivity Center
hub. One spoke represents an office in Los Angeles (us-west2
). Another represents an
office in Mumbai (asia-south1
).
Every month, the US office transfers 5 TiB of data to the Asia office, and the Asia office transfers 5 TiB to the US office.
The following table describes the charges for one 30-day month.
Resources | Usage | Formula | Estimated monthly cost |
---|---|---|---|
Spoke hour charges |
2 spokes | 2 x 24 hours x 30 days at $0.075 | $108.00 |
Data transfer charges |
5 TiB of data transferred 5 TiB of data transferred Total: 10 TiB between one unique site pair. |
5 TiB (5 * 1,024 GiB = 5,120 GiB) at $0.11 per GiB 5 TiB (5 * 1,024 GiB = 5,120 GiB) at $0.11 per GiB |
$563.20 $563.20 |
Advanced Data Networking |
10 TiB of data |
10 TiB (10 * 1,024 GiB = 10,240 GiB) at $0.02 per GiB |
$204.80 Currently waived |
Total cost |
$1,234.40 |
Pricing for other Google Cloud resources
The pricing on this page does not include charges for other Google Cloud resources and products that you might be using in conjunction with Network Connectivity Center. For example:
- If you use Router appliance spokes, you pay for the underlying Compute Engine resources.
- If you use VLAN attachment spokes, you pay for the underlying Cloud Interconnect resources.
- If you use VPN spokes, you pay for the underlying Cloud VPN resources.
Router appliance pricing
Pricing for Router appliance is part of Network Connectivity Center pricing. For pricing, see Network Connectivity Center pricing.
For more information about networking costs, see General network pricing in the Virtual Private Cloud documentation.
CDN Interconnect pricing
The special pricing for your traffic egressing from Google Cloud to a CDN provider is automatic. Google works with approved CDN partners in supported locations to allowlist provider IP addresses. This means that any data that you send to your allowlisted CDN provider from Google Cloud is charged at the reduced price. This reduced price applies only to IPv4 traffic. It does not apply to IPv6 traffic.
Traffic between Google Cloud and pre-approved CDN Interconnect locations is billed as follows:
- Ingress traffic is free for all regions.
- Egress traffic rates apply only to data leaving Compute Engine or Cloud Storage. Egress charges
for CDN Interconnect appear on the invoice as
Compute Engine Network Egress via Carrier Peering Network.
For inter-region CDN Interconnect traffic rates, see Internet egress rates.
Intra-region pricing for CDN Interconnect applies only to intra-region egress traffic that is sent to Google-approved CDN Interconnect providers at specific locations that Google approves for those providers.
Consult with your CDN provider to verify that they are an approved provider, and if so, which of their CDN locations are approved for this program. They can help you set up your deployment to use intra-region egress routes when using Google Cloud as the origin source.
Continental location | Intra-region CDN Interconnect traffic rate |
---|---|
NA | $0.04/GB |
EU | $0.05/GB |
APAC | $0.06/GB |
What's next?
- Read the Network Connectivity documentation.
- Get started with Network Connectivity.
- Try the Pricing calculator.