Action 1: Prevent propagation of incorrect routing information
We are committed to maintaining a secure and reliable global routing system. To prevent the propagation of incorrect routing information, we implement:Prefix filtering based on IRR databases (RADb, RIPE IRR, APNIC, ARIN) and automated RPKI validation to reject invalid announcements.
Strict AS-PATH and prefix-list filtering to ensure only authorized routes are advertised.
Bogon filtering, and manual review of all customer BGP announcements.
Action 2: Prevent traffic with spoofed source IP addresses
We are committed to securing the global internet by preventing IP address spoofing. To ensure that only legitimate traffic flows through our network, we implement:RPKI validator.
Bogon and RFC1918 filtering to prevent invalid traffic from entering or leaving our network.
Regular NetFlow analysis to monitor and improve our anti-spoofing measures.
Action 3: Facilitate global operational communication and coordination
Yes, we facilitate global operational communication and coordination between network operators.Our organization prioritizes operational transparency and collaboration through up-to-date contact information in WHOIS, PeeringDB, and RIPE
Action 4: Facilitate validation of routing information on a global scale
Yes, we facilitate validation of routing information on a global scale.Our organization ensures transparency and validation of routing information through the following actions:We publicly document our routing policy, advertised prefixes, and ASNs in PeeringDB (https://www.peeringdb.com/net/32124).
We maintain up-to-date IRR records in RADb/RIPE IRR for all our advertised prefixes.
We have implemented RPKI ROAs to validate our prefix announcements and prevent hijacks.
We ensure that all customers and peers comply with strict BGP filtering policies to avoid incorrect route advertisements.
Our WHOIS records contain valid admin-c, tech-c, and abuse-c contacts for routing-related issues.