Google has a generally open peering policy, subject to technical, commercial and legal constraints. We have technical and traffic level requirements for peers, please see below.

Peering Technical Requirements: 

- a public Autonomous System Number
- publicly routable address space (at least a  /24)
- address space and AS-Macro registered with the appropriate regional Internet registry
- ASN record completed in PeeringDB
- a 24x7 NOC contact capable of resolving BGP routing issues
- a presence at one or more of the IXes or colocation facilities listed for Google in PeeringDB
- sufficient traffic levels - see below.

Peering Traffic Requirements: Peers in North America or Western Europe with less than 100Mbps peak of Google traffic may peer via route servers at participating IXes. Peers with more than 100Mbps peak of Google traffic may peer via a bilateral BGP session over an IX. The traffic requirements are lower for peering outside of North America and Western Europe.

Peering Methods: Peering can be via Internet Exchanges, or for peers with high volumes of traffic, private interconnects.

Route Advertisement Policy: Where AS15169 interconnects with a peer network in a single location or within a single region/continent route advertisements may be limited to routes relevant to the respective region, and in some cases 'more specific' routes may be seen via a transit provider. If interconnected in two geographically dispersed regions AS15169 will announce all (global) Google routes, except the prefixes associated with our web indexing traffic. No 'more specific' routes will be heard via other routes with this type of peering, with the possible exception of web-indexing routes that are only announced to select providers. 

Maximum Prefix: We recommend max-prefix of 1000 (IPv4) and 100 (IPv6) on peering sessions with Google.

IPv6 Peering: We will peer IPv6 with any peer who qualifies for IPv4 peering.

Peering Requests: If you meet the above requirements and would like to peer, please e-mail peering@google.com.