If you have a BGP session with Mean Servers, we have previously verified your letter of authorization (LOA) to ensure you are utilizing an ASN that has been assigned to you. Clients are no longer required to provide Mean Servers with a new LOA for each IP address space they wish to announce. Instead, we filter all announced space by Route Origin Authorization (ROA) and prevent AS hijacking by filtering the as-path advertised to us.
If the IP address space you wish to announce has been assigned an ROA that is attached to your current public ASN, all you need to do is configure your IP addresses for announcement. Our routers will automatically verify this space to check for the ROA and if valid, it will be announced to our peers and IP transit providers. No need to contact support to get your space authorized, all you need to do is announce it and our network will propagate the route appropriately. Mind the le prefix assigned at your RIR, this can cause announcements to be labeled as invalid.
Note that standard practices do apply. ROAs can take 24-48 hours to correctly propagate, until our cache servers receive this information, we cannot speed up any request. Routes without an ROA or an invalid ROA will not be announced without exception.
If you are experiencing difficulties, you are invited to utilize our looking glass to help debug any problems you may have with announcing your IP space. When you announce your space to us, we will automatically assign it the following communities based on the ROA state of the prefix. Utilizing the show route command against this space will show you any internal communities we have assigned the space.
32931:901 - RPKI Valid
32931:902 - RPKI Invalid (route will be rejected from announcement)
32931:903 - RPKI Unknown (route will be rejected from announcement)
32931:666 - Blackhole (blackhole propagates to all routers, switches, systems, transit providers, and peers)
