Action 1: Prevent propagation of incorrect routing information
We use PeeringDB. In it we put information such as: NOC contacts for troubleshooting, number of announced prefixes, looking glass, type of network, traffic exchange points, facilities, supported protocols and much other information. This service is very important so that we can locate the data of an AS, for example, in case of problems. Nothing better than knowing who to call or contact and having it in easy access. We use the IRR Internet Routing Registry and have a QRATOR Radar peering and filters to ensure that only correct advertisements are passed to the Internet. Validation of blocks and received routes, with RPKI, KRILL and validation, Routinator.
Action 3: Facilitate global operational communication and coordination
We use PeeringDB. In it we put information such as: NOC contacts for troubleshooting, number of announced prefixes, looking glass, type of network, traffic exchange points, facilities, supported protocols and much other information. This service is very important so that we can locate the data of an AS, for example, in case of problems.
Action 4: Facilitate validation of routing information on a global scale
We use the IRR Internet Routing Registry and have a QRATOR Radar peering and filters to ensure that only correct advertisements are passed to the Internet. Validation of blocks and received routes, with RPKI, KRILL and validation, Routinator.