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:
- a publicly routable ASN
- publicly routable address space (at least one /24)
- ASN record completed in PeeringDB
- 24x7 NOC contact capable of resolving BGP routing issues.
- Presence at one or more of the 70+ Internet Exchanges, or 60+ private peering interconnection facilities listed for Google in PeeringDB
- Minimum traffic requirements as below
Peering Traffic Requirements (IPv4)
- Peers in Europe and North America
- Less than 100Mbps peak Google traffic can peer via the route servers at any participating Internet Exchange
- More than 100Mbps peak Google traffic can peer via a bilateral BGP session over an Internet Exchange
- Peers in Asia and Oceania
- Less than 25Mbps peak Google traffic can peer via the route servers at any participating Internet Exchange
- More than 25Mbps peak Google traffic can peer via a bilateral BGP session over an Internet Exchange
- There are no minimum traffic requirements for peers present at Internet Exchanges in Africa, and Central/South America.
- Private peering is welcome subject to sufficient traffic volume
We welcome settlement-free IPv6 peering with any network that also has IPv4 peering with Google.
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.
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.
We suggest peers set a max-prefix of 1000 (IPv4) and 100 (IPv6) routes on peering sessions with Google.
Google Global Cache
Google also offers our content delivery platform, Google Global Cache to ISPs with qualifying levels of traffic.