B-IX Regional VLAN consolidation

We are consolidating the 2 VLANs (Regional and Peering) in favor of the “Peering” VLAN, as we will need a bigger single prefix soon. Both services (Peering and access to Regional partners) will remain the same at a logical level, but we will remove VLAN Peering and the subnets (2001:7f8:8e::0/118 and 217.174.157.0/24) on 30.09.2024. Most of the members, especially those who weren’t present in VLAN “Peering” are contacted directly and 90% of the traffic is already moved to VLAN Peering. Please move your traffic over to the Peering VLAN as soon as possible and disable your BGP sessions with the Regional Route Servers. Please keep in mind also, that you have to move also any private peering sessions over to the “Peering” VLAN. If you have a different BG and INT routers or if you just need another IP addresses or any kind of support, feel free to contact us.

Thank you!
B-IX.NET Team

Geo-distributed RS redundancy and RPKI complete adoption

As part of our effort to decentralize the “Internet” (one of the main goals of each Internet Exchange), in our main operating region (Eastern Europe and Bulgaria) we’ve finalized the provisioning of 3 new route servers spread all in different directions from our main locations in Sofia, Bulgaria. The geographical positions are chosen carefully in account of the backbone hubs of the International and Bulgarian fiber optic routes and the main goal is to provide redundancy to the customers without a direct connection to Sofia, such as (but not limited to) Bulgaria’s South-West, South and the whole Eastern Bulgarian region. We’ve preconfigured some BGP sessions in the new Route Servers, for customers we think will benefit, as their traffic is not going through Sofia, but directly in the exchange through our widely distributed partners network. If any member wants a BGP session in any of the other Route Servers, please ask, and we’ll happily create it. You can see the details at https://b-ix.net/technical/details/ and the preconfigured BGP sessions directly in our Looking Glass.

!! Please note that configuring BFD for all BGP sessions is highly recommended and already automatically preconfigured.

Regarding our second topic – RPKI, we are enforcing RPKI validation in the last remaining Route Servers (RS-BG1 and RS-RG1) at the end of this week (16.08.2024) exactly at 00:00. You may experience a reset of your BGP session. Please verify that your BGP session with any of the other Route servers is working and of course, check your AS for prefixes with invalid RPKI status (https://my.ripe.net/#/rpki ; https://rpki-validator.ripe.net/ui/) or look for filtered prefixes once you log in our portal.

UI filters and RPKI adoption

There are several changes and new features that need your attention:

1. We’ve enabled BGP engineering from the web user interface of our platform. You can define both inbound and outbound BGP announcement policies from the web portal. If you still don’t have a login, please email our support, and we’ll be happy to create one for You.

2. B-IX adopted RPKI validation currently at 50%. This means that all “2nd” route servers, for example, RS2-BG/RG (both IPv4 and IPv6) are validating the prefixes with RPKI and rejecting those that aren’t with “VALID” status. We plan to adopt the RPKI validation at 100% by the end of next month (07.2024), so please review the RPKI status of your prefixes. You can check in the portal for your rejected prefixes or you can use the Looking Glass directly.
Note: The IRRDB validation is still active and the members should have properly set both IRRDB and RPKI for their prefixes to be advertised in the exchange.

3. We see that there are members who still aren’t using the automatically provisioned BFD session for them. Please check the status of your BFD sessions and configure them if needed. This will ensure that wherever you are connected – you don’t have to worry about your transport to B-IX. You can find the details here: https://b-ix.net/technical/details/

New member A1.bg

Let us welcome our latest member:

Member: A1 BG
AS number: AS8717
BG IPv4 address: 185.1.30.4
Location: Telepoint Sofia
Port speed: 20G
Policy: open
RS Client: yes