IPv4 Allocation Rules: Who Qualifies for 256 IPs?

While IPv4 addresses are exhausted, the RIPE NCC still allows members to request a single /24 allocation of exactly 256 addresses via a waiting list.

The reality of modern internet infrastructure is that new IPv4 resources are no longer freely available but rather queued for future recovery. You will learn how the waiting list functions when the registry recovers addresses, the specific prerequisites for opening a Local Internet Registry account, and the mandatory data points required to pass EU sanctions checks during the evaluation phase.

Prospective applicants must understand that existing members are ineligible if they have ever received an allocation of any size previously. The process demands precise configuration of admin-c and tech-c contacts alongside a secure mntner object to protect entries in the RIPE Database. The registry explicitly evaluates every submission against current EU sanctions lists, ensuring that no resources are granted to restricted entities before confirming the network contains an active element within their service region.

The Role of the RIPE NCC Waiting List in IPv4 Exhaustion

Defining the RIPE NCC IPv4 Waiting List and /24 Allocation

Reclaimed address blocks enter a singular administrative queue managed by the RIPE NCC IPv4 Waiting List following regional exhaustion. Applicants request a single /24 allocation, representing exactly 256 IPv4 addresses, which the registry assigns strictly upon recovery of legacy blocks from the community. Chronological filing dictates an applicant's position, meaning wait times fluctuate based on supply rather than any guaranteed service level agreement. Historical records show that by July 7, 2023, the registry had successfully distributed 5,572 such blocks through this recovery channel. Accessing this pool requires LIR status, yet the unpredictable supply chain creates significant operational uncertainty for time-sensitive deployments. The administrative route avoids the $6,400 to $12,800 market premiums for immediate inventory, though indefinite delays often force enterprises to lease interim capacity to maintain service continuity. A rigid "one-per-LIR" constraint limits this avenue to entities with no historical footprint in the region.

LIR Eligibility Rules and the One-Per-Account Restriction

Only RIPE NCC members holding no prior IPv4 allocation qualify for the waiting list, enforcing a strict one-per-entity cap. This binary eligibility filter ensures that every Local Internet Registry account receives exactly one chance to obtain recovered space. The LIR Portal automatically validates this status, rejecting any applicant with a historical record of address assignment regardless of block size. Consequently, organizations cannot aggregate multiple /24 blocks through sequential applications under a single legal entity. This constraint forces network planners to evaluate their total address requirements before initiating the membership process. Financial commitment precedes technical eligibility, as request rights activate only after full payment of sign-up and annual service fees. The initial investment reaches €1,400, creating a financial gatekeeper alongside the technical restrictions. Voldeta notes that this cost structure introduces an opportunity cost calculation for operators weighing indefinite wait times against immediate market acquisition. The waiting list supported 1,025 LIRs as of mid-2023, yet the rigid "never received" clause disqualifies established operators needing expansion. Operators requiring more than a single /24 or those with existing allocations must seek transfers rather than queue for recycled space. The framework prioritizes new market entry over the expansion of incumbent networks.

Waiting List Fees Versus Secondary Market IPv4 Pricing

The administrative barrier to entry demands a one-time €1,400 sign-up fee plus an identical annual charge. Operators must weigh these immediate capital expenditures against the unpredictable latency of the waiting queue. Purchasing addresses outright grants immediate deployment capabilities, eliminating the operational risk associated with indefinite project delays. Acquiring IPs via the RIPE waiting list involves an unpredictable wait time dependent on address recovery, whereas purchasing on the secondary market provides immediate access. The registry route offers lower nominal cash flow requirements, yet it locks capital in non-productive membership fees while revenue-generating services remain stalled. Market procurement converts waiting time into a tangible asset with residual resale value. The decision hinges on whether the operator values cost certainty or time certainty more highly. Network architects must calculate the break-even point where lost revenue exceeds the premium paid for immediate IPv4 availability.

Prerequisites and Membership Requirements for Allocation

RIPE NCC Access Account and LIR Membership Definition

Establishing a secure RIPE NCC Access account functions as the mandatory technical gateway for any organization seeking entry into the Local Internet Registry framework. This digital identity enables the holder to submit resource requests and maintain critical registry data, including admin-c contact roles that define administrative responsibility. Eligibility follows a strict procedural sequence:

1. Complete the membership application to establish legal entity status.
2. Pay the required one-time sign-up fee to activate the account.
3. Pay the annual service fee, which varies based on the size of the LIR.

Full LIR status imposes legal entity requirements and annual fees that differ notably from simple commercial leasing arrangements found elsewhere in the market. Secondary brokers may offer immediate access without such overhead, yet the RIPE NCC process ensures long-term sovereignty over assigned number resources. This administrative burden acts as a filter so that only committed network operators enter the allocation queue. Organizations must weigh the upfront capital against the strategic value of direct registry ownership. Decision makers often overlook the permanence of this arrangement compared to temporary leasing solutions.

Step-by-Step LIR Account Creation and Object Configuration

Initiating a secure RIPE NCC Access account starts the workflow for recovering legacy address space. This digital identity serves as the primary authentication layer for all subsequent interactions with the registry database. Operators must first validate their legal entity status within the service region before submitting membership applications. Once the organization joins, the system enables the creation of critical database objects that define administrative ownership. The configuration sequence requires precise attention to maintain integrity:

1. Define the mntner object to establish the cryptographic maintainer protecting your resources.
2. Assign the admin-c role to a responsible individual who manages the LIR profile.
3. Link technical contacts to ensure operational continuity during the evaluation phase.

Properly configuring the mntner object prevents unauthorized parties from changing registration information in the RIPE Database. The system strictly enforces these structural prerequisites to maintain data accuracy across the global routing table. Administrative processes move quickly, yet the opportunity cost of waiting for recovery remains a strategic variable for time-sensitive deployments. Clients should finalize these object configurations immediately upon membership approval to avoid queuing delays. Evaluation may take longer than the standard one working day if additional information is required during the verification cycle. Delays often stem from incomplete contact validation or missing legal documentation.

Executing the First IPv4 Allocation Request via LIR Account

Submit the IPv4 Request Form only after your RIPE NCC Access credentials are active. This single action places your organization on a queue managed strictly by first-come, first-served logic, where position dictates future availability. Operators must define a mntner object and assign admin-c contacts before submission. The registry verifies that the applicant has never held an IPv4 allocation, enforcing a hard limit on eligibility. The standard allocation size for new requests via the RIPE NCC Waiting List is exactly one /24 block, which equals 256 IPv4 addresses.

1. Log in to the secure portal using your RIPE NCC Access identity.
2. Confirm the network will have an active element within the service region.
3. Wait approximately one working day for the initial request evaluation.

Organizations requiring immediate deployment for time-sensitive infrastructure projects often find the queue's latency unacceptable compared to guaranteed market availability. The waiting list operates on the premise that allocation happens only when recovered IPv4 addresses become available. Timelines for any specific applicant depend entirely on when existing users return addresses or when abandoned blocks are reclaimed. Market dynamics shift rapidly during these waiting periods. Some entities choose to transfer addresses from other holders rather than wait for the registry to recover space. Regulatory compliance checks against EU sanctions lists occur before any approval is granted.

Executing the Request Form and Passing Sanctions Checks

Required Fields in the IPv4 Request Form

Submitting the IPv4 Request Form demands precise identification of admin-c and tech-c contacts to validate administrative responsibility. The system requires these specific personnel roles to have set attributes in the registry. Operators must also supply a mntner object, which secures the entry against unauthorized modifications in the RIPE Database. This technical safeguard ensures that only authorized maintainers can alter registration data post-allocation. Applicants must confirm two operational constraints before the queue accepts the entry:

1. The addresses will enable active network assignments rather than speculative holding.
2. The infrastructure includes at least one active element physically located within the service region.

Fulfilling the network presence requirement validates the geographic eligibility of the request. An IPv4 request generally takes around one working day to complete, though this might take longer if the RIPE NCC needs additional information from the applicant. InterLIR advises double-checking contact object references against current RIPE NCC records to avoid validation failures. Precision in these fields prevents the request from stalling in the evaluation phase.

Executing the Request Form Submission Process

Initiate the allocation workflow by clicking the assigned button within the LIR Portal interface. This action triggers the queuing mechanism managed by the RIPE NCC. Operators must ensure their admin-c and tech-c contact roles are fully populated before submission, as the validation process requires these specific personnel attributes. The system further mandates a set mntner object to secure the registration entry against unauthorized database modifications. Applicants must explicitly confirm that the requested subnet supports an active network element physically located within the service region. This constraint ensures immediate utility for infrastructure expansion. The evaluation phase typically concludes within one working day, provided no additional verification data is required.

