Action 1: Prevent propagation of incorrect routing information
We strictly refrain our client from not updating their IRR database, and check that their routes are legit before updating filters.On our side our IRR objects are up to date with AS-SET AS-DCLUX up to date.
Action 2: Prevent traffic with spoofed source IP addresses
We have implemented robust measures to prevent the transmission of traffic with spoofed source IP addresses across our network. This critical security practice enhances the integrity and reliability of internet communications by mitigating the risk of IP address spoofing, which can be exploited for various malicious activities, such as DDoS attacks and man-in-the-middle attacks
Action 3: Facilitate global operational communication and coordination
We reply promplty to any mail dropped at noc [at] datacenter.eu
Action 4: Facilitate validation of routing information on a global scale
Our peering policy is open and all of the details are visible on PeeringDB and through IRR objects.
RPKI ROAs: To enhance the security of our routing information, we have created Route Origin Authorizations (ROAs) for all prefixes associated with our ASNs using RIPE's resource certification service. This cryptographic validation helps in preventing route hijacking and ensures the authenticity of our prefix announcements.
Please visit our PeeringDB : https://www.peeringdb.com/net/7408