BatamIX Route Server Guide

BatamIX operates so-called route server systems according to RFC7947 to facilitate the exchange of BGP announcements between peers at BatamIX. Each peer needs only to set up a BGP connection to the route server in order to receive the BGP announcements of all other peers having a BGP connection with the route server.

BatamIX operates two route servers at each of its Internet Exchanges that are redundant to each other.

Route servers keep the number of necessary BGP sessions low for BatamIX members because you need only one BGP session to each of the route servers to receive the prefixes of all other route server users.

You can use BGP communities to tell the BatamIX route servers to whom to announce (or not announce) your prefixes.

Incoming you can use filter lists on your own routers to decide what to accept (or not accept) from the prefixes the route servers announce to you.

Route Server Guides for the exchanges

besides the conventional route servers, BatamIX also operates a so-called Blackholing route server. This Blackholing route server only distributes BGP announcements marked as Blackholes which are typically used to fight massive DDoS attacks. Please also see our Blackholing Guide to learn more about this topic.

BGP Session Parameters?

This section provides a brief overview of the BGP session parameters to connect to the conventional and Blackholing route servers:

Route ServerIPv4IPv6
Route Server#1 - LAN JKT27.124.87.1
Route Server#2 - LAN JKT27.124.87.22402:d680:1000:4::2
Route Server#1 - LAN BTM27.124.88.1
Route Server#2 - LAN BTM27.124.88.22405:aac0:212::213
Prefix limit (your side)20.0005.000

How and what the route servers filters

BatamIX filters are updated every 1 hours. Don't forget to register your IP prefixes in the IRR database well in advance (at least 24h before announcing the first time).

Bogon and Martian filtering

Please make sure not to announce routes that

  • are not > /24 (IPv4) and > /48 (IPv6) (RFC7454)
  • are bogons/martians (private and reserved IP prefixes as defined by RFC 1918, RFC 2544, RFC 3927, RFC 5735, RFC 6598, and RFC 6890)
  • BatamIX is peering LAN (please also do not announce any of our peering LANs in the Internet!)
  • contain bogon ASNs in the BGP AS path (private and reserved ASN numbers as defined by RFC 7607, RFC 6793, RFC 5398, RFC 6996, RFC 7300)
  • are not < /8 (IPv4) and < /19 (IPv6) (RFC 7454)
  • BatamIX will drop these kinds of routes.

    Check the status of your routes

    You can check the status of your announced routes to us in the BatamIX Looking Glass, member can see Looking Glass in Member Portal – the reason why a route is filtered is also shown, as is a hint on how to fix the issue.

IRR and RPKI validation

Whatever route you announce will be filtered and validated by rpki and re-checked by the Internet Routing Registry (IRR). The AS-SET you provide will be recursively resolved. Then filtering is executed as follows:

  • Origin ASN needs to be in member cone (make sure that your AS-SET is well maintained and that all your downstreams are included)
  • if the result is RPKI Valid, the route is accepted
  • if the result is RPKI Invalid, the route is rejected
  • if the result is RPKI NotFound/Unknown, we check if the route is resolvable for its origin ASN

Route Server Setup

The route server setup at BatamIX consists of two machines, The software utilized to provide the route server service is BIRD. Of the two conventional route servers only one is required. However, in order to use the route server service, every peer is requested to connect to both machines for redundancy purposes, so that if one machine is out of order (e.g. maintenance), the route server service can still be used.

Route Server Control

Operational BGP Communities can be used to control various functions of the route server. With this communities, you can:

  • control the redistribution of advertised prefixes
  • prepend your own AS up to three times
  • rigger the calculation of a new alternate path (if available) for your advertised prefixes before you start commencing a maintenance
  • More information can be found here.

Our Mission

Why pay premium prices to transit, when you can connect to an inordinate number of your fellow regional networks for a single flat monthly cost? stop pay per megabyte to get to your colleague just down the road.


To provide a robust, transparent and neutral peering platform to all its members to improve secure, network performance, increase resiliency, and reduce operational costs..