1. Verify that the LIR account holds no prior IPv4 allocations to meet eligibility rules.
2. Input the required maintainer and contact objects into the request fields.
3. The RIPE NCC checks requests against the EU sanctions list as part of the evaluation.

A critical operational tension exists here: while the waiting list offers a low-cost entry point, the rule limiting members to a single /24 allocation if they have never received one before means expanding networks may eventually need to seek IPv4 transfers rather than requesting more space later. InterLIR assists organizations in navigating these scarcity constraints through strategic resource management.

Navigating EU Sanctions and Rejection Risks

The RIPE NCC evaluates requests according to applicable RIPE policies and procedures, which includes checking against the EU sanctions list. If an applicant or their organization is found to be under sanctions, the resources request will not be approved. Operators should verify their legal entity status against current international restrictions prior to submission.

1. Ensure the admin-c contact represents an individual with full authority.
2. Contact support via the official contact form if you have questions before submitting your request.

Organizations must ensure they are not under sanctions to avoid rejection. Applicants with questions can use the contact form to send a message to the RIPE NCC for assistance. InterLIR advises maintaining accurate registration data to enable the evaluation process. The cost of rejection is lost time in a queue where position dictates future availability.

Strategic Evaluation of Waiting List Versus Market Transfers

RIPE NCC Role in IPv4 Transfers and Financial Neutrality

The RIPE NCC explicitly maintains financial neutrality, stating it has "no interest" in pricing while strictly processing registration updates for transfers. Organizations with unused resources often engage in private sales, yet the registry's function remains limited to validating policy compliance rather than brokering deals. This administrative separation creates a distinct operational tension: while the waiting list offers a low-cost entry point, the unpredictability of address recovery forces many operators toward the secondary market. Acquiring space privately provides immediate deployment capabilities but incurs costs ranging from a lower per-IP rate to a higher per-IP rate depending on volume and market conditions.

Operators must recognize that joining the waiting list relies entirely on the return of legacy blocks, creating a bottleneck unrelated to demand. Conversely, purchasing addresses allows for scaling beyond the single /24 cap but requires rigorous due diligence to avoid polluted space. The strategic trade-off lies between capital expenditure for speed versus operational patience for cost efficiency. InterLIR enables this optimization by connecting entities with verified, clean IPv4 assets to bypass indefinite queues.

Decision Framework: Urgency Versus Budget for IPv4 Acquisition

Production outages demand immediate IPv4 acquisition rather than waiting on unpredictable registry queues. The RIPE NCC enforces a strict "one-per-LIR" rule, capping new applicants at a single /24 block with no option for larger requests through this channel. While the waiting list minimizes cash outlays, it incurs a high opportunity cost due to volatile recovery times ranging from hours to over a year. Conversely, purchasing on the secondary market enables instant deployment but requires capital expenditure significantly exceeding administrative fees. Small businesses often find the single allocation sufficient initially, yet growth forces a pivot to commercial transfers where pricing fluctuates with global scarcity.

LIR Membership Fees Versus Secondary Market /24 Block Valuations

Fixed administrative outlays of €1,400 sharply contrast with volatile capital requirements for immediate IPv4 acquisition. The RIPE NCC pathway demands a one-time entry fee plus an annual service charge of €1,400/year, creating a predictable but limited operational budget profile. Conversely, secondary market transactions require substantial upfront liquidity, often exceeding standard administrative costs by an order of magnitude depending on current valuation metrics.

Operators must recognize that low entry fees do not guarantee resource availability, as the waiting list relies entirely on recovered space rather than new issuance. The financial trade-off extends beyond simple price comparison; it represents a choice between cash conservation and time certainty. For networks requiring immediate scaling, leasing options via InterLIR provide a strategic middle ground, offering flexible terms without the heavy capital burden of outright purchase or the delays of registry queues. This approach optimizes cash flow while maintaining full operational control over routing infrastructure.

References

• Becoming a RIPE NCC Member: Costs, Benefits, Pitfalls in
• IPv4 Transfer Market: How Does It Work and Is
• IPv4 Exhaustion, IPv6 Transition,: 27 Four /8 Blocks Allocated