Network pricing

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

Compute Engine charges for usage based on the following price sheet. A bill is sent out at the end of each billing cycle, listing previous usage and charges. Prices on this page are listed in U.S. dollars (USD).

For Compute Engine, disk size, machine type memory, and network usage are calculated in gigabytes (GB), where 1 GB is 230 bytes. This unit of measurement is also known as a gibibyte (GiB).

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

You can also find pricing information with the following options:

General network pricing

Traffic type Price
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 GCP 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 Platform service within the same region using an external IP address or an internal IP address, except for Cloud Memorystore for Redis, Cloud Filestore, and Cloud SQL No charge
Egress between zones in the same region (per GB) $0.01
Egress to Cloud Memorystore for Redis is charged at the rate of "Egress between zones in the same region"
Egress to Cloud 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*

Iowa (us-central1) Los Angeles (us-west2) Oregon (us-west1) Northern Virginia (us-east4) South Carolina (us-east1) Montréal (northamerica-northeast1) São Paulo (southamerica-east1) Belgium (europe-west1) Finland (europe-north1) Frankfurt (europe-west3) London (europe-west2) Netherlands (europe-west4) Zürich (europe-west6) Mumbai (asia-south1) Singapore (asia-southeast1) Sydney (australia-southeast1) Hong Kong (asia-east2) Taiwan (asia-east1) Tokyo (asia-northeast1) Osaka (asia-northeast2)
Monthly Usage Network (Egress)
Worldwide Destinations
(excluding China & Australia,
but including Hong Kong)
(per GB)
Network (Egress)
China Destinations
(excluding Hong Kong)
(per GB)
Network (Egress)
Australia Destinations
(per GB)
Network (Ingress)
0-1 TB $0.23 $0.19 Free
1-10 TB $0.22 $0.18 Free
10+ TB $0.20 $0.15 Free

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

Load balancing and forwarding rules

The following pricing applies to all types of load balancing and forwarding rules (protocol forwarding).

Iowa (us-central1) Los Angeles (us-west2) Oregon (us-west1) Northern Virginia (us-east4) South Carolina (us-east1) Montréal (northamerica-northeast1) São Paulo (southamerica-east1) Belgium (europe-west1) Finland (europe-north1) Frankfurt (europe-west3) London (europe-west2) Netherlands (europe-west4) Zürich (europe-west6) Mumbai (asia-south1) Singapore (asia-southeast1) Sydney (australia-southeast1) Hong Kong (asia-east2) Taiwan (asia-east1) Tokyo (asia-northeast1) Osaka (asia-northeast2)
Item Price per unit (USD) Pricing unit
First 5 forwarding rules Per Hour
Per additional forwarding rule Per Hour
Ingress data processed by load balancer Per GB
If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

Load balancing ingress and egress charges

  • The load balancing and forwarding table earlier in this topic contains the charges for ingress data processed by load balancers.
  • 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 charges

Compute Engine charges for forwarding rules whether they are created for load balancing or other uses.

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

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

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.

These charges become effective after the user-defined request headers feature becomes available in General Availability (GA).

Network Telemetry

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

  • VPC flow logs
  • Firewall rule logs
  • Cloud NAT logging (starting at NAT logging GA. No charge for logs generation during beta.)
Log generation Price
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 can be exported to Stackdriver Logging, Cloud Pub/Sub, Cloud Storage, or BigQuery. Cloud Pub/Sub, Cloud Storage, or BigQuery charges apply in addition to log generation charges.

If you send your logs to Stackdriver Logging, logs generation charges are waived, and only Logging charges apply.

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

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

If you reserve a static external IP address but do not use it, you are charged for the IP address according to the following table. If you reserve a static external IP address and use it with a Compute Engine resource, such as a VM instance or a forwarding rule, the address is considered in use and you aren't charged for it.

Iowa (us-central1) Los Angeles (us-west2) Oregon (us-west1) Northern Virginia (us-east4) South Carolina (us-east1) Montréal (northamerica-northeast1) São Paulo (southamerica-east1) Belgium (europe-west1) Finland (europe-north1) Frankfurt (europe-west3) London (europe-west2) Netherlands (europe-west4) Zürich (europe-west6) Mumbai (asia-south1) Singapore (asia-southeast1) Sydney (australia-southeast1) Hong Kong (asia-east2) Taiwan (asia-east1) Tokyo (asia-northeast1) Osaka (asia-northeast2)
Type Price/Hour
Static IP address (assigned but unused)
Static and ephemeral IP addresses in use on standard VM instances

*Starting January 1st, 2020, you will be charged $0.004 per hour.
No charge*
Static and ephemeral IP addresses in use on preemptible VM instances

*Starting January 1st, 2020, you will be charged $0.002 per hour.
No charge*
Static and ephemeral IP addresses attached to forwarding rules No charge
If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

In use or not

GCP 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, GCP considers the static IP address as not in use.

For an ephemeral IP address, GCP considers the address as in use only when the associated VM instance is running. When the instance is stopped or deleted, GCP 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 and isn't charged while IPv4 address-2 is reserved but not being used. address-2 is charged according to the unused IPv4 address pricing.

VPN

See the Cloud VPN Pricing for VPN pricing information.

¿Te ha resultado útil esta página? Enviar comentarios:

Enviar comentarios sobre...

Compute Engine Documentation