All networking pricing

This page describes pricing for networking products.

Virtual Private Cloud

The following prices are applied both during and after the Google Cloud Free Tier period. During the Free Tier period, these prices are charged against the Free Tier credit amount.

General network pricing information

ingress traffic

Traffic coming in to a Google Cloud resource, such as a VM. If you send traffic between two VMs, then the traffic is counted as egress traffic as it leaves one VM and counted as ingress traffic as it arrives at the other VM.

egress traffic

Traffic leaving a Google Cloud resource, such as a VM. Egress traffic is charged based on whether the traffic uses an internal or external IP address, whether the traffic crosses zone or region boundaries, whether the traffic leaves or stays inside Google Cloud, and how far the traffic travels before leaving Google Cloud. When two VMs or two cloud resources internal to Google Cloud communicate with each other, there are two traffic paths—one in each direction. Traffic in each direction is designated as egress at the source and ingress at the destination, and each direction is priced accordingly.

Premium Tier

The Network Service Tiers Premium Tier leverages Google's premium backbone to carry traffic from and to your external users. The public internet is usually only used between the user and the closest Google network ingress point.

Standard Tier

The Network Service Tiers Standard Tier leverages the public internet to carry traffic between your services and your users. While using the public internet provides a lower quality of service, it is more economical than Premium Tier.

Ingress pricing

Traffic type	Price
Ingress	No charge for ingress traffic. However there may be a charge for resource that processes ingress traffic. Services that process ingress traffic are as follows: Load balancers Cloud NAT Protocol forwarding Responses to requests count as egress and are charged.

VM-VM egress pricing within Google Cloud

This section covers traffic that leaves a Google Cloud VM and travels to another Google Cloud VM. The cost is attributed to the project of the VM that is sending the traffic. This pricing affects Compute Engine VMs, Google Kubernetes Engine (GKE) nodes, and VMs running App Engine flexible environment.

The following prices are applied both during and after the Google Cloud Free Tier period. During the Free Tier period, these prices are charged against the Free Tier credit amount.

Traffic type	Price
Egress to the same Google Cloud zone when using the internal IP addresses of the resources^1	No charge
Egress to a different Google Cloud zone in the same Google Cloud region when using the internal IP addresses^1 (per GB)	$0.01
VM-to-VM egress when both VMs are in the same Google Cloud region, regardless of zone, when using the external IP addresses (per GB)	$0.01
VM-to-VM egress when both VMs are in different regions of the same network using internal or external IP addresses	See the rest of this table.
Egress from a Google Cloud region in the US or Canada to another Google Cloud region in the US or Canada (per GB)	$0.01
Egress between Google Cloud regions within Europe (per GB)	$0.02
Egress between Google Cloud regions within Asia (per GB)	$0.05
Egress between Google Cloud regions within South America (per GB)	$0.08
Egress to a Google Cloud region on another continent (excludes Oceania) (per GB)	$0.08
Indonesia and Oceania^2 to/from any Google Cloud region (per GB)	$0.15

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

¹The prices are used regardless of network or subnet. The price for traffic within a zone using internal IP addresses is the same even if the traffic is to a different subnet or network. The price on traffic between zones in the same region is the same if the two instances are in the same subnet, different subnets, or different networks. Pricing is the same whether the instances are in a VPC network or a legacy network.

² Oceania includes Australia, New Zealand, and surrounding Pacific Ocean islands such as Papua New Guinea and Fiji. This region excludes Hawaii.

VM-to-Google Cloud service

This section covers traffic that leaves a Google Cloud VM and travels to a Google service. The cost is attributed to the project of the VM that is sending the traffic. This pricing affects Compute Engine VMs, Google Kubernetes Engine nodes, and VMs running App Engine flexible environment.

The following prices are applied both during and after the Google Cloud Free Tier period. During the Free Tier period, these prices are charged against the Free Tier credit amount.

