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-IELO up to date.
Action 3: Facilitate global operational communication and coordination
We reply promptly to any mail dropped at peering [at] ielo.net and are following any BGP incident that might occur.
Action 4: Facilitate validation of routing information on a global scale
Our peering policy is open and most of the details are visible on peering-db and through IRR objects.We will have a dedicated website for making policy, contacts, and prefixs up to date.