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

You're charged on a monthly basis for interconnects and on an hourly basis for interconnect attachments (VLANs).

Egress traffic from your Virtual Private Cloud (VPC) networks through your interconnect connections is discounted compared to general network pricing for Google Cloud. Egress pricing depends on the number of GB transferred and the region the traffic is coming from.

This discounted pricing applies only to traffic that originates in the region where the interconnect attachment (VLAN) is located. You can use attachments to access services located in a different region than the attachment. In this case, you are charged standard cross-region rates for traffic between the region where the attachment is located and the region where the service is located.

Pricing tables

Dedicated Interconnect pricing:

Resource Price
Interconnect $1,700 a month per 10 Gbps circuit
Interconnect $13,000 a month per 100 Gbps circuit
A 50, 100, 200, 300, 400, or 500 Mbps interconnect attachment (VLAN) $0.10 per hour per attachment
A 1, 5, or 10 Gbps interconnect attachment (VLAN) $0.10 per hour per attachment
A 20 Gbps interconnect attachment (VLAN) $0.20 per hour per attachment
A 50 Gbps interconnect attachment (VLAN) $0.50 per hour per attachment

Egress traffic from a VPC network through an interconnect:

Region Price
Asia (asia-east1, asia-east2, asia-northeast1, asia-northeast2, asia-northeast3, asia-south1, asia-southeast1) $0.042 per GB
Europe (europe-north1, europe-west1, europe-west2, europe-west3, europe-west4, europe-west6) $0.02 per GB
North America (northamerica-northeast1, us-central1, us-east1, us-east4, us-west1, us-west2, us-west3) $0.02 per GB
South America (southamerica-east1) $0.06 per GB
Australia (australia-southeast1) $0.042 per GB

Pricing example

The following table shows an example usage pattern of Dedicated Interconnect connections for a single month:

Resources Usage Estimated cost
Interconnect capacity 30 Gbps (3 x 10 Gbps circuit) 3 x $1,700 = $5,100
Redundant Interconnect capacity 30 Gbps (3 x 10 Gbps circuit) 3 x $1,700 = $5,100
Interconnect attachment (VLAN) 6 (one per interconnect circuit) 6 x 10G attachment x 24 hrs @ $0.10 per hour x 30 days = $432
Egress traffic
(leaving us-central1 region over Cloud Interconnect)
20 TB 20,480 GB x $0.02 = $409.60
Total cost $11,041.60

Partner Interconnect

Google charges you on a monthly basis for VLAN attachments, depending on their capacity. Your service provider might also charge you for services such as using their network, which isn't included in your GCP bills. Contact your service provider for information about their pricing.

Egress traffic from your VPC networks though your attachments is discounted compared to general network pricing for Google Cloud. Egress pricing depends on the number of GBs transferred and the region the traffic is coming from.

This discounted pricing applies only to traffic that originates in the region where the interconnect attachment (VLAN) is located. You can use attachments to access services located in a different region than the attachment. In this case, you are charged standard cross-region rates for traffic between the region where the attachment is located and the region where the service is located.

Pricing tables

Partner Interconnect pricing:

Partner interconnect attachment (VLAN) capacity Price
50 Mbps $0.05417 per hour per attachment
100 Mbps $0.0625 per hour per attachment
200 Mbps $0.08333 per hour per attachment
300 Mbps $0.1111 per hour per attachment
400 Mbps $0.1389 per hour per attachment
500 Mbps $0.1736 per hour per attachment
1 Gbps $0.2778 per hour per attachment
2 Gbps $0.5694 per hour per attachment
5 Gbps $1.25 per hour per attachment
10 Gbps $2.36 per hour per attachment
20 Gbps $3.61 per hour per attachment
50 Gbps $9.02 per hour per attachment

Egress traffic from a VPC network through an interconnect:

Region Price
Asia (asia-east1, asia-east2, asia-northeast1, asia-northeast2, asia-northeast3, asia-south1, asia-southeast1) $0.042 per GB
Europe (europe-north1, europe-west1, europe-west2, europe-west3, europe-west4, europe-west6) $0.02 per GB
North America (northamerica-northeast1, us-central1, us-east1, us-east4, us-west1, us-west2, us-west3) $0.02 per GB
South America (southamerica-east1) $0.06 per GB
Australia (australia-southeast1) $0.042 per GB

Pricing example

The following table shows an example usage pattern of Partner Interconnect connections for a single month:

Resources Usage Estimated cost
Interconnect attachment (VLAN) 6 100 Mbps attachments 6 x $0.0625 x 720 hours = $270
Egress traffic
(leaving us-central1 region over Cloud Interconnect)
20 TB 20,480 GB x $0.02 = $409.60
Total cost $679.60

Pricing scenarios

This section describes how Google Cloud calculates pricing for Cloud Interconnect egress traffic using different pricing scenarios. 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 an interconnect attachment located in the same or different geographical location:

For more information on costs for each scenario, including egress charges between regions within a continent and between continents, see General network pricing.

A VM in the same continent as an attachment, using regional VPC dynamic routing

In this scenario, there are two regions within North America, us-west1 and us-east1. These regions use Virtual Private Cloud (VPC) regional dynamic routing provided by Cloud Router.

You order a Cloud Interconnect connection running from your on-premises location to San Jose (SJC) and create two interconnect attachments over that connection. One attachment goes to region us-east1, and the other 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 egress charges for North America, since that is where the Cloud Interconnect is located
  • But, you are not charged region-to-region egress charges

A VM in the same continent as an 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 using Cloud Router. Global dynamic routing enables interconnect attachments in one region to be used by one or more VMs located in another region.

You order an Cloud Interconnect connection running from your on-premises location to San Jose (SJC) and create one interconnect attachment over that connection to us-west1. You then send traffic from a VM in us-east1 to your on-premises location through the interconnect attachment located in us-west1. You are then charged the following rates:

  • Region-to-region egress charges for forwarding traffic from us-east1 to the interconnect attachment in us-west1. The interconnect attachment in us-west1 is considered the source of traffic.
  • Cloud Interconnect egress charges for North America for traffic from region us-west1 to your on-premises location.

A VM in a different continent than an 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 egress rates.

The only way to send traffic from asia-east1 over the Cloud Interconnect in North America, is by enabling VPC global dynamic routing. This makes the interconnect 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 egress charges for traffic forwarded from asia-east1 to us-west1
  • Cloud Interconnect egress charges for North America for traffic from region us-west1 to your on-premises location

A non-VM Google Cloud product or service in a different location than an attachment, using global VPC dynamic routing

In addition to the preceding scenarios, Cloud Interconnect egress charges apply to traffic sent from a Google Cloud product or service that is not a VM to your on-premises location over an interconnect attachment. You pay the product's egress charges to reach the region of the interconnect attachment, and then pay the Cloud Interconnect egress charges based on the continent where the Cloud Interconnect connection is located.

The following example describes charges for traffic egressing a Cloud Storage bucket in a different region in North America than the region where the interconnect 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 using Cloud Router.

You order an Cloud Interconnect connection running from your on-premises location to San Jose (SJC) and create one interconnect 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 interconnect attachment located in us-west1. You are charged the following rates:

  • The Cloud Storage egress cost for forwarding traffic from a Cloud Storage bucket in northamerica-northeast1 to an interconnect attachment in us-west1. If the regions were both inside the US location, then there would be no egress charge.
  • Cloud Interconnect egress charges for North America for traffic from region us-west1 to your on-premises location, since that is where the Cloud Interconnect is located.

If the Cloud Storage bucket is located in a different continent than the interconnect attachment, you pay Cloud Storage intercontinental egress charges to reach the interconnect attachment in us-west1.

For a full list of pricing scenarios for Cloud Storage, see the Cloud Storage pricing page.