Traffic type	Price
Egress to specific Google non-cloud products such as YouTube, Maps, Doubleclick, and Drive, whether from a VM in Google Cloud with an external IP address or an internal IP address.	No charge
Egress to a different Google Cloud service within the same region using an external IP address or an internal IP address, except for Memorystore for Redis, Filestore, GKE, and Cloud SQL	No charge
Egress to Memorystore for Redis, Filestore, Cloud SQL, and Google Kubernetes Engine within the same region is priced the same as VM-to-VM traffic.	VM-VM egress pricing within Google Cloud
Egress to a Google Cloud service in a different region.	VM-VM egress pricing within Google Cloud
For Cloud Spanner network pricing, see Cloud Spanner pricing.
For Cloud Storage network pricing, see Cloud Storage pricing.

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

Internet egress rates

The following prices are applied both during and after the Google Cloud Free Tier period. During the Free Tier period, these prices are charged against the Free Tier credit amount.

Note: The monthly usage is counted by each SKU, while the "Wordwide Destinations" may contain multiple SKUs. For more information, see Google Cloud SKUs.

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

^*These rates do not apply for Cloud CDN, CDN Interconnect, Carrier Peering, Direct Peering, and Cloud Interconnect traffic. Instead, see pricing for Cloud CDN, CDN Interconnect, Carrier Peering, Direct Peering, or Cloud Interconnect.

External IP address pricing

You are charged for static and ephemeral external IP addresses according to the following table.

If you reserve a static external IP address and do not assign it to a resource such as a VM instance or a forwarding rule, you are charged at a higher rate than for static and ephemeral external IP addresses that are in use.

You are not charged for static external IP addresses that are assigned to forwarding rules.

In use or not

Google Cloud considers a static external IP address as in use if it is associated with a VM instance whether the instance is running or stopped. If the instance is deleted or if the IP address is dissociated from the instance, Google Cloud considers the static IP address as not in use.

For an ephemeral IP address, Google Cloud considers the address as in use only when the associated VM instance is running. When the instance is stopped or deleted, Google Cloud releases the ephemeral IP address and no longer considers it as in use.

You can check whether a static external IP address is in use by making a gcloud compute addresses list request. This command returns a list of static external IP addresses and their statuses:

gcloud compute addresses list

NAME          REGION  ADDRESS        STATUS
address-1             130.211.8.68   IN_USE
address-2             35.186.217.84  RESERVED

In this example, IPv4 address-1 is in use while IPv4 address-2 is reserved but not being used. Both addresses are charged according to the External IP address pricing table in this document.

Firewall rules

VPC firewall rules are free of charge.

Hierarchical firewall policies and hierarchical firewall policy rules (beta) are offered without charge until General Availability.

Network telemetry

Network logs generate charges. You are charged for the following products:

• VPC Flow Logs
• Firewall Rules Logging
• Cloud NAT logging

Log generation	Price (USD)
0—10 TB per month	0.50/GB
10—30 TB per month	0.25/GB
30—50 TB per month	0.10/GB
>50 TB per month	0.05/GB

Logs are sent to Cloud Logging. Logs can be further exported to Pub/Sub, Cloud Storage, or BigQuery. Pub/Sub, Cloud Storage, or BigQuery charges apply in addition to log generation charges. For more information on exporting logs, see Overview of logs export.

If you store your logs in Cloud Logging, logs generation charges are waived, and only Logging charges apply.

If you send and then exclude your logs from Cloud Logging, log generation charges apply.

Packet Mirroring

You are charged for the amount of data processed by Packet Mirroring. You are not charged for packet mirroring forwarding rules. The costs for the data processed by Packet Mirroring are described in the following table.

Normal egress rates are charged for traffic outbound from a load balancer. There is no additional load balancer egress cost beyond normal egress rates.

Cloud Load Balancing

Load balancing and forwarding rules

The following pricing applies to all types of load balancing other than Internal HTTP(S) Load Balancing. For Internal HTTP(S) Load Balancing, see the Internal HTTP(S) Load Balancing section.

