Core Transit BGP ASN Management
Our ASN Manager is designed to be simple and to confirm the BGP information we check when building a BGP session.
Steps to take:
1. You will want to add your AS number to the ASN manager
2. To confirm your AS number, you will need to send a verification email to one of your contacts associated with the ARIN, RIPE, etc. entry for your ASN.
3. Your prefixes will be learned from your IRR data and be presented on the prefixes page (click on your AS number to see this).
4. You will need a valid ROA for your prefix / AS pair.
How often do we check RPKI & IRR / AS-SET Data?
We poll every 6 hours: at 00:00, 06:00, 12:00 and 18:00 UTC. Each run re-reads their IRR records and AS-SET, and any changes are pushed to our network devices approximately 15 minutes later. So a new prefix shows up within about 6 hours.
A ROA alone won't add a prefix. The prefix list is built from IRR route objects (route/route6 in ARIN's IRR or RADB), not from ROAs. ROAs only decide RPKI validity, and we drop any RPKI-invalid prefixes.
So, along with the ROA, they need a route or route6 object for the prefix with their ASN set as the origin. For downstream ASNs we check your AS-SET as well. The advertising ASN also has to be a member of your AS-SET. Once all of these conditions are met, we pick up your advertisement in the next 6 hour cycle.
