Action 1: Prevent propagation of incorrect routing information
Customer announcements are validated through statically and explicitly configured ingress filters, ensuring only authorized prefixes and AS paths are accepted. The ownership of resources is verified through various sources before filters are created and BGP peering is established. Similarly, our announcements to upstreams are filtered based on prefixes and AS paths to ensure compliance and operational integrity
Action 3: Facilitate global operational communication and coordination
We actively participate in technical mailing lists of IXPs where we are present and attend meetings held by Italian IXPs. To ensure accessibility and transparency, we maintain an up-to-date PeeringDB record for abuse, peering, and NOC-related requests. Additionally, we keep our RIPE IRR entries current with accurate information about our AS and organization. Contact information is also readily available on our website.
Action 4: Facilitate validation of routing information on a global scale
All our routing policies are public and published in the RIPE IRRDB