Normal egress rates are charged for traffic outbound from a load balancer. There is no additional load balancer egress cost beyond normal egress rates.

HTTP(S) Load Balancing pricing with Serverless NEGs

If you are using serverless NEG backends for an external HTTP(S) load balancer, existing HTTP(S) Load Balancing charges will apply in addition to the serverless compute charges for Cloud Run (fully managed), Cloud Functions, or App Engine backends. If Google Cloud Armor or Cloud CDN are used, their respective charges also apply.

However, you will not be charged for both serverless egress and Internet egress. Only Internet egress rates apply. Cloud Functions outbound data (egress) charges, App Engine outgoing network traffic charges and Cloud Run (fully managed) egress charges do not apply to requests passed from an HTTP(S) load balancer (using serverless NEGs) to a Cloud Functions, App Engine, or Cloud Run (fully managed) service.

Forwarding rules pricing examples

Google Cloud charges for forwarding rules whether they are created for load balancing or other uses, such as Packet Mirroring.

The following examples use US pricing:

You can create up to 5 forwarding rules for the price of $0.025/hour. For example, if you create one forwarding rule, you are charged $0.025/hour. If you have 3 forwarding rules, you are still charged $0.025/hour. However, if you have 10 forwarding rules, you are charged as follows:

• 5 forwarding rules = $0.025/hour
• Each additional forwarding rule = $0.01/hour

$0.025/hour for 5 rules + (5 additional rules * $0.01/hour) = $0.075/hour

For most load balancing use cases, you need only one forwarding rule per load balancer.

Google Cloud charges for global forwarding rules and regional forwarding rules separately, and also per project. For example, if you use one global forwarding and one regional forwarding rule in two separate projects (four rules total), you are charged $0.10/hour (4 x $0.025/hour).

Estimating load balancing charges

To estimate load balancing charges:

1. Go to the Pricing Calculator.
2. On the Cloud Load Balancing tab.
3. From the dropdown menu, select a region.
4. Enter your estimated number of forwarding rules.
5. Enter your monthly estimated amount of network traffic processed.

For example:

• Iowa
• Forwarding rules: 10
• Network ingress: 2,048 GB
• Total Estimated Cost: USD 71.13 per 1 month

This example doesn't include the egress cost of sending replies from the backends.

Internal HTTP(S) Load Balancing

Proxy instance charge

Internal HTTP(S) Load Balancing is a proxy-based load balancer. The load balancer automatically scales the number of proxies available to handle your traffic based on your traffic needs. The proxy instance charge is based on the number of proxy instances needed to satisfy your traffic needs. Each additional proxy incurs an additional hourly charge according to the prices indicated in the previous table.

The number of proxies is calculated based on the measured capacity needed to handle your traffic over a 10-minute time period. During this time period, we look at the greater of:

• The number of proxies needed to serve your traffic's bandwidth needs. Each proxy instance can handle up to 18 MB per second. We monitor the total bandwidth required and divide that total by the bandwidth that a proxy instance can support.
• The number of proxies needed to handle connections and requests. We count the total of each of the following resources and divide each value by what a proxy instance can handle:
  • 600 (HTTP) or 150 (HTTPS) new connections per second
  • 3,000 active connections
  • 1,400 requests per second*

*A proxy instance can handle 1,400 requests per second if Cloud Logging is disabled. If you enable Logging, your proxy instance can handle fewer requests per second. For example: logging 100% of requests decreases the proxy's request handling capacity to 700 requests per second. You can set Logging to sample a smaller percentage of traffic. This enables you to meet your observability needs while controlling your cost.

Example calculation

In a 10-minute period, 180 MB per second of data pass through the load balancer. 180 MB per second / 18 MB per second per proxy instance = 10 proxy instances

During this same period, 300 new HTTPS connections are established per second, 3,000 connections are active and 2,800 requests are sent per second:

300 new HTTPS connections per second / 150 new HTTPS connections per second per proxy instance = 2 proxy instances 3,000 active connections / 3,000 active connections per proxy instance = 1 proxy instance 2,800 requests per second / 1,400 requests per second per proxy instance = 2 proxy instances

This sums up to 5 proxy instances. This amount is lower than the 10 proxy instances required to serve bandwidth. Thus, the proxy instance charge for this 10-minute time period would be calculated as follows:

10 proxy instances * $0.025 per proxy instance per hour * (10 minutes / (60 minutes per hour)) = $0.0417

Billing is calculated based on the measured capacity needed to satisfy your traffic needs, not the number of proxy instances that are establishing connections to your backends. As such, you might be billed for a different number of proxy instances than you see in your infrastructure.

Minimum proxy instance charge

To ensure optimal performance and reliability, each load balancer is allocated at least three proxy instances in the Google Cloud region where the load balancer is deployed. These proxy instances are allocated even if the load balancer handles no traffic. After a forwarding rule (with load balancing scheme INTERNAL_MANAGED) is deployed to your project, you start to accrue proxy instance charges. Additional forwarding rules incur additional proxy instance charges as described previously (in other words, three additional proxy instances per forwarding rule).

The three proxy instances that are allocated to your load balancer result in a minimum hourly proxy instance charge. For example, for the us-central1 Google Cloud region, the minimum charge is calculated as follows:

3 proxy instances * $0.025 per proxy per hour = $0.075 per hour

As described previously, these proxy instances can each handle a certain amount of traffic. Once your traffic needs surpass the capacity of these three proxy instances, you will incur costs for the proxy instances required to handle any additional traffic.

Data processing charge

The data processing charge is calculated by measuring the total volume of data for requests and responses processed by your load balancer during the billing cycle. This charge scales according to your usage and there is no minimum charge for data processing.

User-defined request headers and Google Cloud Armor charges

If a backend service has a Google Cloud Armor policy associated with it, you can use the user-defined request headers feature with that backend service without any additional charge for the user-defined request headers feature.

If a backend service does not have a Google Cloud Armor policy associated with it, the charges are $0.75 per million HTTP(S) requests sent to those backend services that use the user-defined request headers feature.

Protocol forwarding

Protocol forwarding is charged at the same rates as the load balancing service. There is a charge for a forwarding rule and the ingress data processed by a target instance.

SSL certificates

There is no charge for self-managed and Google-managed SSL certificates.

Google Cloud Armor

This document explains Google Cloud Armor and Google Cloud Armor Managed Protection pricing details. This pricing is active, with the exception of the data processing fee, which becomes active at General Availability.

	Standard Tier	Plus Tier
Billing model	Pay as you go	Subscription
Subscription price	N/A	$3,000/month (includes up to 100 protected resources)
Protected resources	N/A	$30/protected resource per month after initial 100
WAF HTTP requests WAF security policies WAF rules	$0.75 per million requests $5 per policy per month $1 per rule per month	All included
Data processing fee	None	Yes; see the following section.
Time commitment	None	One year

Data processing fee

The Google Cloud Armor Managed Protection data processing fee applies only for egress generated by Managed Protection Plus Tier protected resources. The data processing fee applies when Managed Protection is in General Availability.

Protected resources include all backend services of the following load balancer types in each enrolled project:

• An external HTTP(S) load balancer
• An SSL proxy load balancer
• A TCP proxy load balancer

Prices are per egressed GB. For example, for Cloud Load Balancing, the internet, and Cloud Interconnect, the charge is $0.05 per GB for the first 100 TB egressed.

TBs egressed	Cloud Load Balancing, internet, and Cloud Interconnect	Cloud CDN	Cloud DNS
0-100	$0.05	$0.025	Free
101-500	$0.04	$0.020	Free
501-1000	$0.03	$0.015	Free
1001+	Contact account team	$0.010	Free

If a backend service has a Google Cloud Armor security policy associated with it, you can use the custom headers feature with that backend service without any additional charge for the custom headers feature.

