Notes on additional Routes (incl. Google VPP) via GlobePEER Route Service

Johannes Moos Updated by Johannes Moos

Notes on additional Routes (incl. Google VPP) via GlobePEER Route Service

Strict peering policies of some networks may include the disfavor of route server peering and/or strict requirements for bilateral peering via GlobePEER or VirtualPNI. As many networks are not eligible to set up a peering in this case, DE-CIX also offers additional routes of selected partner networks via GlobePEER through the DE-CIX Layer 3 Services ASN (AS214292). DE-CIX will take care of managing all peering relationships with these partners (so you don't have to) and will make their routes available from AS214292 via the GlobePEER route service at many DE-CIX Exchanges.

Thus, you can maintain a peering relationship with these networks without directly interacting with them or having to fulfil their peering requirements. All this is handled by DE-CIX.

Available Networks

Currently we offer connectivity to Google resources (incl. GCP) as a member of Google's Verified Peering Provider Program.

You can check the DE-CIX Looking Glass for additional routes that are currently being made available.

Availability

Google Peering is available via GlobePEER in the following locations:

Europe

  • Frankfurt (FRA)
  • Madrid (MAD)

Americas

  • Chicago (ORD)
  • Phoenix (PHX)
  • New York City (NYC)

Asia

  • Singapore (SIN via ASEAN Peering LAN)
  • Johor Bahru (JHB via ASEAN Peering LAN)
  • Kuala Lumpur (KUL)
  • Brunei (BWN via ASEAN Peering LAN)

In all other locations Google Peering is available via GlobePEER Remote.

It is not posssible to peer with Google remotely (via GlobePEER Remote) from one of the above listed locations.

For more details on where Google Peering is available and to verify routing paths, please consult the Looking Glass.

The list of Route Servers in the dropdown menu on the right-hand side of the Looking Glass interface reflects the regional availability of Google Peering locations.

Please see also DE-CIX Layer 3 Services (AS214292) at PeeringDB for a list of DE-CIX locations/IXP where the service is currently available.

Requirements

Additional routes are only made available via the GlobePEER route service.
DE-CIX Layer 3 Services (AS214292) does not offer bilateral peering sessions!

Please have a look at our Route Server Guides on how to set up your route server peering for your GlobePEER service.

Technical Considerations

Announcing partner routes via DE-CIX Layer 3 Services (AS214292) will result in AS214292 in the AS path in comparison to a direct peering relationship with a given network.

Please make sure to prioritize your GlobePEER peering accordingly, e.g. with setting a higher BGP local preference for your GlobePEER service than for your transit provider(s)!

Opt-out

Partner routes are redistributed to you by default. On the other hand, all routes announced to the GlobePEER route service will also be redistributed to our partner networks, e.g. Google. This is necessary to prevent asymmetric traffic flow as much as possible. If you want to opt-out, please make sure to prevent traffic in both ingress and egress directions!

Your Ingress Traffic/Your BGP Announcements

Prevent your prefixes from being propagated to partner networks announced by DE-CIX Layer 3 Services (AS214292). You can control this behavior by setting the following BGP Action Community:

<RS_ASN>:0:214292

e.g.

6695:0:214292

for DE-CIX/GlobePEER Frankfurt.

Please see BGP Action Communities for a full list of Route Service control options.

Your Egress Traffic/Partner BGP Announcements

Prevent learning of partner prefixes from the GlobePEER route service (e.g. by rejecting AS path pattern ^214292 .*).

Support/Questions

Please contact our Customer Service Team for support requests that are related to connectivity issues with partner routes/networks and do not contact our partners directly. We'll troubleshoot your case and escalate to the corresponding partner NOC if necessary.

How did we do?

Get in touch