Action 1: Prevent propagation of incorrect routing information
All prefixes must have a valid IRR record. All IPv6 prefixes must have a valid RPKI record. Due to the existence of legacy spaces, we allow 'RPKI unknown' for IPv4 prefixes. We validate these information every 30 minutes.
Action 2: Prevent traffic with spoofed source IP addresses
We do not allow spoofed IP address to be passed through our infrastructures. Customers are only allowed to use their announced IP address blocks on/through their services. This is automatically provisioned.
Action 3: Facilitate global operational communication and coordination
We monitor our NoC emails 12 hours a day throughout the year. All correspondences will be expected to be replied within 24 hours.
Action 4: Facilitate validation of routing information on a global scale
All IP address blocks that are originated by our network have valid IRR records, which can be publicly accessed/queried through major RIR databases and RADB. We set up RPKI wherever it is possible for an IP address block. All IPv6 address block we announce have valid RPKI records. However, a small portion of IPv4 address blocks we announce have unknown RPKI record due to the fact that they are legacy spaces.