If you pay in a currency other than USD, the prices listed in your currency on Google Cloud Platform SKUs apply.

Cloud CDN

This document discusses pricing for Cloud CDN.

Prices on this page are listed in US dollars (USD). If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

Pricing structure

Case	What you pay for	Notes
Cacheable content, cache hit	cache lookup + cache egress	When Cloud CDN serves your content, you're charged for bandwidth and HTTP/HTTPS requests. The GET and HEAD HTTP methods cause cache lookups. Other methods such as POST and PUT do not. This also applies to Cloud CDN cache hits for cacheable content from custom origins.
Cacheable content, cache miss	cache lookup + cache egress + cache fill + applicable Cloud Load Balancing data processing or Cloud Storage operation charges	Cache fill and cache egress charges apply to cacheable content. On cache misses, any applicable Cloud Load Balancing data processing or Cloud Storage operation charges apply. These charges replace the network egress charges that apply when serving directly from Compute Engine or Cloud Storage. For Cloud CDN cache fills from custom origins, requests to the custom origin are charged at internet egress rates. Cache fills continue to benefit from Google's global backbone network between Google's Cloud CDN edge and origin.
Non-cacheable content	standard Compute Engine + Cloud Storage egress rates	For non-cacheable content, standard Compute Engine and Cloud Storage internet egress rates apply. For custom origins, you're also charged for request bytes sent to custom origins from the load balancer at the standard Compute Engine internet egress rates.

Overview

Cache egress and cache fill are calculated in gigabytes (GB).

Item	Price
Cache egress	$0.02 - $0.20 per GB
Cache fill	$0.01 - $0.04 per GB
HTTP/HTTPS cache lookup requests	$0.0075 per 10,000 requests
Requests sent from Cloud CDN to custom origins	Compute Engine internet egress rates

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

Pricing calculator

You can use the Google Cloud Pricing Calculator to estimate the cost of using Cloud CDN.

Go to the pricing calculator

Commitment-based discounts

If you plan to serve a large volume of content from Cloud CDN (1 PB+ per month), you can contact the Google Cloud sales team to discuss commitment-based discounts.

Cache egress

Cache egress charges represent cached responses served from Cloud CDN's caches, and vary based on the destination and your monthly usage. Monthly usage is calculated per project per destination. Destination is a geographic area determined by the client's IP address.

Destination		Price (per GB) by monthly usage
				First 10 TB	Next 140 TB	Next 850 TB	> 1000 TB
Asia Pacific (including Hong Kong)		$0.09	$0.06	$0.05	$0.04
China^1		$0.20	$0.17	$0.16	$0.145
Europe		$0.08	$0.055	$0.03	$0.02
North America (including Hawaii)		$0.08	$0.055	$0.03	$0.02
Oceania^2		$0.11	$0.09	$0.08	$0.065
South America		$0.09	$0.06	$0.05	$0.04
All other destinations		$0.09	$0.06	$0.05	$0.04

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

¹ Traffic destined for mainland China is served from Google locations outside of mainland China. Performance and reliability may be lower than for traffic served from in-country locations.

² Oceania includes Australia, New Zealand, and surrounding Pacific Ocean islands such as Papua New Guinea and Fiji. This region excludes Hawaii.

Cache fill

Cache fill charges represent the data required to populate Cloud CDN's caches. For typical workloads where you are serving popular content, cache fill is often less than 10% of your total egress GB. Charges vary based on the source and destination, where the source is the region of your backend service, or for custom origins, the geographic area based on your origin's IP address.

Cache fill	Price (per GB)
Within North America or Europe (including Hawaii)	$0.01
Within each of Asia Pacific, South America, Middle East, Africa, and Oceania (including Hong Kong)	$0.02
Inter-region cache fill (for example: between Asia Pacific and North America)	$0.04

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

Pricing example

The following example shows a simple scenario that might apply if you are just getting started with Cloud CDN.

Suppose you have the following Cloud CDN usage pattern in a given month.

