Which type of carrier connections that organization connects to only one service provider?

Google's connectivity solutions enable you to connect your networks to Google in the following ways:

Inhaltsverzeichnis Show

Try it for yourself
Connecting to Google Cloud
Cloud Interconnect
Cloud Router
Connecting your sites by using Google Cloud
Network Connectivity Center
Router appliance
Connecting to Google Workspace and Google APIs
Direct Peering
Carrier Peering
Connecting to CDN providers
CDN Interconnect
Setting up CDN Interconnect
Typical use cases for CDN Interconnect
What's next
What are the types of WAN connections?
What is a WAN carrier?
What type of WAN technology provides a dedicated connection from the service provider?
What is MAN connection?

To Google Cloud, which enables you to access your Virtual Private Cloud (VPC) networks and Compute Engine virtual machine (VM) instances from your on-premises networks or from another cloud provider.
To connect your sites together through a Network Connectivity Center hub located in Google Cloud.
To Google Workspace and supported Google APIs, which lets you access only these products and services.
To CDN providers, which enables you to choose supported content delivery providers that establish Direct Peering links with Google's edge network. Choosing a provider enables you to send traffic from your VPC networks to that provider.

Try it for yourself

If you're new to Google Cloud, create an account to evaluate how our products perform in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.

Get started for free

Connecting to Google Cloud

When connecting to Google Cloud, you can choose among the following Google Cloud networking products.

If you need to access only Google Workspace or supported Google APIs, see Connecting to Google Workspace and Google APIs.

Product

Description

Cloud VPN and
Cloud Interconnect

Provide network connectivity with Google Cloud between your on-premises network and Google Cloud, or from Google Cloud to another cloud provider.

If you need to encrypt traffic to Google Cloud, or you need a lower throughput solution, or you are experimenting with migrating your workloads to Google Cloud, you can choose Cloud VPN. For more information, see the Cloud VPN overview

If you need an enterprise-grade connection to Google Cloud that has higher throughput, you can choose Dedicated Interconnect or Partner Interconnect.

We recommend using Cloud Interconnect instead of Direct Peering and Carrier Peering, which you would only use in certain circumstances. For a quick summary, you can compare the features of Direct Peering with Cloud Interconnect and Carrier Peering with Cloud Interconnect.

Cloud Router

Provides dynamic routing by using the Border Gateway Protocol (BGP) over Interconnect connections and Cloud VPN gateways.

For pricing, quotas, service level agreement (SLA), and release note information for all Network Connectivity products, see the Network Connectivity resources page.

For high-level architectural guides and tutorials that describe networking scenarios for Google Cloud, see the Technical guides for networking.

Cloud VPN

Google Cloud offers two types of Cloud VPN gateways: HA VPN and Classic VPN.

For information about moving to HA VPN, see Moving to HA VPN from Classic VPN.

HA VPN

HA VPN is a high-availability (HA) Cloud VPN solution that lets you securely connect your on-premises network to your VPC network through an IPsec VPN connection in a single region. HA VPN provides an SLA of 99.99% service availability.

When you create an HA VPN gateway, Google Cloud automatically chooses two external IPv4 addresses, one for each of its fixed number of two interfaces. Each IPv4 address is automatically chosen from a unique address pool to support high availability. Each of the HA VPN gateway interfaces supports multiple tunnels. You can also create multiple HA VPN gateways. When you delete the HA VPN gateway, Google Cloud releases the IP addresses for reuse. You can configure an HA VPN gateway with only one active interface and one external IP address; however, this configuration does not provide a 99.99% service availability SLA.

HA VPN supports the exchange of IPv6 traffic in Preview.

In the API documentation and in gcloud commands, HA VPN gateways are referred to as VPN gateways rather than target VPN gateways. You don't need to create any forwarding rules for HA VPN gateways.

HA VPN uses an external VPN gateway resource in Google Cloud to provide information to Google Cloud about your peer VPN gateway or gateways.

For more information, see the following resources:

For requirements, see HA VPN requirements.
For Cloud VPN specifications, see Specifications.
For sample topologies, see Cloud VPN topologies.
For information about high-availability, high-throughput scenarios, or multiple subnet scenarios, see Advanced configurations.
For routing scenarios, see Active/active and active/passive routing options for HA VPN.
For more information about Classic VPN and HA VPN, see the Cloud VPN overview.

Cloud Interconnect

Network Connectivity provides two options for extending your on-premises network to your VPC networks in Google Cloud. You can create a dedicated connection (Dedicated Interconnect) or use a service provider (Partner Interconnect) to connect to VPC networks. When choosing one of the following connection types, consider your connection requirements, such as the connection location and capacity.

If you can't physically meet Google's network in a colocation facility to reach your VPC networks, you can use Partner Interconnect to connect to service providers that connect directly to Google:

If you have high bandwidth needs, Dedicated Interconnect can be a cost-effective solution.
If you require a lower bandwidth solution, Dedicated Interconnect and Partner Interconnect provide capacity options starting at 50 Mbps.
Cloud Interconnect provides access to all Google Cloud products and services from your on-premises network except Google Workspace.
Cloud Interconnect also allows access to supported APIs and services by using Private Google Access from on-premises hosts.

Compare Cloud Interconnect solutions

The following table highlights the key differences between Dedicated Interconnect and Partner Interconnect.

	Dedicated Interconnect	Partner Interconnect
Features	A direct connection to Google. Traffic flows directly between networks, not through the public internet. 10-Gbps or 100-Gbps circuits with flexible VLAN attachment capacities from 50 Mbps to 50 Gbps.	More points of connectivity through one of our supported service providers. Traffic flows between networks through a service provider, not through the public internet. Flexible capacities from 50 Mbps to 50 Gbps.
Service providers		Connect to supported service providers, who provide more points of connectivity compared to the colocation facilities available for Dedicated Interconnect. Work with a supported service provider. If your service provider isn't supported, or if you don't want to pass traffic through a service provider, consider Cloud VPN or Dedicated Interconnect. Compared to Dedicated Interconnect, you don't need to install and maintain routing equipment in a colocation facility.
Supported bandwidth	Scale your costs according to the number and capacity of VLAN attachments that you order, with capacities of 50 Mbps to 50 Gbps for each VLAN attachment. Scale to meet the most demanding data needs. Connection capacity is delivered over one or more 10-Gbps or 100-Gbps Ethernet circuits, with a maximum of 8 x 10-Gbps (80 Gbps) circuits, or 2 x 100-Gbps (200 Gbps) circuits for each Dedicated Interconnect connection. If your traffic doesn't require a 10-Gbps or 100-Gbps circuit, consider Cloud VPN or Partner Interconnect.	Scale your costs according to the number and capacity of VLAN attachments that you order, with capacities of 50 Mbps to 50 Gbps for each VLAN attachment. Increases in the number of VLAN attachments or increasing the capacity of an existing VLAN attachment depends on your service provider's available capacity.
Setup	Requires routing equipment in a colocation facility that supports the regions that you want to connect to.	Use any supported service provider to connect to Google.
BGP configuration	Configure BGP on your on-premises routers and Cloud Routers.	For layer 2 connections, configure BGP on your on-premises routers and Cloud Routers. For layer 3 connections, the configuration of your Cloud Routers and their peers is fully automated.
Encryption	The connection between your network and Google's network is not encrypted. If you require additional data security, use application-level encryption or your own VPN. Currently, you can't use Cloud VPN with Dedicated Interconnect, but you can use your own VPN solution.	The connection between your network and Google's network is not encrypted. If you require additional data security, use application-level encryption or your own VPN. Currently, you can't use Cloud VPN with Partner Interconnect, but you can use your own VPN solution.
SLA	Google offers an end-to-end SLA for the connectivity between your VPC network and on-premises network for Google-defined topologies.	Google provides an SLA for the connection between Google and the service provider. Your service provider might provide an end-to-end SLA, based on the Google-defined topologies. For more information, contact your service provider.
Pricing	For details, see Dedicated Interconnect pricing.	Google bills you based on your VLAN attachment's capacity and egress traffic. Charges also apply to egress traffic from your VPC network to your on-premises network. In addition, your service provider might charge you to carry data across their network. For details, see Partner Interconnect pricing.

