BALT-IX: Baltnet Neutral Carrier Internet Exchange
BALT-IX's PEER service reduces IP Transit and network costs by aggregating all kinds of ISPs on a Layer 2 switching platform. By connecting networks on the most advanced industry platforms, the service enhances the speed and reliability of all kinds of IP products.
Enhanced end-user experience
Bandwidth requirements for services like video LIVE and VOD, gaming, cloud, or voice over IP grow continuously, and every millisecond, if not nanosecond, is important; peering provides for the lowest latency path and therefore greatly enhances the end-user Internet experience.
Deciding for BALT-IX's services means making a safe investment with a reliable partner. Let us show you how to increase your revenues with peering. To take advantage of the BALT-IX PEER service, you need to have access to BALT-IX, and you need to have your own Autonomous System Number (ASN).
Reduced IP transit costs
The more networks you reach with one cross connect, the fewer cross connects you have to pay for. With just one cross connect to the BALT-IX platform you reach most of Lithuanian networks. Reaching a multitude of networks also reduces your IP transit costs.
Short routes to IP networks in the metro region
BALT-IX’s platforms are distributed platforms connecting multiple locations in Vilnius. Prime - Tier 3 Datacenter Liepkalnio st. 160C, Vilnius, others - Juozapavičiaus st. 13 Vilnius, Laisvės av. 60, Vilnius, Radastų st. 2, Kaunas and other locations.
No need to arrange individual peering arrangements
The connection to BALT-IX not only saves costs on cross connects, but it saves you a lot of time: you don’t have to arrange peering agreements for hundreds of networks by contacting them individually. The BALT-IX route servers give you instant access to about 80% of the connected networks.
Control over routing and IP traffic flow
Peering gives you the control over routing and your traffic flow. You can see how much traffic is flowing over your port and where it goes; you don’t have to struggle with overbooked IP transit routes.
Highly reliable connectivity
The standard service level guaranteed in our Service Level Agreements for availability of the BALT-IX PEER service is 99.98%; our platform has maintained 99.98% percent uptime since 2015.
If peering sessions fail, transit services provide backup connectivity to peer networks; if the transit connectivity fails, the peering connectivity is unaffected.
Increased network quality
Direct peering provides you with the lowest latency path to your target networks on an uncongested path; therefore, peering improves the quality of networks.
|ISP Name||AS Number||Policy||Speed||AS SET|
|Baltnetos komunikacijos Customers||AS15440||Open||40G||AS-ML|
|Baltnetos komunikacijos DC||AS42549||Open||40G||AS-ML|
The Route Servers (RS) are used to simplify peering between BALT-IX participants and excludes the need to have a multiple BGP session with each other IX member. RS retransmits BGP announcements between the connected participants, thus peering with the RS means establishing peering relations with all other participants connected to that RS.
Once the BGP session is established, IP traffic will be exchanged transparently between pairs of neighbours on the peering LAN: the route-server IP address will never be shown as a next-hop address, nor the route-server ASN will appear in the as-path. Because no data is passing through the RS, therefore RS doesn't influence cross-network delays.
Note: RS doesn't insert its own ASN into the AS_PATH by default some routers might deny such updates, to solve this behaviour you should specify "no bgp enforce-first-as" (IOS/IOS-XE) or "bgp enforce-first-as disable" (IOS-XR).
Route Server Configuration Info
In BALT-IX the service is offered by means of two route-servers on the peering LAN. All the members should configure two peering sessions, in order to take advantage of the redundancy in case of an issue or maintenance. All RS are configured for both IPv4 and IPv6 peering.
Primary RS1-L160C: 188.8.131.52/24 or 2001:1ab8:8486::1/64
Secondary RS2-J13: 184.108.40.206/24 or 2001:1ab8:8486::254/64
AS-SET: AS-BALT-IX and AS-BALT-IX-v6
- RS does not accept default route
- RS does not accept private AS
- RS does not accept Martian’s prefixes (BOGONS VIA HTTP)
- RS accepts the route if it has corresponding "route/route6" object that exists in IRR DB. Each member has its own list of prefixes that are considered valid for the BGP announcements, this list is obtained by querying IRR DB using ASN off the member or a given as-set.
Filters are updating automatically every night at 04:00.
Maximum number of announced prefixesFor those members who have a max-prefix limit configured on the peering sessions with the route-servers, these are the recommended minimum thresholds:
- 60k prefixes for IPv4 peering
- 30k prefixes for IPv6 peering
BGP Community Attributes
Each of route-server does not modify, process or remove communities received from customers except those communities which are processed by the route-servers themselves.Communities affecting announces to other peers:
|0:8486||Do not announce prefix to all peers|
|0:X||Do not announce prefix to peer ASX|
|8486:8486||Announce prefix to all peers|
|8486:X||Announce prefix to peer ASX only|
|rt:0:X||Do not announce prefix to peer ASX|
|rt:8684:X||Announce prefix to peer ASX only|
Well-known communities like no-export or no-advertise are also supported. If no communities are set, then received prefixes are advertised to all peers by default.Following communities are also applied by RS:
[65000 + <R>]:[10000 + 1000 * <X> + <CC>] ~ Where (based on RFC4384):
|<R>||is the 5-bit Region Identifier|
|<X>||is the 1-bit satellite link indication|
|X = 1 for satellite links, 0 otherwise|
|<CC>||is the 10-bit ISO-3166-1 country code [ISO3166]|
|and <R> takes the values:|
|Africa (AF)||00001 (1)|
|Oceania (OC)||00010 (2)|
|Asia (AS)||00011 (3)|
|Antarctica (AQ)||00100 (4)|
|Europe (EU)||00101 (5)|
|Latin America/Caribbean Islands (LAC)||00110 (6)|
|North America (NA)||00111 (7)|
|65000:10000||Tier 1 and Tier 2 ISPs|
Note: Communities are set to all prefixes received from BGP peer, based on peer AS country code:
whois -h whois.cymru.com " -v PeerAS"
With some exceptions like Tier1 and Tier2 ISPs, and some others.