Pricing category	Type of usage	Amount
Cache egress	Cache egress in North America	500 GB
Cache fill	Data transfer to Cloud CDN caches	25 GB
Cache lookup requests	GET and HEAD HTTP methods	5,000,000 operations

Your bill for the month is calculated as follows.

Pricing category	Calculation	Cost
Cache egress	500 GB cache egress * $0.08 per GB	$40.00
Cache fill	25 GB fill * $0.01 per GB	$0.25
Cache lookup requests	5,000,000 operations (500 GB of 100 KB responses, on average) $0.0075 per 10,000 operations $0.0075 * 500	$3.75
Total		~$44.00

Cloud DNS

With Cloud DNS pricing, the charge is per zone per month (regardless of whether you use your zone), and you also pay for queries against your zones.

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

Note: There is no free tier for Cloud DNS.

Pricing table

The following pricing applies to all zone types: public, private, and forwarding. All zone types are aggregated for purposes of pricing. For example, if you have 10 public zones, 10 private zones, and 10 forwarding zones, then your pricing is based on having 30 zones. All queries are aggregated as well, regardless of zone type.

You can use labels to label zones in certain ways. You can then use these labels to see per-label breakdowns in your billing.

Metric	Price
Queries: 0-1 billion	$0.40 per million queries per month.
Queries: over 1 billion	$0.20 per million queries per month.
Managed Zones^*: 0-25	$0.20 per managed zone per month.
Managed Zones^*: 26-10,000	$0.10 per managed zone per month for each additional zone after 25.
Managed Zones^*: over 10,000	$0.03 per managed zone per month for each additional zone over 10,000.

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

^* Managed zone pricing is calculated based on the number of managed zones that exist at a time, prorated by the percentage of the month they exist. This prorating is measured by hour. Zones that exist for a fraction of an hour are counted as having existed for the whole hour.

Pricing example

The following table shows sample Cloud DNS usage patterns and the potential costs per month:

Usages	Standard website	Enterprise	Web virtual hosting provider
Zones	5	200	100,000
Zone cost	5 * $0.20 = $1.00	25 * $0.20 = $5.00 175 * $0.10 = $17.50	25 * $0.20 = $5.00 9,975 * $0.10 = $997.50 90,000 * $0.03 = $2,700.00
Monthly queries	10,000,000	50,000,000	100,000,000
Queries cost	10 * $0.40 = $4.00	50 * $0.40 = $20.00	100 * $0.40 = $40.00
Total cost	$5.00/month	$42.50/month	$3,742.50/month

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

Note: If you are a high volume user managing millions of DNS zones and/or record sets, contact us to tell us what you need.

Cloud Interconnect

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 interconnects and 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 interconnect attachments to access services located in a different region than the interconnect attachment. In this case, you are charged standard cross-region rates for traffic between the region where the interconnect attachment is located and the region where the service is located.

Cloud Interconnect egress charges accrue to the project that owns the interconnect attachment (VLAN). The project that owns the Cloud Interconnect connection is not billed for egress. Specifically, costs for egress traffic from an interconnect 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.

Pricing tables

Dedicated Interconnect pricing:

Resource	Price
Interconnect	$2.328 per hour per 10 Gbps circuit
Interconnect	$18.05 per hour per 100 Gbps circuit
A 50, 100, 200, 300, 400, or 500 Mbps interconnect attachment (VLAN)	$0.10 per hour per interconnect attachment
A 1, 2, 5, or 10 Gbps interconnect attachment (VLAN)	$0.10 per hour per interconnect attachment
A 20 Gbps interconnect attachment (VLAN)	$0.20 per hour per interconnect attachment
A 50 Gbps interconnect attachment (VLAN)	$0.50 per hour per interconnect 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, 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 a Cloud 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	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	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
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		$10,898.56

Partner Interconnect

