Google Cloud Platform: Direct Peering

Direct Peering allows Google Cloud Platform (GCP) customers to connect to Google via carrier-grade connections that can reduce latency and increase availability versus best-effort internet connections.

When connecting to GCP Direct Peering with Megaport, the Virtual Cross Connect  (VXC) forms a Layer 2 VXC between the customer’s Megaport and Mega-IX or AMS-IX.

Direct Peering with Google is achieved by exchanging BGP routes between Google and the customer network. Once Direct Peering is in place, customers can reach all of Google’s services including the full suite of GCP products.

Features and Benefits:

  • Reduced latency, increase availability
  • Reduce data egress cost: See Direct Peering pricing
  • Secure connectivity
  • Access to all Google Cloud services and Google Apps for Business across one connection

Direct Peering Requirements:

  • Publicly routable ASN
  • Publicly routable address space (at least one /24 of IPv4 and/or one /48 of IPv6 space)

NOTE: Not all customers will meet Google’s Direct Peering requirements. The user is not required to have 24/7 NOC but must meet remaining requirements outlined by Google.

Megaport – Google IX Peering Locations:

  • MegaIX: Ashburn, Dallas, Los Angeles, Seattle, Singapore, Sofia, Sydney
  • AMS-IX: Chicago, New York, Bay Area

See PeeringDB for additional details.

Deployment Steps:

  1. Create Google Direct Peering Virtual Cross Connect (VXC). Provision a VXC in the Megaport Portal to your chosen MegaIX or AMS-IX Peering location.

To create a MegaIX VXC in the Portal, click +Connection on the Megaport to which you want to attach your VXC. An example below reflects Google as the customer named, Megaport selected.

Next, select Internet Exchange tile.

Next, select the MegaIX location where peer will be set up with Google. Then, click Next.

You will then be presented with the options screen for configuring your VXC:

  1. Name Your Connection. This is a free text field allowing you to assign a logical name to your Megaport.
  2. Note or leave blank an Invoice Reference internal to your records, optional.
  3. Choose a Rate Limit speed in 1Mbps increments up to the Megaport rate size.

Select Next, you will fill out the following details below:

  1. Preferred VLAN: The VLAN for this connection that you will receive via the Megaport. This must be a unique VLAN ID on this Port. You can also select the toggle to “untag” this VXC. This will remove the VLAN tagging for this connection but will also mean only one VXC can be deployed on this Port.
  2. ASN: You must own a registered Publicly routable ASN.
  3. MAC Address: MAC address of your device used to peer.
  4. Graph Visibility: You can select Public or Private visibility. If Public is selected, the usage graph will be visible on the MegaIX.  If Private is selected, the usage graph will not be visible.

Once you have completed the sections, you are ready to click Next and add the VXC.  You then can proceed through the checkout process.

To complete the Google Direct Peering process, you will need to register with Google.  Click here to be directed to the Google registration.

©2018 Megaport. Megaport, Virtual Cross Connect, VXC and MegaIX are registered trademarks of Megaport (Services) Pty Ltd ACN 607 432 646.

Log in with your credentials

Forgot your details?