Liberal peering policy subject to certain technical, commercial and legal requirements:
- Maintain 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
- Fault management escalation list
- Presence at one or more of the IXes or accessible colocation facilities 

Peering Traffic Requirements (IPv4):
+ 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. 
+ Open peering policy in Eastern Europe, Africa & Central/South America
IPv6 Peering: 
We agree to settlement free peer IPv6 with any that maintains IPv4 peering in good state.

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:
Set max-prefix of 1000 (IPv4) and 100 (IPv6)

Related ASNs
AS36040, AS43515, AS36561

Peering Requests: 
Contact the team - peering@google.com.