Skip to content
Peering
Direct Peering
Direct Peering enables you to establish a direct 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 .
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.
Direct Peering exists outside of Google Cloud. Unless you need to access Google Workspace applications, the recommended methods of access to Google Cloud are or .
Compare Direct Peering and Cloud Interconnect
Direct Peering
Cloud Interconnect
Can be used by Google Cloud—for example, to access VMs through Cloud VPN—but does not require it.
Requires Google Cloud.
Provides direct access from your on-premises network to Google Workspace and Google APIs for the full suite of Google Cloud products.
Does not provide access to Google Workspace, but provides access to all other Google Cloud products and services from your on-premises network. Also allows access to supported APIs and services by using .
Does not provide direct access to VPC network resources that have only internal IP addresses.
Provides direct access to VPC network resources that have only internal IP addresses.
Connects to Google's edge network.
Connects to Google's edge network.
Does not use any Google Cloud resources; configuration is opaque to Google Cloud projects.
Uses Google Cloud resources, such as Interconnect connections, VLAN attachments, and Cloud Routers.
To change the destination IP address ranges for your on-premises network, contact Google.
To change the destination IP address ranges for your on-premises network, adjust the routes that your routers share with Cloud Routers in your project.
Routes to your on-premises network don't appear in any VPC network of your Google Cloud project.
Routes to your on-premises network are learned by Cloud Routers in your project and applied as in your VPC network.
Google does not offer a service level agreement (SLA) with Direct Peering.
Google offers an end-to-end SLA for the connectivity between your VPC network and on-premises network for .
There are no rows in this table
Carrier Peering
Carrier Peering enables you to access Google applications, such as Google Workspace, by using a to obtain enterprise-grade network services that connect your infrastructure to Google.
When connecting to Google through a service provider, you can get connections with higher availability and lower latency, using one or more links. Work with your service provider to get the connection that you need.
When to use Carrier Peering?
To access Google Workspace applications from an on-premises network, an organization might need a perimeter network to reach Google's network. The perimeter network enables organizations to expose an isolated subnetwork to the public internet instead of their entire network. Instead of setting up and maintaining a perimeter network, the organization can work with a service provider so that their traffic travels on a dedicated link from their systems to Google. With the dedicated link, the organization gets a higher availability and lower latency connection to Google's network.
Unless you need to access Google Workspace applications as described in the preceding use case, Partner Interconnect is the recommended way to connect to Google through a service provider.
Compare Carrier Peering and Cloud Interconnect
Carrier Peering
Cloud Interconnect
Can be used by Google Cloud, but does not require it.
Requires Google Cloud.
Gives you direct access from your on-premises network through a service provider's network to Google Workspace and to Google Cloud products that can be exposed through one or more public IP addresses.
Does not give you access to Google Workspace, but gives you access to all other Google Cloud products from your on-premises network. Also allows access to supported APIs and products by using .
Connects to Google's edge network through a service provider.
Connects to Google's edge network.
Does not use any Google Cloud resources; configuration is opaque to Google Cloud projects.
Uses Google Cloud resources, such as Interconnect connections, VLAN attachments, and Cloud Routers.
To change the destination IP address ranges for your on-premises network, contact Google.
To change the destination IP address ranges for your on-premises network, adjust the routes that your routers share with Cloud Routers in your project.
Routes to your on-premises network don't appear in any VPC network of your Google Cloud project.
Routes to your on-premises network are learned by Cloud Routers in your project and applied as in your VPC network.
Google does not offer a service level agreement (SLA) with Carrier Peering. If you are interested in an SLA, we recommend consulting with your network service provider to determine whether that provider might offer an SLA.
Google offers an end-to-end SLA for the connectivity between your VPC network and on-premises network for .
There are no rows in this table
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.