For more information, see the following resources:

Cloud Interconnect overview
Dedicated Interconnect overview
Partner Interconnect overview
Tutorials: sample topologies

Cloud Router

Cloud Router is a fully distributed and managed Google Cloud service that uses the Border Gateway Protocol (BGP) to advertise IP address ranges. It programs custom dynamic routes based on the BGP advertisements that it receives from a peer. Instead of a physical device or appliance, each Cloud Router consists of software tasks that act as BGP speakers and responders. A Cloud Router also serves as the control plane for Cloud NAT. Cloud Router provides BGP services for the following Google Cloud products:

Dedicated Interconnect
Partner Interconnect
Cloud VPN, specifically HA VPN
Router appliance (part of Network Connectivity Center)

Each Cloud Router works with at least one of the networking connectivity products listed previously.

When you connect an on-premises or multicloud network to Google Cloud, Cloud Router uses BGP to dynamically exchange routes between your Google Cloud VPC network and the remote network. Prefix and next hop changes automatically propagate between your VPC network and the other network without the need for static routes.

You can also use Cloud Router to connect two VPC networks in Google Cloud. In this scenario, you connect the VPC networks by using two HA VPN and two Cloud Routers, one HA VPN and its associated Cloud Router on each network.

Direct Peering and Carrier Peering do not use Cloud Routers.

For more information, see the Cloud Router overview.

Connecting your sites by using Google Cloud

Use Google Cloud to connect your sites to each other through a Network Connectivity Center hub.

Network Connectivity Center

Network Connectivity Center supports connecting different enterprise sites outside of Google Cloud by using Google's network as a wide area network (WAN). On-premises networks can consist of on-premises data centers and branch or remote offices.

Network Connectivity Center is a hub-and-spoke model for network connectivity management in Google Cloud. The hub resource reduces operational complexity through a simple, centralized connectivity management model. The hub is paired with Google's network to deliver reliable connectivity on demand.

For definitions of hub and spoke, see Hubs and spokes.

On-premises networks connect to a Network Connectivity Center hub by using spokes that have supported Google Cloud resources attached to them.

The following diagram shows a Network Connectivity Center hub and its spokes. For example, a spoke can contain a VLAN attachment to an on-premises branch office in region us-east1. Another spoke can contain an attachment that connects to a Google Cloud region near another branch office in Europe. After the two branch offices are configured, they can send traffic over the hub to each other. Traffic between the offices enters and exits Google's network close to each office. This traffic spends little or no time on the public internet.

For a list of supported Google Cloud resources that you can attach to spokes, see Spoke resource types.
For general information about Network Connectivity Center, see the Network Connectivity Center overview.

Network Connectivity Center concept (click to enlarge)

Router appliance

Router appliance is an alternative way of enabling connectivity between sites outside of Google Cloud through a Network Connectivity Center hub. You peer your Router appliance with Cloud Router to provide this connectivity.

You can install an image from your vendor of choice onto one or more VMs that act as router appliance instances, or you can choose a supported vendor from Google Cloud Marketplace.

You associate your router appliance instance with a Network Connectivity Center Router appliance spoke, which you attach to a Network Connectivity Center hub.

Cloud Router uses interfaces configured with private IP addresses to establish BGP peering with router appliance instances. In that way, you establish routes among all locations.

For more information, see the Router appliance overview.

Connecting to Google Workspace and Google APIs

If you need access to only Google Workspace or supported Google APIs, you have the following options:

You can use Direct Peering to directly connect (peer) with Google Cloud at a Google edge location.
You can use Carrier Peering to peer with Google by connecting through a support provider, which in turn peers with Google.

Direct Peering

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.

Compare Direct Peering and Cloud Interconnect

The following table describes the differences between 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.
Gives you direct access from your on-premises network to Google Workspace and Google APIs for the full suite of Google Cloud products.	Does not give you access to Google Workspace, but gives you access to all other Google Cloud products and services from your on-premises network. Also allows access to supported APIs and services by using Private Google Access from on-premises hosts.
Has no setup or maintenance costs.	Has maintenance costs; see pricing.
Has reduced internet egress rates to your on-premises network from Google Cloud resources in the same continental location and in an enabled project; see pricing.	Has standard egress rates for traffic sent through an Interconnect connection; see pricing.
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 do not 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 custom dynamic routes in your VPC network.

