IPv4 and IPv6 Addresses available for immediate lease/rent.

How to Set Up Your New ASN: A Step-by-Step Guide
So your organisation has acquired an ASN and the IP address space, or is seriously thinking about it. But you are not sure what the next steps are to ensure the global visibility of your ASN and IPs in BGP?
We regularly get these questions from our clients, so we understand how confusing this can be at first. This guide shows precisely what needs doing, step by step, to get you up and running quickly. It focuses on the RIPE (registry) side of the configuration, rather than the BGP router setup. If you need help with your routers, we offer a reasonably priced BGP implementation service.
We also introduce tools to help you validate the results, and a printable checklist of every step, so that you can keep yourself organised as you read.
Download the printable ASN checklist (PDF)
- 1IP transitAn upstream provider sets up a BGP session with you and filters what you announce.
- 2PeeringDB profileYour network's public profile. Many tools and some providers read it.
- 3IRR route objectsA route or route6 object for every prefix, naming your ASN as the origin.
- 4RPKI ROAA signed Route Origin Authorisation for every prefix.
- 5AS-SET (optional)A grouping of your ASNs, so providers can build filters from it.
- 6Routing policyUpdate the import and export statements of your ASN.
- 7Reverse DNSA domain object with two name servers, if you need reverse DNS.
- 8Talk to your providersAsk how they build filters and how often they update them.
- 9ValidateCheck RIPE Stat, the Hurricane Electric BGP Toolkit and PeeringDB.
What you need before you start
- An ASN. It is the number that identifies your network. If you are not sure what it is, read what an ASN is. If you do not have one yet, we can register it for you.
- An IP prefix to announce. A prefix that you hold, that is sponsored for you, or that you lease.
- A RIPE account that is allowed to update the objects of your resources. Everything in this guide is done in the RIPE Database and the RIPE dashboards.
- An upstream provider that offers BGP. The first step below explains what to look for.
Step 1: Sign up for an IP Transit
First of all, for your organisation to announce a BGP route, you need an upstream provider to establish a BGP session and exchange routes.
The upstream provider could be an ISP or a hosting company where you host your servers.
As part of the service often called “IP Transit”, they will establish a BGP session with you.
However, this guide is not going to attempt to make a recommendation on upstream providers as these vary from country to country, and it is impossible to cover all the options available to you.
If your organisation already holds an ASN, then hopefully your upstream providers are already decided. Otherwise, you are encouraged to do your research separately.
As you are going to learn, sooner or later your upstream providers employ some kind of route filtering on the BGP session with you. They do this to ensure that you only announce the networks you are authorised to announce.
This practice protects the rest of the internet from what is technically known as a “prefix hijack”. It happens when a network operator advertises a route of another network operator that they are not authorised to advertise, and so attracts the traffic destined for that network.
Now, with this introduction out of the way, let's focus on the actual steps for you to follow.
Do not have an ASN or IP addresses yet?
We register ASNs and lease IPv4 and IPv6 space.
Step 2: Create a PeeringDB profile
Quoting directly from PeeringDB's (opens in a new tab) website:
PeeringDB is a freely available, user-maintained, database of networks, and the go-to location for interconnection data. The database facilitates the global interconnection of networks at Internet Exchange Points (IXPs), data centers, and other interconnection facilities, and is the first stop in making interconnection decisions.
So, before you do anything else, you should create a PeeringDB profile for your organisation.
Some of the tools that we introduce later depend on your organisation having a PeeringDB profile to display proper information. Also, if you are thinking of peering on an Internet Exchange, then PeeringDB is a must.
While the process is pretty straightforward, it requires manual verification to link your ASN to your PeeringDB account. So, please make sure that your email address is correct in the RIPE Database before you proceed.
One point worth mentioning is that you will come across the option for specifying a route prefix limit. Some providers use these on their BGP sessions to limit how many prefixes you can advertise to them before they disable the BGP session. This is called a prefix limit. This is yet another layer of protection against route leaks.
Our advice here is to start with something like 25 even if you are announcing just a single route. The reason is that you are likely to forget that you have set this up, and it has the potential to cause issues later.
Takes you directly to PeeringDB, for your convenience:Create a PeeringDB account (opens in a new tab)
Step 3: Create IRR route objects
The Internet Routing Registry (IRR) is a database used to record a connection between a route (IP address space) and the originating ASN.
Each Regional Internet Registry (RIR) runs an IRR database for its own region: RIPE (opens in a new tab), APNIC (opens in a new tab), AFRINIC (opens in a new tab) and ARIN (opens in a new tab), and, since 2020, LACNIC (opens in a new tab), whose IRR (opens in a new tab) is generated from its RPKI ROAs and its WHOIS data.
These databases are available to their respective resource holders only. To put this in perspective, as an example, RIPE routes can be registered in the RIPE IRR (part of the RIPE Database), but not in the APNIC IRR.
Additionally, there are third-party IRR databases that accept routes from all RIRs, so it would be acceptable to register RIPE routes in them. Examples are:
- RADb (opens in a new tab) (free to query, a paid subscription to register objects)
- NTTCOM (opens in a new tab) (run by NTT)
- ALTDB (opens in a new tab) (free to use, objects are registered by email)
However, you should use your own RIR's IRR database as much as possible for the best results, as some network providers ignore one or more of the third-party databases.
The route objects in the RIPE Database look like this. The examples in this guide use documentation values (192.0.2.0/24, 2001:db8::/48 and AS64500), which are reserved for examples and are never routed on the internet.
route for IPv4
route: 192.0.2.0/24
descr: Example Ltd
origin: AS64500
route6 for IPv6
route6: 2001:db8::/48
descr: Example Ltd
origin: AS64500
So, the route and route6 attributes describe the network address for IPv4 or IPv6, respectively, and the origin describes the originating ASN.
Add a descr attribute too (use the “+” button if the form does not show it). Some tools, such as the HE BGP Toolkit (opens in a new tab) that we introduce later, use it as the network name.
To create the route objects, use these links. You need to log in to your RIPE account.
Takes you directly to RIPE, for your convenience:Create a route object (IPv4) (opens in a new tab)Create a route6 object (IPv6) (opens in a new tab)
And populate the form as in the example below:
Do not have addresses to announce yet?
You can lease IPv4 or IPv6 space and announce it from your own ASN.
Step 4: Create an RPKI Route Origin Authorisation
If you lease your addresses from us, we create the ROAs for you; you only need to create your own route objects.
Resource Public Key Infrastructure (RPKI) is a cryptographic method of signing route objects that associate a BGP route announcement with its originating ASN. RPKI is defined in RFC6480 (opens in a new tab).
The RPKI was created to work around some limits of the IRR, which does not validate the origin ASN of an announcement, technically allowing a network to announce somebody else's IP blocks.
To create an RPKI Route Origin Authorisation (ROA), use the RPKI Dashboard. You log in with a RIPE NCC Account that belongs to a RIPE NCC member (an LIR), which can create ROAs for its own allocations. If you hold PI (Provider Independent) or Legacy space and are not a member, RIPE has a separate guide (opens in a new tab) to get you started, and your sponsoring LIR can help.
Takes you directly to RIPE, for your convenience:Open the RPKI Dashboard (opens in a new tab)
In the dashboard, create a new ROA with your origin AS, the prefix and the maximum length. Leave the maximum length at its default, which is the length of the prefix that you announce (for example /24 for a /24). RIPE discourages longer values (opens in a new tab), because they can allow hijacking through more specific prefixes. The exception is traffic engineering with BGP: if you plan to announce more specific prefixes than the one you hold, for example two /24s from a /23, set the maximum length to /24 (or create a ROA for each /24), otherwise those announcements will be marked invalid.
If you are leasing your IPs from a provider such as LIR SERVICES, the block is held by your provider, so you need to ask your provider to create the ROAs. We create these automatically for all our clients.
Step 5: Create an AS-SETOptional
This step is entirely optional, so feel free to skip it if it doesn't apply to you.
An AS-SET is an object that groups multiple ASNs together. It can then be used by other networks (for example upstream providers) to generate BGP filters that allow routes from multiple ASNs on a single BGP session.
It is going to be super handy if your organisation decides to provide IP Transit as a service to clients at a later date, or partners with another network to provide a backup connection for each other.
Whatever your plans are, our opinion is that it is still worth creating an AS-SET with just a single ASN, as it can save you quite a bit of time in the future on contacting your upstream providers to request this change.
Note: Starting in 2023, it is no longer possible to create non-hierarchical (i.e., AS-MYCOMPANY) AS-SETs in the RIPE database. This is to prevent potential crashes between different IRR databases. You would need to create a hierarchical AS-SET, such as AS64500:AS-MYCOMPANY, instead.
To create an AS-SET, use this link:
Takes you directly to RIPE, for your convenience:Create an AS-SET (opens in a new tab)
Check that the members attribute lists your ASN, and add it with the “+” button if it is not shown.
If you create an AS-SET, use it in your routing policy in the next step.
Step 6: Check and update your Routing Policy statements
The import and export statements describe your Autonomous System's routing policy. These are written in the RPSL (Routing Policy Specification Language), which is defined in RFC4012 (opens in a new tab). While not a common practice anymore, some network providers may still rely on these to create their BGP filters and authenticate peering relationships.
We suggest that you create these and keep them up to date.
If your organisation already has an ASN, you may remember that as part of the original ASN registration you provided details of two peering partners (usually upstream providers). RIPE then used this information to create the routing policy statements, which may look like this:
import: from AS64501 accept ANY
export: to AS64501 announce AS64500
While the above statements relate to IPv4 only, some network providers build both IPv4 and IPv6 filters from these statements for simplicity. However, this isn't always the case, so we also recommend creating mp-import and mp-export statements, which were specifically introduced to support both IPv4 and IPv6.
The final example would look like this:
import: from AS64501 accept ANY
export: to AS64501 announce AS64500
mp-import: afi ipv6.unicast from AS64501 accept ANY
mp-export: afi ipv6.unicast to AS64501 announce AS64500
If you created an AS-SET in the previous step, use its name (for example AS64500:AS-ALL) instead of your ASN in the export filters, like in the following example:
export: to AS64501 announce AS64500:AS-ALL
mp-export: afi ipv6.unicast to AS64501 announce AS64500:AS-ALL
To update these, you need to edit your ASN (aut-num) entry in the RIPE Database.
To do this, search for your ASN in the RIPE Database and click the “update” button.
Takes you directly to RIPE, for your convenience:Open the RIPE Database query page (opens in a new tab)
For simplicity, we suggest that you do this update in the “text area” mode, using the button at the top right of the form.
Step 7: Configure Reverse DNS
You may also need to set up reverse DNS records for your networks, for example if you plan to host mail servers.
RIPE validates the DNS server configuration as part of the setup process, so you need to meet some specific conditions. These are, quoting directly from RIPE's website:
- Make sure you set up at least two name servers that are authoritative for the zone.
- Ensure that the servers are at least in different subnets, but preferably in different networks that are geographically distributed.
- The resolvable names of these name servers should be in the NS resource records of the zone.
- The SOA resource record (RR) should have the same content, both serial number and other data, on all the nameservers.
- The SOA should contain a valid ‘RNAME’ (the contact address).
- The timing parameters should be reasonable.
The reverse DNS is controlled by the domain object in the RIPE Database.
Takes you directly to RIPE, for your convenience:Create a domain object (opens in a new tab)
Enter your prefix and the names of at least two name servers, and the form shows the reverse zone it will create. The example below uses the documentation prefix 192.0.2.0/24.
Step 8: Talk to your upstream providers
That's it! We've covered all the technical steps, and it is time to talk to your upstream providers and ask some questions. And, optionally, let them know what your AS-SET is.
Our printable checklist has these questions with space for the answers, so you can bring it to the call.
Download the printable ASN checklist (PDF)
The questions that you should ask:
- Do you build BGP filters automatically or manually?
- If automatically, how often do you update the filters?
- If manually, can you build them based on the AS-SET, or do you need a list of prefixes? How often do you make manual changes?
- Do you enforce any prefix limits on the BGP sessions? How is the limit updated, and what is our current limit? Ask if updating it automatically from PeeringDB is possible.
These should hopefully cover the most common scenarios, but if you find something else worth mentioning that comes up in discussion with your provider, please let us know so that we can update this guide.
Step 9: Validate your announcements
So now that you have followed all these steps, it would be helpful to validate that your announcements are working as expected. For this, we introduce a few tools.
However, please bear in mind that most of these tools aren't real-time, so it may take a few hours to a few days for them to pick up your announcements.
| Tool | What it shows |
|---|---|
| RIPE Stat (opens in a new tab) | RIPE's own statistical tool, with handy functions such as Routing Status and Visibility. Just search for your own ASN. Updated a few times a day. |
| Hurricane Electric's BGP Toolkit (opens in a new tab) | Our go-to tool for general information on any ASN: peering information and the network prefixes advertised. Updated daily, but may take a few days to show up initially. |
| PeeringDB (opens in a new tab) | A database of networks and their interconnections, ideal for finding the facilities where a given network is present. You've hopefully listened to us and created a profile for your ASN by now! |
| Looking Glass | Shows whether your routes are properly seen by various networks in real time, although the output can be a little difficult to read at first. Google your upstream provider's name + “looking glass”, and give it a go. |
You are done when:
- Your ASN and prefixes show in RIPE Stat (opens in a new tab)'s Routing Status.
- The Hurricane Electric toolkit (opens in a new tab) lists your prefixes under your ASN.
- Your PeeringDB (opens in a new tab) profile is verified.
- Your upstream providers confirm your filters are updated.
Stuck? If a route still does not appear after a couple of days, or a ROA shows as invalid, send us your ASN and prefix and we will look. Contact us.
Need help with the router side?
Your provider's filters are only half of it. We configure BGP on Cisco, Juniper, Mikrotik and other routers.
Conclusion
Thanks to this guide, you've got everything that you need to get started in one place. It hopefully saves you some time, and you found it useful.
Now that your IPs are visible in BGP, you may also want to read our guide to how IP geolocation works and how to correct it to ensure that their location is recognised properly, and what a geofeed is if you want to publish it yourself. The glossary explains the terms used here, such as IRR, RPKI and BGP.
Oh, and remember to download our printable checklist.
Still missing an ASN or IP addresses?
We register ASNs and lease IPv4 and IPv6 space, and set them up with you.
Related Services
Have a question about IP addresses or ASNs?
Tell us what you are working on. We lease IPv4 and IPv6 address space, register and sponsor AS numbers, and look after the RIPE relationship for you.
Contact Us