Google charges you on an hourly basis for interconnect attachments (VLANs), 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 interconnect attachments to access services located in a different region than the interconnect attachment. In this case, you are charged standard cross-region rates for traffic between the region where the interconnect 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 interconnect attachment
100 Mbps	$0.0625 per hour per interconnect attachment
200 Mbps	$0.08333 per hour per interconnect attachment
300 Mbps	$0.1111 per hour per interconnect attachment
400 Mbps	$0.1389 per hour per interconnect attachment
500 Mbps	$0.1736 per hour per interconnect attachment
1 Gbps	$0.2778 per hour per interconnect attachment
2 Gbps	$0.5694 per hour per interconnect attachment
5 Gbps	$1.25 per hour per interconnect attachment
10 Gbps	$2.36 per hour per interconnect attachment
20 Gbps	$3.61 per hour per interconnect attachment
50 Gbps	$9.02 per hour per interconnect 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, 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 a Cloud 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
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:

• A VM in the same continent as an interconnect attachment, using regional VPC dynamic routing
• A VM in the same continent as an interconnect attachment, using global VPC dynamic routing
• A VM in a different continent than an interconnect attachment, using global VPC dynamic routing
• A VM in a different continent than an interconnect attachment, using VPC Network Peering
• A non-VM Google Cloud product or service in a different location than an interconnect attachment, using global VPC dynamic routing

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.

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

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 interconnect attachment goes to region us-east1, and the other interconnect 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

Note: Unless you enable global dynamic routing for your VPC network using Cloud Router, your regions without an interconnect attachment have no access to your Cloud Interconnect. This also means that you can't accidentally incur intercontinental egress charges if you have regions located on different continents.

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

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 a 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 interconnect 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

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 VM in a different continent than an interconnect 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)
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 the Cloud Interconnect in Asia 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 an interconnect 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.

Note: For information on egress charges for other Google Cloud products, not described in this example, check the pricing page for that product.

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.

Non-VM in two North American regions, global dynamic routing (click to enlarge)
Cloud Storage egress charges for traffic forwarded from for forwarding traffic 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 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.

Cloud Router

Cloud Router is provided free of charge. Note that 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 documentation.

Cloud VPN

Cloud VPN pricing is based on the location of the Cloud VPN gateway and the number of tunnels per hour.

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

Note: Only VPN tunnels in these tunnel states are billed.

Select the location of the VPN gateway in Google Cloud to view pricing.

Cloud NAT

Cloud NAT pricing is based on the following usage:

• An hourly price for the NAT gateway that is based on the number of VM instances that are using the gateway. The per-hour rate is capped at 32 VM instances. Gateways that are serving instances beyond the maximum number are charged at the maximum per-hour rate.

  Google Cloud counts VM instances that get a NAT assignment as using the gateway. For more information, see Cases where NAT is not performed on traffic.

• A per-GB cost for ingress and egress data that is processed by the gateway. The data processing price is the same across all regions. Egress costs to send traffic from the VM out of the network also apply.

Number of assigned VM instances	Price per hour	Price per GB processed, both egress and ingress
Up to 32 VM instances	$0.0014 * the number of VM instances that are using the gateway	$0.045
More than 32 VM instances	$0.044	$0.045

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

The total cost for running a NAT gateway and running traffic through it is as follows:

total cost for running the gateway = hourly cost for the NAT gateway
+ cost per GB of data that is processed by the gateway
+ egress costs for any traffic leaving the network

Pricing example

The following table shows the estimated monthly cost for a single NAT gateway that is serving a different number of VM instances. For both cases, the gateway runs for 720 hours in a billing cycle.

Usage	Estimated bill
14 VM instances Gateway processes 100 GB of traffic (egress and ingress)	($0.0014 * 14 instances * 720 hours) + (100 GB processed traffic * $0.045) = $18.61
36 VM instances Gateway processes 200 GB of traffic (egress and ingress)	($0.044 * 720 hours) + (200 GB processed traffic * $0.045) = $40.68

Logging pricing

NAT logging pricing is described in Network Telemetry pricing.

Standard pricing for Cloud Logging, BigQuery, or Pub/Sub apply.