Network pricing

This page describes the network costs of running a VM on Compute Engine. To learn more about networking on Google Cloud, see the networking documentation.

General network pricing

Traffic type Price (USD)
Ingress No charge, unless there is a resource that is processing ingress traffic,such as a load balancer. Responses to requests count as egress and are charged.
Egress* to the same zone No charge
Egress to Google products (such as YouTube, Maps, Drive), whether from a VM in Google Cloud with an external IP address or an internal IP address No charge
Egress to Double-click in the same region 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, and Cloud SQL No charge
Egress between zones in the same region (per GB) $0.01
Egress to Memorystore for Redis is charged at the rate of "Egress between zones in the same region"
Egress to Filestore is charged at the rate of "Egress between zones in the same region"
Egress to Cloud SQL is charged at the rates described in Traffic through external IP addresses
Egress between regions within the US and Canada (per GB) $0.01
Egress between regions within Europe (per GB) $0.02
Egress between regions within Asia (per GB) $0.05
Egress between regions within South America (per GB) $0.08
Intercontinental egress (excludes Oceania) (per GB) $0.08
Oceania to or from any 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.

*These charges are for egress through internal IP addresses. There are different charges for egress through external IP addresses, regardless of whether the instances are in the same zone. 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.

Internet egress rates*

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs 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.

Traffic through external IP addresses

When you send traffic between virtual machines through the external IP addresses, it is charged as follows:

  • Traffic sent between the external IP addresses of two virtual machines in the same region is charged as Egress between zones in the same region, even if the virtual machines are in the same zone.
  • Traffic sent between the external IP addresses of two virtual machines in different regions within the US are charged as Egress between regions within the US.
  • Traffic sent between the external IP addresses of two virtual machines in different regions, not including traffic between US regions, is charged at Internet Egress pricing.

It is not possible to charge traffic through the external IP address of two virtual machine instances in the same zone as Egress to the same zone because Compute Engine cannot determine the zone of a virtual machine through the external IP address.

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.

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.

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.

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 Compute Engine tab, search for Load Balancing.
  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

To ensure optimal performance and reliability, each load balancer is allocated at least one proxy per zone in the load balancer's GCP region. For example, the us-west1 region has three zones: us-west1-a, us-west1-b, and us-west1-c. The minimum hourly charge due to proxies in us-west1 is calculated as follows:

1 proxy instance/zone * 3 zones * $0.025/hour = $0.075/hour

Internal HTTP(S) Load Balancing allocates additional proxies as needed to handle traffic. These proxies incur an additional hourly charge according to the table above.

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.

VPN

See Cloud VPN Pricing for VPN pricing information.