Action 1: Prevent propagation of incorrect routing information
NetActuate's customer BGP sessions have strict prefix-lists set validated against IRRs records. Additionally, NetActuate is filtering RPKI invalids for most BGP sessions, with 100% filtering occurring as of 02/2023.
Action 2: Prevent traffic with spoofed source IP addresses
NetActuate follows BCP38 for all cloud, dedicated server, and colocation customers. Transit customers are requested to follow BCP38 procedures.
Action 3: Facilitate global operational communication and coordination
NetActuate keeps an accurate contact list for their network at https://as36236.peeringdb.com.
Action 4: Facilitate validation of routing information on a global scale
NetActuate publishes RPKI and IRR records on all of their prefixes.
Action 5: Encourage MANRS adoption
NetActuate asks that all of our customers follow the requirements of MANRS. We ensure that our customers follow MANRS when reaching our network by following BCP38, RPKI invalid filtering, and filtering prefixes by published IRR records.
Action 6: Provide monitoring and debugging tools to the peering partners
NetActuate provides a public looking glass for partners to investigate routing from our network at https://netactuate.com/lg/.