For more information, see the Direct Peering overview.

Carrier Peering

Carrier Peering enables you to access Google applications, such as Google Workspace, by using a service provider 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

The following example describes a common use case for 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. To choose a product, see the Considerations section and the table that compares Carrier Peering with Cloud Interconnect.

Considerations

Review the following considerations to decide if Carrier Peering meets your needs:

Carrier Peering exists outside of Google Cloud. Instead of Carrier Peering, the recommended methods of access to Google Cloud are Partner Interconnect, which uses a service provider, or Dedicated Interconnect, which provides a direct connection to Google.
If used with Google Cloud, Carrier 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.
To send traffic through Carrier 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.

Compare Carrier Peering and Cloud Interconnect

The following table describes the differences between 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 Private Google Access from on-premises hosts.
Has service provider costs.	Has maintenance costs; see pricing.
Has reduced internet egress rates to your on-premises network from Google Cloud resources in the same continental location and in an enabled project; see pricing.	Has standard egress rates for traffic sent through an Interconnect connection; see pricing.
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 do not 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 custom dynamic routes in your VPC network.

For more information, see the Carrier Peering overview.

Connecting to CDN providers

CDN Interconnect

CDN Interconnect enables select third-party Content Delivery Network (CDN) providers to establish direct peering links with Google's edge network at various locations, which enables you to direct your traffic from your Virtual Private Cloud (VPC) networks to a provider's network.

CDN Interconnect enables you to optimize your CDN population costs and use direct connectivity to select CDN providers from Google Cloud.

Your network traffic egressing from Google Cloud through one of these links benefits from the direct connectivity to supported CDN providers and is billed automatically with reduced pricing.

Setting up CDN Interconnect

If your CDN provider is already part of the program, you don't have to do anything. Traffic from supported Google Cloud locations to your CDN provider automatically takes advantage of the direct connection and reduced pricing.

Work with your supported CDN provider to learn what locations are supported and how to correctly configure your deployment to use intra-region egress routes. CDN Interconnect does not require any configuration or integration with Cloud Load Balancing.

If your CDN provider is not part of the program, contact your CDN provider and ask them to work with Google to get connected.

Typical use cases for CDN Interconnect

High-volume egress traffic. If you're populating your CDN with large data files from Google Cloud, you can use the CDN Interconnect links between Google Cloud and selected providers to automatically optimize this traffic and save money.
Frequent content updates. Cloud workloads that frequently update data stored in CDN locations benefit from using CDN Interconnect because the direct link to the CDN provider reduces latency for these CDN destinations.
For example, if you have frequently updated data served by the CDN originally hosted on Google Cloud, you might consider using CDN Interconnect.

For information about pricing and service providers, see the CDN Interconnect overview.

What's next

Network Connectivity key terms

What are the types of WAN connections?

Types of WAN technologies.

TCP/IP protocol suite. TCP/IP is a protocol suite of foundational communication protocols used to interconnect network devices on today's Internet and other computer/device networks. ... .

Router. ... .

Overlay network. ... .

Packet over SONET/SDH (PoS) ... .

Multiprotocol Label Switching (MPLS) ... .

ATM. ... .

Frame Relay..

What is a WAN carrier?

A wide area network (WAN) is a communication network that connects geographical dispersed locations across cities, countries or even continents. In one of its common implementations, a wide area network connects an organization's local area networks (LANs) to one another.

What type of WAN technology provides a dedicated connection from the service provider?

Private WAN infrastructure: Service providers may offer dedicated point-to-point leased lines, circuit-switched links, such as PSTN or ISDN, and packet-switched links, such as Ethernet WAN, ATM, or Frame Relay.

What is MAN connection?

A metropolitan area network (MAN) is a computer network that connects computers within a metropolitan area, which could be a single large city, multiple cities and towns, or any given large area with multiple buildings. A MAN is larger than a local area network (LAN) but smaller than a wide area network (WAN).