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 Interconnect connections and VLAN attachments.

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 gigabytes (GB) transferred and the region that the traffic is coming from.

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 egress charges accrue to the project that owns the VLAN attachment. The project that owns the Interconnect connection is not billed for egress. Specifically, costs for egress traffic from a VLAN attachment in a Shared VPC service project, which travels through an Interconnect connection in a different host project, are attributed to the service project.

Pricing tables

Dedicated Interconnect pricing
Resource Price
Interconnect connection $2.328 per hour per 10-Gbps circuit
Interconnect connection $18.05 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
Egress traffic from a VPC network through an Interconnect connection
Region Price
Asia (asia-east1, asia-east2, asia-northeast1, asia-northeast2, asia-northeast3, asia-south1, asia-southeast1, asia-southeast2) $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, us-west4) $0.02 per GB
South America (southamerica-east1) $0.06 per GB
Australia (australia-southeast1) $0.042 per GB
Ingress traffic through an Interconnect connection
Traffic type Price
Ingress

Google does not charge for ingress traffic. However, there might be a charge for resources that process ingress traffic. For a list of these resources, see the VPC section of All networking pricing.

Responses to requests count as egress 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
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 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 Interconnect connection circuit) 6 x 10-Gbps attachment x 24 hrs @ $0.10 per hour x 30 days = $432.00
Egress traffic
(leaving us-central1 region over Cloud Interconnect)
20 TB 20,480 GB 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. 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.

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 gigabytes (GB) transferred and the region that the traffic is coming from.

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.

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
Egress traffic from a VPC network through an Interconnect connection
Region Price
Asia (asia-east1, asia-east2, asia-northeast1, asia-northeast2, asia-northeast3, asia-south1, asia-southeast1, asia-southeast2) $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, us-west4) $0.02 per GB
South America (southamerica-east1) $0.06 per GB
Australia (australia-southeast1) $0.042 per GB
Ingress traffic through an Interconnect connection
Traffic type Price
Ingress

Google does not charge for ingress traffic. However, there might be a charge for resources that process ingress traffic. For a list of these resources, see the VPC section of All networking pricing.

Responses to requests count as egress 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
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 different pricing scenarios for how Google Cloud calculates pricing for Cloud Interconnect egress traffic; 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:

For more information about 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 VPC regional dynamic routing provided by Cloud Router.

VM in same continent, regional routing (click to enlarge),
              Cloud Interconnect egress charges for North America,
               no region-to-region egress charges.
VM in same continent, regional routing (click to enlarge)
Cloud Interconnect egress charges for North America
No region-to-region egress charges

You order an 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 Interconnect connection in SJC, you are charged the following rates:

  • Cloud Interconnect egress charges for North America (because that is where the Interconnect connection is located).
  • You are not charged region-to-region egress charges.

A VM in the same continent as 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.

VM in same continent, global dynamic routing (click to enlarge),
              Region-to-region egress charges for us-east1 to us-west1,
              Cloud Interconnect egress charges for North America from us-west1 to on-premises.
VM in same continent, global dynamic routing (click to enlarge)
Region-to-region egress charges from us-east1 to us-west1
Cloud Interconnect egress charges for North America from us-west1 to on-premises

You order an 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 egress charges for forwarding traffic from us-east1 to the VLAN attachment in us-west1. The VLAN 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 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 egress rates.

VM in a different continent, global dynamic routing (click to enlarge),
              Intercontinental region-to-region egress charges for traffic forwarded from
              asia-east1 to us-west1,
              Cloud Interconnect egress charges for North America from us-west1 to on-premises.
VM in a different continent, global dynamic routing (click to enlarge)
Intercontinental region-to-region egress charges for traffic forwarded from asia-east1 to us-west1
Cloud Interconnect egress charges for North America from us-west1 to on-premises

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 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 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.

VM in a different continent, VPC Network Peering (click to enlarge),
              Cloud Interconnect egress charges for Asia Pacific from asia-northeast1 to on-premises,
               Intercontinental region-to-region egress charges for traffic forwarded from
              us-east4 to asia-northeast1.
VM in a different continent, VPC Network Peering (click to enlarge)
Intercontinental region-to-region egress charges for traffic forwarded from us-east4 to asia-northeast1
Cloud Interconnect egress charges for Asia Pacific from asia-northeast1 to on-premises

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 egress charges for traffic forwarded from us-east4 to asia-northeast1.
  • Cloud Interconnect egress charges for Asia Pacific 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 egress 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 egress charges to reach the region of the VLAN attachment, and then pay the Cloud Interconnect egress charges based on the continent where the 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 VLAN attachment is located.

Non-VM in two North American regions, global dynamic routing (click to enlarge),
              Cloud Storage egress charges for traffic
            forwarded from a Cloud Storage bucket in northamerica-northeast1 to us-west1,
              Cloud Interconnect egress charges for North America from us-west1
              to on-premises.
Non-VM in two North American regions, global dynamic routing (click to enlarge)
Cloud Storage egress charges for traffic forwarded from a Cloud Storage bucket in northamerica-northeast1 to us-west1
Cloud Interconnect egress charges for North America from us-west1 to on-premises

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 an 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 egress cost for forwarding traffic from a Cloud Storage bucket in northamerica-northeast1 to a VLAN 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 (because that is where your Interconnect connection is located).

If the Cloud Storage bucket is located in a different continent than the VLAN attachment, you pay Cloud Storage intercontinental egress 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.