Peering Policy

Google is listed in PeeringDB, the industry database for peering information for network operators. Please review our PeeringDB entry entry for an up-to-date list of Google's public and private peering locations, along with contact information if you are interested in peering with Google.

Google has a generally open peering policy, subject to certain technical, commercial and legal requirements. Technical requirements for peering are:

Peering Traffic Requirements (IPv4)

IPv6 Peering

We welcome settlement-free IPv6 peering with any network that also has IPv4 peering with Google.

Routing Policy

In general, peering sessions with AS15169 will advertise all AS-GOOGLE routes. AS15169 interconnects in Africa and Asia may be limited to routes relevant to the respective region, and in some cases 'more specific' routes may be seen via a transit provider. Web-indexing routes may only be seen over specific providers.

Traffic Management

Google generally carries traffic on our own network as close to users as possible. In general, Google recommends that peers advertise all their prefixes over all peering sessions with Google, unless other route advertisement policies have been agreed upon.

Maximum Prefix

We suggest peers set a max-prefix of 15000 (IPv4) and 1000 (IPv6) routes on peering sessions with Google.

Related ASNs

Google also manages the following ASNs: AS36040, AS43515, AS36561

Google Global Cache

Google also offers our content delivery platform, Google Global Cache to ISPs with qualifying levels of traffic.