1. Overview
   1. Carrier Peering
      1. Enables access to Google applications such as Google Workplace via a service provider's enterprise-grade network services
      2. When connecting to Google through a service provider, users benefit from higher availability and lower latency, using one or more links
      3. Where these is no need to access Google Workspace applications, use Partner Interconnect to connect to Google's network via a service provider
   2. Direct Peering
      1. Enables a direct peering connection between an on-premise network and Google's edge network
      2. Available at more than 100 locations in more than 33 countries around the world
      3. Provides a direct path from on-premises network to Google services, including the full suite of Google Cloud products
      4. Traffic from Google's network to on-premises network takes a direct path, including traffic from VPC networks in projects
   3. Getting started
      1. Any Google Cloud Platform customers that meet Google’s technical peering requirements can be considered for the direct peering service
      2. Google can peer at the Internet Exchanges (IXPs) and private facilities that are listed in the PeeringDB entry
      3. To request that a new peering connection is established, register interest with the Google peering team
2. Use Cases
   1. An organization might need a perimeter network to reach Google's network
   2. The DMZ enables organizations to expose an isolated subnetwork to the public Internet instead of their entire network
   3. Organization can use a service provider's network as a DMZ to transmit traffic via a dedicated link to Google
   4. A dedicated link delivers a higher availability and lower latency connection to Google's network
3. Considerations
   1. Carrier and Direct Peering exists outside of Google Cloud, and does not create any custom routes in a VPC network
   2. Traffic sent from resources in a VPC network leaves by way of a route whose next hop is either a default Internet gateway or Cloud VPN tunnel
   3. To send traffic using a route whose next hop is a Cloud VPN tunnel, the IP address of the on-premises VPN gateway must be in the destination range
   4. If the destination for Direct Peering traffic matches on-premises IP ranges, it could be eligible for discounted egress rates
4. Pricing
   1. Carrier Peering
      1. Google Cloud egress traffic through Carrier Peering connections is billed to the originating Google Cloud project
      2. All other traffic, including ingress traffic through the connection, is billed at standard Google Cloud Platform rates
      3. Google Cloud Platform traffic sent to an in-region connection is charged in a similar manner to the Direct Peering pricing structure
   2. Direct Peering
      1. Establishing a direct peering connection with Google is free
      2. GCP projects are eligible for discounted egress data rates for traffic sent to peered network
      3. All other traffic, including egress traffic to destinations other than on-premises network, is billed at standard Google Cloud Platform rates