IPv6 Address Leasing

Once your request is paid, your dashboard lists what to provide. If you have them at hand, it takes a few minutes; otherwise you have up to 10 days to send them:

• For a company, an extract from the company register or a Certificate of Good Standing, issued within the last 3 months.
• For an individual, a utility bill or a bank statement in their name, issued within the last 3 months.
• If the holder or the network is outside the RIPE NCC service region, a recent invoice or contract from a data centre or a transit provider located in the region.

The person who signs the agreement verifies their identity online with a passport or a national identity card and a selfie. A copy of the ID and the selfie is kept, encrypted, with the documents of your request, as the RIPE NCC requires. The assignment agreement is then signed online.

Contact us if you’re uncertain about any documentation needs.

The request asks for:

• The size of the prefix. A /44 or a /40 needs a few sentences on why a /48 is not enough, such as the number of sites.
• A few sentences on the network and what will run on the addresses, and the countries where they will be used.
• The AS number that announces the prefix: your own, or the one of your hosting or transit provider. You can add up to five other AS numbers for its ROAs.
• The holder's details, or the ORG-ID of its organisation if it already has one in the RIPE Database. An existing organisation must allow us to register resources to it with the line mnt-ref: ELAUNIRA-MNT.
• Who signs the agreement, and their phone number.

Your answers are saved as you go, so you can stop and come back later. A request covers one prefix: for several, send a request for each from your dashboard. If you don't have an AS number yet, you can request one from your dashboard too: a free IPv6 prefix comes with it.

Quickly. Nothing waits on a third party: the prefix comes from our own address space, so no RIPE NCC approval is needed. The identity check takes a few minutes, and the 10 days given for the documents are a deadline, not a delay. Once your documents are accepted and the agreement is signed, the prefix is usually set up within one business day.

If we cannot accept the request after the review, you are refunded except for the part that covers the verification. If we cannot deliver for a reason of our own, you are refunded in full. If the documents are not provided within 10 days, the request is closed without a refund.

If you order as an individual, you can withdraw within 14 days of the payment: you are refunded except for the part that covers the verification, until the prefix is delivered. The details are in our Terms of Use.

Provider Aggregate (PA) space is allocated by RIPE NCC to an LIR like Ipregistry (through its parent company), which then assigns portions to its customers. The PA space remains with the LIR, so if you change LIRs, you'll need to renumber your network. We provide PA IPv6 subnets directly allocated to us, ensuring a straightforward leasing process without third-party involvement.

Provider Independent (PI) address space assignments are made directly by RIPE NCC to the end user (customer) through a sponsoring LIR. This means if you change LIR (e.g moving from us to another LIR or from another to Ipregistry), you can take your PI address space with you without needing to renumber your network. Note that renting out PI space is against RIPE rules. We support PI assignments through sponsoring.

An IPv6 lease is billed yearly, one year up front. You can stop its renewal from your dashboard at any time: the lease then ends at the end of the year already paid.

RPKI records are configured automatically upon activation of IPv6 Provider Aggregate (PA) address leases, for the AS numbers given in your request. Subsequent adjustments are handled through technical support.

For Provider Independent (PI) address space (sponsored), you can create the RPKI record(s) from within the RPKI Dashboard in your RIPE account.

Once you receive your IPv6 assignment, you can manage reverse DNS records directly from your RIPE account. Create a domain object that links to your organization’s DNS servers, and ensure that the reverse DNS zone is active on those servers to meet RIPE's validation requirements.

Your organization has control over reverse DNS delegations and routing details by default. When PA IP space is leased from us, the inetnum record is automatically configured with:

• mnt-lower: YOUR-MNT
• mnt-domains: YOUR-MNT
• mnt-routes: YOUR-MNT

This setup enables you to manage the entries independently, which is sufficient for everyday operations.

To uphold our abuse policy, however, the Maintainer (mnt-by) attribute in the inetnum record is fixed and cannot be modified. In other words, while you can adjust most aspects directly, any changes that might affect compliance with our policies must be coordinated with us.

We believe this structure provides the best balance between operational autonomy and adherence to our regulatory requirements.

A strict zero-tolerance policy is maintained, explicitly prohibiting activities including:

• Hacking, Spam, Denial of Service (DoS), and Distributed Denial of Service (DDoS) attacks.
• Hosting content that is threatening, defamatory, or otherwise illegal.
• Operating public VPNs, proxy services, or TOR nodes.
• Any other unlawful activities not explicitly listed above.