Google peering
More Direct and Reliable Access to Google’s Network Through BIX
The Google Verified Peering Provider (VPP) program enables BIX members to access Google’s network through their existing BIX connection, without the need to establish a separate, direct peering connection with Google.
BIX (Budapest Internet Exchange) is an official Google Verified Peering Provider, making this service available to all members connected to BIX. The solution simplifies connectivity to Google’s network while leveraging BIX’s redundant, high-capacity network infrastructure.
Requesting the Service
Access to the Google VPP service is not enabled by default for BIX members. If you would like to access Google’s network through BIX, please submit your request to info@bix.hu.
The service is available to BIX members at no additional cost.
There is no need to contact Google directly for connectivity or configuration. BIX handles the entire process. There is no minimum traffic requirement, so smaller members are also eligible to use the service.
The service is available at all BIX locations:
| Budapest | |
| H-1132 Budapest, Victor Hugo u. 18-22. | Victor Hugo Street Data Center Building |
| H-1108 Budapest, Kozma u. 2. | 2Connect adatközpont (DC10) |
| H-1087 Budapest, Asztalos Sándor u. 13. | T-Systems Cloud & Datacenter (Dataplex) |
| Wien | |
| A-1210 Wien, Louis-Häfliger-Gasse 10. | Digital Realty (VIE1) |
| Frankfurt | |
| D-60314 Frankfurt am Main, Weismuellerstrasse 36. | Digital Realty (FRA8) |
| D-60326 Frankfurt am Main, Kleyerstrasse 90. | Equinix (FR5) |
How Does It Work?
The Google VPP service is built on BIX’s existing peering infrastructure.
Once the service has been activated, the prefixes advertised by a member to the BIX RS1 and RS2 route servers are also propagated to Google. In turn, BIX makes the network prefixes advertised by Google available to the member through both route servers.
As a result, no separate BGP session with Google is required to exchange traffic with Google’s network. All necessary routing information is exchanged through the BIX route servers.
The BIX route servers (RS1 and RS2) do not prepend their AS number (AS5507) to the AS path. When Google VPP is enabled on a BIX member’s router, the first AS hop towards Google in the routing table entries for Google routes will be AS210788, the AS number of the routers responsible for BIX’s Layer 3 services.
Redundant Connectivity to Google’s Network
BIX connects to Google’s network through two separate data center rooms, providing redundancy. Each location has multiple 400 Gbps connections (n × 400 Gbps).
The data centers connected to Google’s network are interconnected in a ring topology, ensuring connectivity with Budapest as well. Particular attention was paid to designing the topology so that the optical cable routes are physically separated as much as possible while maintaining optimal latency.
The redundant architecture is designed to ensure that the failure of any single network component, location, or connection path does not result in Google’s network becoming unavailable to BIX members.
Prefix Validation
BIX route servers perform IRR- and RPKI-based prefix validation and filter out prefixes that are considered invalid according to these validation mechanisms (IRR or RPKI Invalid). In addition to the BIX route servers, Google also validates the prefixes it receives.
When adding new prefixes or onboarding a new member, please note that Google may take several days (typically 2–10 days) to download and process changes to IRR databases. Therefore, we recommend allowing for this potential processing time when planning service activation.
Google’s documentation on validation and the required processing time is available here.
Both the BIX operations team and Google strongly recommend that BIX members create and maintain valid RPKI ROA records for all their advertised prefixes. Implementing RPKI significantly improves the security of route advertisements and contributes to the more reliable operation of the routing infrastructure.
RIPE NCC: RPKI Dashboard Quick Tour 2026
BGP advertisements sent to BIX can be viewed on the BIX Looking Glass page. To list the advertised prefixes, click the prefix count displayed in the State/PfxRcd column. Detailed information is available by clicking the Details button next to the relevant prefix in the resulting list.
Google Networks Available Through the Service
The following Google autonomous systems are accessible through the service:
When connecting to the service, BIX members should expect to receive approximately 5,000 additional IPv4 prefixes and 600 additional IPv6 prefixes from the BIX route servers (RS1 and RS2).
The exact number of current Google prefixes can be viewed on the BIX Looking Glass page at the following addresses of the routers responsible for BIX’s Layer 3 services (AS210788):
193.188.137.248
193.188.137.249
2001:7f8:35::21:788:3
2001:7f8:35::21:788:4
The current number of Google prefixes is displayed in the State/PfxRcd column.
Route Optimization
After activating the service, additional route optimization may be required to ensure optimal traffic routing.
This may be necessary if Google sees the routes available via the BIX and through international transit connections as having equal AS-PATH lengths. In such cases, Google recommends applying AS-path prepending to routes advertised via international transit connections. This makes these routes appear longer from Google's perspective, helping favor the route via the BIX.
While this approach may be suitable for many providers, it is not necessarily ideal for BIX members that also provide transit services.
The BIX is currently in discussions with the Google team to find an alternative solution that fully meets the needs of the affected members.