CUBE will always peer with Public Peering Exchange Points registered at as151062.peeringdb.net,
but may reject or terminate peering with the following networks
When AS-SET is not submitted and not registered in the PeeringDB
When an AS-SET has been submitted but does not match the AS-SET registered in the PeeringDB
When prefixes other than customer and origin are identified
CUBE always refers to IRRs in the following order.
See www.gin.ntt.net/support-center/policies-procedures/routing-registry for more information.
The filtering is then based on the IRR information and the ROUTE object derived from the AS-SET submitted by the customer.
As for RPKI, CUBE does not refer to it. However, depending on the upstream, invalid and undefined prefixes may be filtered.
Data is provided to RIS via Route Collector
Data on geofeed is available at cbik.net/geofeed.csv
We provide data to bgp.tools and Looking Glass
We provide data for ROA and ASPA via rpki.co/repo/Cube