Having your own block of IPv4 addresses is important for network independence, but not every organization can justify becoming a RIPE NCC member (LIR) just to get addresses. In our practice, we often see clients who are not fully aware of their options and think they need to register a LIR just to buy a /24 RIPE subnet, as if that were the only path available. In reality, if your business operates in the RIPE service region and you only need a small block for your own infrastructure, a more cost-effective solution can be to acquire a RIPE PI subnet. In this article, we explain what RIPE PI subnets are, how you can get one without being a LIR, and the pros and cons of PI addresses compared to the usual Provider Aggregatable (PA) addresses.
Understanding RIPE Address Types: PA vs. PI
The RIPE NCC, the Regional Internet Registry (RIR) for Europe and the Middle East, primarily provides two types of IPv4 subnets: Provider Aggregatable (PA) and Provider Independent (PI).
In this article, we focus only on subnets allocated or assigned by the RIPE NCC, specifically these two types. Legacy subnets—allocated before the establishment of RIRs—as well as other subnet types are not covered here. The complete list of RIPE subnet types can be found here.
Provider Aggregatable (PA) addresses are allocated by the RIPE NCC to its members (LIRs), who can then assign them to customers. The generally accepted best practice is to use PA address space, as it is the only sustainable way to scale the Internet and reduce the number of routing entries.
The trade-off is that PA address ranges can only be transferred or allocated to registered LIR members. Without LIR membership, an organisation cannot buy or receive PA space. This is the most common subnet type in the RIPE service region, and by default most IPv4 subnets offered on the IPv4 marketplace belong to this category.
LIRs can make assignments to their end users by creating ASSIGNED PA inetnums, or they can sub-allocate space to another organisation by creating SUB-ALLOCATED PA inetnums. The sub-allocated organisation may then take over some of the management of that space. When creating an assignment or sub-allocation, the LIR may set the end-user’s or organisation’s ORG object in the RIPE Database, which can differ from the subnet holder’s name.
Provider Independent (PI) addresses, by contrast, are assigned directly by the RIPE NCC to the end-user organisation and do not originate from any LIR’s allocation. This allows an organisation to hold a PI subnet without being a LIR.
Before IPv4 exhaustion, organisations could obtain PI space from RIPE NCC through a sponsoring LIR. Today, PI IPv4 address space can only be acquired on the secondary IPv4 market. However, since only LIRs communicate with the RIPE NCC and are responsible for maintaining accurate database information, end users can hold PI address space only as long as they maintain a contractual relationship with a sponsoring LIR. The sponsoring LIR manages communication with the RIPE NCC and pays the annual PI resource fees on behalf of the end user.
Having a sponsoring LIR does not make that LIR the subnet holder. The end user remains the legal holder of the PI subnet and can change sponsoring LIRs at any time if dissatisfied with service or pricing. The key requirement is that the end user must always have an active sponsoring LIR, unless they become an LIR member themselves. If a PI resource remains without a sponsoring LIR for more than 10 business days, the RIPE NCC will initiate deregistration of the independent Internet number resources in accordance with section B.2.2 of the RIPE NCC procedural document.
Another limitation is that PI subnets may only be used for the end user’s own infrastructure. RIPE policies explicitly prohibit leasing PI address space. It is also not possible to change the ORG object for PI resources, except in the case of a transfer (sale). Since PI blocks are usually rare, small and separate, it’s difficult to aggregate them into larger ranges.
If an end user decides to register their own LIR, they can transfer their PI subnet to their new LIR account. The LIR may also request to convert PI space into PA space, but the reverse conversion—from PA to PI—is not possible.
Obtaining a PI Subnet Without Becoming a LIR
PI subnets can be obtained both by LIRs and by end users. Normally, the standard way to obtain your own IPv4 subnet is to become a member LIR, which involves significant fees (approximately €1,000 sign-up and €1,800 annually as of 2025). For many small companies that only require a limited IPv4 subnet, such costs are not viable. Below is an overview of the steps to acquire a /24 PI subnet as an end user through a Sponsoring LIR:
1. Identify a Sponsoring LIR and sign the agreement
The first step for an end user is to find a Sponsoring LIR willing to sponsor their PI subnet. The end user signs a Sponsoring LIR Agreement, under which they pay an annual fee to the LIR. This fee covers both the RIPE NCC’s maintenance charge for the PI resource (currently €75 per year) and the sponsor’s administrative costs. In practice, the total annual cost usually amounts to €250–€300. Some sponsors may also charge a one-time setup fee, but this remains modest compared to full LIR membership.
The end user must provide basic corporate information to the sponsor. Due to the increasing number of fraudulent agreements, many Sponsoring LIRs require that the Sponsoring Agreement is signed with a qualified electronic signature or verified by a public notary. This ensures that the authorized contact is legitimate and prevents misuse.
2. Acquire a PI IPv4 subnet on the market
After the Sponsoring Agreement is signed, the next step is to acquire a PI IPv4 subnet on the secondary IPv4 market. Since RIPE NCC no longer assignes IPv4 PI subnets, such subnets can only be obtained via transfer. IPv4 PI address space is relatively rare, and its transfer requires precise handling to comply with RIPE NCC policies.
The most reliable approach is to work with an IPv4 broker specialized in the RIPE NCC service region. The broker assists with sourcing available IPv4 PI subnets, negotiating terms, and managing the transfer process. At Voldeta, we provide both Sponsoring LIR services and IPv4 brokerage, allowing us to deliver a full-package solution for end users. This way, the process with the RIPE NCC runs smoothly, as the Sponsoring LIR is the official contact point during the transfer.
3. Announce the subnet
Once the RIPE NCC finalizes the transfer, the PI subnet is officially registered under the end user’s organisation, with the Sponsoring LIR listed as reference. From this point, the end user has full control over the subnet within the framework of the RIPE NCC policies. The addresses can be announced via BGP using the end user’s own AS number, or alternatively the announcement can be delegated to an upstream provider.
Conclusion
RIPE IPv4 PI subnets provide an effective alternative for organisations that require their own address space but cannot justify the expense of operating a full LIR. A PI /24 IPv4 subnet gives businesses a stable, provider-independent block of IPv4 addresses, ensuring continuity and flexibility in network operations.
PI space is particularly well-suited for companies with relatively small but permanent infrastructure needs, where independence is a priority. By working with a Sponsoring LIR and a trusted broker, end users can secure such subnets in a cost-efficient and policy-compliant way.
If you would like to explore the current availability and market pricing of PI subnets, or if you require support with both Sponsoring LIR arrangements and IPv4 acquisition, please contact us at info@voldeta.com. Our team provides end-to-end solutions, from sourcing suitable IPv4 PI resources to handling RIPE documentation, ensuring that you can obtain and operate your own IPv4 subnet smoothly and without unnecessary complexity.
Author: Anastasia Kleiman.
Follow us to get the latest articles and news:
