Direct Peering enables 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. For more information about Google's edge locations, see Google's peering site.
When established, Direct Peering provides a direct path from your on-premises network to Google services, including Google Cloud products that can be exposed through one or more public IP addresses. Traffic from Google's network to your on-premises network also takes that direct path, including traffic from VPC networks in your projects. Google Cloud customers must request that direct egress pricing be enabled for each of their projects after they have established Direct Peering with Google. For more information, see Pricing.
Direct Peering exists outside of Google Cloud. Unless you need to access Google Workspace applications, the recommended methods of access to Google Cloud are Dedicated Interconnect or Partner Interconnect.
For a description of the differences between Direct Peering and Cloud Interconnect, see the comparison table.
If used with Google Cloud, Direct Peering 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 in Getting started.
To send traffic through Direct Peering by 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 customers that meet Google's technical peering requirements can be considered for Direct Peering. Google can peer at the internet exchanges (IXPs) and private facilities that are listed in our PeeringDB entry.
When privately peering, Google requires physical redundancy with at least two separate connections to Google in a single metropolitan area. Each physical connection must have its own IP addressing.
For more information about requirements, and to review Google's peering best practices for Google Cloud customers, visit Google peering.
To request that a new peering connection be established, register your interest with our peering team. If you meet the posted technical requirements, a Google representative will contact you with further details to guide you through 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 Google Cloud projects are eligible for discounted egress data rates for traffic sent to your peered network. To request that your projects be enabled to receive the discounted direct peering egress rates to your peered network's IP ranges, contact your Google Cloud sales team.
Discounted egress rates through a direct peering connection are available under the following conditions:
- The continental location of the source Google Cloud resource sending traffic must be the same as the continental location of your peered network.
- The destination for egress traffic must fall into your peered network's IP ranges.
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 is billed at
the direct peering egress rate listed in the following table.
|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 rates.