RIPE ASN Application Requirements

Before applying for an Autonomous System Number (ASN), make sure you have prepared all required information and documentation. Here is what RIPE NCC needs for a smooth application.

Basic requirements

1. Applicant identity

Requirements differ for individuals and legal entities.

Individuals (natural persons): full legal name, residential address, ID document number (passport / national ID) and a copy of that document.

Legal entities: official company name, registered address, company registration number and a copy of the registration certificate.

In some countries sole proprietors count as natural persons — even if registered as a sole trader, apply as a natural person.

2. RIPE database objects

You need a RIPE organisation (org) object for the applicant. The org-name must exactly match the applicant's legal name. With a registered trademark or trading name, format it as Legal Name trading as Trademark.

You also need an IP prefix referencing that org object (an inetnum or inet6num with the org: attribute pointing to it). If you have no IP assignment yet:

Order RIPE ASN + /48 IPv6, which includes a free /48; or
Order a RIPE IPv6 allocation before applying.

For either option, add mnt-ref: GETIPV6-MNT to the applicant's org object so we can create the assignment.

3. Peering partners

Provide at least two ASNs you plan to peer with after your allocation. These seed your initial routing policy when the ASN is assigned.

Special circumstances

Applicants outside the RIPE service region

Provide proof of a network element inside the RIPE region (e.g. an invoice or contract for a server purchased or rented there). It must show the applicant's name and the element's location, and be valid for a period after the application date.

Minor applicants

Provide the guardian's basic information and an authorization letter signed by the guardian (a template is available during the order process).

Additional ASN requests

If you already hold an ASN and want another, include an explanation of why it is necessary plus supporting evidence.

Third-party applications

If you apply on someone else's behalf and they cannot sign the EUAA personally, provide an authorization letter signed by the applicant.

Checklist

Applicant identity and ID documents
Valid RIPE org object with a matching org-name
An IP prefix assignment (or order RIPE ASN + /48 IPv6)
At least two peering-partner ASNs
If applicable: proof of a RIPE-region network element, guardian authorization, justification for an additional ASN, or a third-party authorization letter

Have everything ready?

Order RIPE ASN

← All guides