Direct Peering allows you to establish a direct peering connection between your business network and Google's edge network and exchange high-throughput cloud traffic. This capability is available at any of more than 100 locations in 33 countries around the world. Visit Google's peering site to find out more information about Google's edge locations.
However, Direct Peering exists outside of Google Cloud Platform. The recommended methods of access to GCP are Cloud Interconnect – Dedicated or Cloud Interconnect – Partner.
See the next section to determine which of these solutions is right for you.
How to choose
The following table describes the differences between Direct Peering and Cloud Interconnect.
|Direct Peering||Cloud Interconnect|
|Can be used by GCP, but does not require it||Requires GCP|
|Gives you direct access to G Suite and Google services, including the full suite of Google Cloud Platform products, from your on-premises network.||Does not give you access to G Suite, but gives you access to all other Google Cloud Platform products and services from your on-premises network. Also allows access to supported APIs and services using Private Google Access from on-premises hosts.|
|No setup or maintenance costs||Has maintenance costs (pricing)|
|Reduced Internet egress rates to your on-premises network from GCP resources in the same continental location and in an enabled project (details)||Standard egress rates for traffic sent through an interconnect apply (pricing)|
|Connects to Google's edge network||Connects to Google's edge network|
|Does not use any GCP objects; configuration is opaque to GCP projects||Uses GCP objects, such as interconnects, interconnect attachments (VLANs), and Cloud Routers|
|You need to contact Google if you need to change the destination IP address ranges to your on-premises network.||You can easily change the destination IP address ranges for your on-premises network by adjusting the routes that your routers share with Cloud Routers in your project.|
|Routes to your on-premises network do not appear in any VPC network of your GCP project.||Routes to your on-premises network are learned by Cloud Routers in your project and applied as custom dynamic routes in your VPC network.|
How it works
Direct peering with Google exchanges BGP routes between Google and your on-premises network. When established, direct peering provides a direct path to Google services, including the full suite of Google Cloud Platform products, from your on-premises network.
Cloud Interconnect requires GCP, and it connects an on-premises network to a given Virtual Private Cloud network. As part of the VPC network configuration, the routes in the VPC network clearly show what destinations are sent over the interconnect. The next hop is the BGP peer for the BGP session on Cloud Router that manages routes for the interconnect attachment (VLAN). You can easily change those destinations yourself by advertising routes from your on-premises router.
In contrast, Direct Peering, if used with GCP, doesn't produce any custom routes in a VPC network. Traffic sent from resources in a VPC network leaves by way of a route whose next hop is either a default Internet gateway (a default route, for example) or a Cloud VPN tunnel. If the destination for the traffic matches your on-premises IP ranges, it could be eligible for discounted egress rates, as described below.
To send traffic through Direct Peering using a route whose next hop is a Cloud VPN tunnel, the IP address of your on-premises network's VPN gateway must be in your configured destination range.
Who can peer with Google?
Any Google Cloud Platform customers that meet Google’s technical peering requirements specified in our peering page can be considered for the direct peering service. Google can peer at the Internet Exchanges (IXPs) and private facilities that are listed in our PeeringDB entry.
To request that a new peering connection is established, register your interest with our peering team. If you meet the posted technical requirements a Google representative will reach out to you with further details to guide you though the application process.
Establishing a direct peering connection with Google is free. There are no costs per port or fractional port, and no per hour charges.
Your GCP projects are eligible for discounted egress data rates for traffic sent to your peered network. You must contact your GCP sales team to request that your projects be enabled to receive the discounted direct peering egress rates to your peered network's IP ranges.
Discounted egress rates through a direct peering connection are available under these conditions:
- The continental location of the source GCP resource sending traffic must be the same as the continental location of your peered network, and
- The destination for egress traffic must fall into your peered network's IP ranges, and
- Your project must be enabled for direct peering egress pricing for your peered network's IP ranges.
For example, suppose your on-premises network uses the range
and is located in North America. From an enabled project, egress traffic sent
from any VM in any zone in North America to
203.0.113.0/24 would be billed at
the direct peering egress rate listed in the table below.
|Continental location||Direct peering egress rate|
All other traffic, including egress traffic to destinations other than your on-premises network, is billed at standard Google Cloud Platform rates.