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(VPC-1 -> VPC-2)

5 TiB of data(VPC-2 -> VPC-1)

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(Los Angeles -> Mumbai)

5 TiB of data transferred(Mumbai -> Los Angeles)

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.

What's next