Some IXPs offer access to Google's VPP Program as a value-add to compensate for this, i.e. you'd establish a bilat or VLL with the IXP's VPP ASN to receive AS15169 routes.
Especially for smaller operators with sub-10G aggregated traffic this is the only viable solution. Further, if you're doing 10G+ to any provider, you'd find that it's more viable to establish redundant PNIs in any case. - CH ________________________________ From: Will OBrien via NANOG <[email protected]> Sent: Wednesday, 20 August 2025 7:46 AM To: [email protected] <[email protected]> Cc: Will OBrien <[email protected]> Subject: Google is not turning up any new peering on IXs? We recently turned up a new IXP and I’m going through the motions of arranging the usual peers, etc. I’m extremely surprised by this one: Public Peering Google no longer accepts new peering requests at internet exchanges (IXPs). However, Google maintains dedicated connectivity to the internet exchanges (IXPs) listed in our PeeringDB entry<https://www.peeringdb.com/asn/15169>. We also maintain existing BGP sessions across internet exchanges where we are connected. For networks who do not meet our PNI requirements Google will serve those networks via indirect paths. I can only presume that someone who doesn’t pay for cross connect fees came up with this plan. This feels short sighted at the least. Considering the benefits of peering, I have to express some dismay at this disservice to the internet in general. Anyone from Google care to explain what appears to be a willful withdrawal of support for the IXP community? _______________________________________________ NANOG mailing list https://lists.nanog.org/archives/list/[email protected]/message/77ZSJJ65QQMALALSFHXJD7WAPFA6P2F4/ _______________________________________________ NANOG mailing list https://lists.nanog.org/archives/list/[email protected]/message/S3AC25GXC3CE32JQ7BXXXPF3VX7IFXUV/
