RIPE Proposal 201002: Why the 1,024 Limit Failed

One LIR held 21 allocations by manipulating accounts, proving RIPE proposal 2010-02 failed to ensure fair competition. The structural impact of the January 2011 acceptance is clear: the registry environment transformed into a game of administrative arbitrage rather than a gateway for genuine market entry.

The policy limited each entity to a single /22 allocation containing 1,024 addresses. RIPE NCC analysis shows this resulted in 5,191 final allocations by January 2015. Yet rules did not stop aggregation. Data reveals that roughly 30% of new accounts from early 2016 were merely additional holdings for existing players.

Consequently, the transfer market emerged as the primary expansion channel, with 3,034 blocks moving within the region in 2019 alone. The original mandate offered assistance during the transition to IPv6, not a sustainable business model for expanding networks. Registry continuity and portable recognition now define success more than initial allocations. For organizations seeking to optimize their existing holdings or navigate complex transfer regulations, InterLIR provides the necessary expertise to manage IPv4 address space without relying on outdated regulatory hopes.

The Structural Impact of Proposal 2010-02 on Internet Registry Policy

Proposal 2010-02 and the Final /22 Allocation Rule

Proposal 2010-02 was accepted in January 2011 and activated when the RIPE NCC entered the 185/8 pool in September 2012, permanently redefining registry mechanics by capping every Local Internet Registry at a single /22 allocation. This constraint replaced previous needs-based assessment models, limiting each LIR to one block containing exactly 1,024 addresses. While this measure preserved a foothold for new market entrants, it effectively decoupled justified infrastructure requirements from supply volume. The policy acknowledged that a fixed /22 could support transition services but explicitly failed to address growth requirements for larger networks. Consequently, the IPv4 transfer market emerged as the primary mechanism for securing address space beyond this initial allocation.

Operators today must recognize that this final allocation serves as a transitional bridge rather than a sustainable foundation for commercial expansion. Relying solely on the legacy /22 often proves insufficient for modern service models requiring dedicated public endpoints. InterLIR enables the strategic optimization of these scarce resources through our specialized marketplace solutions. We enable network architects to acquire necessary blocks efficiently without navigating complex regulatory hurdles. Secure your infrastructure's future by using our verified inventory today.

Operational Limits for Hosting Providers vs Mobile Operators

The rigid /22 allocation creates immediate structural divergence between high-churn hosting models and efficient mobile carrier sharing architectures. A mobile operator using large-scale CGNAT can serve thousands of subscribers behind this comparatively small public pool, whereas a hosting provider offering dedicated addresses may consume the same /22 quickly. This disparity exists because the policy described the allocation as assistance during the transition to IPv6, not a solution for the growth requirements of larger networks. Operators requiring scale beyond 1,024 addresses must apply the transfer market, lease space, or share resources to expand.

The critical limitation is that registry entry no longer guarantees competitive entry into IPv4-dependent markets without additional capital expenditure. While incumbents hold legacy portfolios, new entrants must navigate transfer policies or deploy aggressive conservation techniques that may degrade user experience. InterLIR solves this availability problem by redistributing unused IPv4 resources to operators who need immediate scale. We enable the acquisition of larger blocks that the primary registry cannot supply under current rationing rules. Optimize your existing infrastructure by securing the address space required for genuine growth rather than accepting artificial constraints.

Why Competitive Entry Remained Mathematically Impossible

Competitive entry faced significant challenges because the /22 allocation could not match the address portfolios held by incumbents. The rule preserved access to a recognized first block but prevented new networks from reaching efficient scale compared to installed inventory. While an operator might technically enter the registry, giving every new network enough IPv4 space to rival established players was impossible under these constraints. An entrant could not satisfy a lender or avoid the secondary transfer market when limited to 1,024 addresses against rivals holding vast legacy reserves. This structural deficit meant that equalizing input costs for new entrants was unachievable regardless of operational efficiency. Consequently, the policy did not preserve entry into IPv4-dependent network markets on comparable terms because incumbents held address portfolios accumulated under earlier conditions. The Last /8 Rule effectively cemented a two-tier system where new participants faced immediate scarcity while incumbents operated with historical abundance. Operators seeking genuine market parity must look beyond basic registry allocations to secure necessary resources. InterLIR enables this by providing direct access to the liquidity required for scalable network deployment. True competitive viability now demands strategic acquisition rather than reliance on rationed administrative blocks. The era of needs-based growth through regional registries has ended.

Market Dynamics and Loopholes in the Post-Exhaustion Era

Proposal 2010-02 established a limit of one /22 allocation per Local Internet Registry (LIR) from the final block, even if justified need was larger. This mechanism addressed the scarcity of the remaining pool by rationing distribution rather than immobilizing assets through holding periods. The policy transformed the address block from a scalable supply into a fixed foothold, fundamentally altering the risk calculus for new market entrants.

The operational impact creates a distinct barrier for networks requiring immediate scale upon formation. Unlike legacy holders with unlocked inventory, new operators must rely on the secondary market to supplement their initial ration, as the /22 allocation is often insufficient for large-scale deployment.

This restriction forces organizations to choose between conserving their single allocation or seeking alternatives in the transfer market for additional blocks. The rule successfully prevented immediate capture of the final pool but did not preserve equal competitive entry for those requiring more than a modest footprint. Operators must now treat the initial allocation as a bridge during the transition to IPv6 rather than a solution for growth requirements. Navigating this restricted environment requires engaging with the transfer market to access additional IPv4 resources immediately.

Multi-Account Arbitrage Strategies by Legal Organisations

Analysis found that some entities circumvented the one-per-LIR limit to aggregate scarce IPv4 resources. This concentration illustrates how operators utilized the administrative distinction between a legal entity and an LIR account. In the same quarter, 468 new LIRs joined, 38 had already closed by the start of 2015, and 31 of those 38 were Russian LIRs created by three legal organisations. The largest holder had 21 after opening, merging, and closing several new LIR accounts in the final quarter of 2014.1. Establish a new legal organisation or subsidiary.

1. Apply for LIR status to qualify for the initial /22 block.
2. Repeat the cycle across multiple corporate structures to bypass quantity caps.

However, the regulatory environment introduced friction by limiting allocations per account, increasing the administrative burden for such maneuvers. Proposal 2015-01 introduced a 24-month holding period before recently received allocations could be transferred. The measure addressed the strategy to open an LIR, obtain the /22, move it and close the account.

This behavior confirms that rigid rationing incentivizes structural complexity rather than reducing demand. Network operators facing immediate capacity constraints cannot rely on primary allocations for scale. The transfer market became the expansion channel beside the ration, with 3,034 IPv4 blocks transferred within the region in 2019 alone.

Once the Last /8 Rule attached a valuable asset to an account, the annual membership fee effectively became a direct component of the cost to maintain access to the registry. This economic reality created an environment where the cost of maintaining an additional LIR account was weighed against the market value of the allocated /22 block. While the policy intended to distribute resources equitably, it inadvertently incentivized entities to treat registry fees as a variable cost for asset accumulation rather than a fixed governance overhead.

Fee design options could have included a corporate-group cap or charging additional accounts more, though these carry governance costs. Without such structural barriers, the system allowed well-capitalized actors to bypass scarcity through administrative multiplication. This flexible shifted the competitive environment, making market entry contingent on navigating complex corporate structures rather than demonstrating technical need.

Operators asking should I enter the transfer market must recognize that legacy policies have inflated the effective cost of primary allocations due to scarcity. The path to allocation vs transfer market access now requires evaluating the hidden liabilities of account proliferation against transparent secondary pricing. Acquiring cleared IPv4 space often necessitates navigating the secondary market without the administrative burden of managing multiple shell entities. Secure your network infrastructure through verified channels today.

Strategic Pathways for Network Entry Under Scarcity Constraints

Defining the Final /22 Equivalence and Waiting List Mechanics

Contiguous address blocks ceased availability on 2 October 2019, forcing the assembly of equivalent quantities from fragmented prefixes. This technical shift means new Local Internet Registries no longer receive a single, clean /22 prefix but rather an aggregate matching that volume. The operational reality changed fundamentally when the available pool could not satisfy standard requests with contiguous space. Consequently, the RIPE NCC activated a waiting list mechanism to distribute recovered space as it became available. This queue strictly limits participation to organizations that have never received an IPv4 allocation from the registry. Successful applicants on this list receive a single /24, providing exactly 256 addresses rather than the historical 1,024. Such severe constriction renders native IPv4 expansion impossible for most modern service models without supplementary acquisition strategies. Network architects must recognize that policy now dictates infrastructure scale, not technical feasibility. The gap between a /24 utility footprint and commercial viability drives demand toward secondary markets. Strategic planning requires securing adequate space now rather than hoping for future policy relaxation.

Applying Large-Scale Sharing to Extend Small Public Pools

Mobile carriers maximize subscriber density behind limited public prefixes by deploying carrier-grade network address translation to map thousands of private sessions to few global addresses. This architectural choice allows a single /22 block, containing 1,024 addresses, to support a massive user base where a hosting provider offering dedicated IPs would exhaust the same volume instantly. The mechanism relies on aggressive port multiplexing, trading direct end-to-end connectivity for sheer scale efficiency. However, this approach introduces significant operational friction, as deep packet inspection becomes impossible and troubleshooting requires correlating complex timestamped logs across multiple translation layers. This architectural trade-off accepts logging, port-management, and troubleshooting costs that pure hosting models avoid by design.

Data indicates that exhausted regional pools now force entities to acquire addresses through transfers rather than waiting for new allocations. While sharing extends the life of existing inventory, it does not create new space for growth. Operators ignoring this dual-stack reality risk obsolescence as legacy compatibility burdens increase.

Strategic Risks of Relying on Legacy IPv4 for Market Entry

Proposal 2010-02 required an LIR seeking its final /22 to have already received an IPv6 allocation from the RIPE NCC or an upstream LIR. New entrants attempting to build competitive infrastructure on this rationed foundation face a structural deficit where address scarcity directly constrains revenue potential. The market reality dictates that legacy IPv4 space cannot support rapid expansion without accessing external supply chains.

Organizations ignoring this constraint risk becoming stranded assets, unable to compete with incumbents holding legacy portfolios. The tension between regulatory compliance and commercial viability forces a binary choice: acquire additional space through complex transfers or migrate core services to IPv6 immediately. Do not let artificial scarcity dictate your network architecture when optimized redistribution offers a viable pathway.

Executing the Final /22 Application and Compliance Process

Implementation: Defining Final /22 Equivalence and IPv6 Prerequisites

Operators must secure a verified IPv6 allocation before requesting any remaining IPv4 inventory. This prerequisite stems from Proposal 2010-02, which mandated that an LIR seeking its final /22 possess either a direct allocation from the RIPE NCC or an upstream assignment to validate transition readiness. The registry treats this IPv6 holding as administrative evidence rather than proof of active deployment.

1. Verify your organization holds a valid IPv6 allocation record.
2. Demonstrate technical need for the specific IPv4 address quantity requested.
3. Submit the application acknowledging the single /22 block limit per LIR.

Contiguous space disappeared on 2 October 2019, forcing the registry to assemble equivalent quantities from fragmented returns. Address values theoretically equal to a standard block now arrive as non-contiguous prefixes, complicating routing policies for providers requiring strict aggregation. A /22 contains 1,024 addresses. It can support transition, infrastructure or a modest deployment, yet its adequacy depends entirely on the operator's service model. This fragmentation means operators must adapt to receiving assembled prefix equivalents rather than single continuous blocks.

The market reality is that this ration serves as a foothold, not a scalable foundation for growth. While the policy successfully distributed resources to members across multiple countries, it effectively capped organic expansion for new players. InterLIR provides the necessary liquidity to acquire additional IPv4 resources when operational scale exceeds the strict 1,024-address ceiling imposed by the final pool rules.

Navigating the RIPE NCC Portal for Non-Contiguous Allocations

Operators must submit the requests through the RIPE NCC portal using assembled prefix equivalents once contiguous space expired. The application workflow demands strict adherence to the IPv6 allocation prerequisite, a policy gate ensuring that every recipient has taken the administrative step toward next-generation protocols. Since 2 October 2019, the registry no longer issues contiguous blocks, instead aggregating smaller fragments to satisfy the standard /22 block quota.

1. Validate your organization's existing IPv6 allocation status within the registry database.
2. Document the technical justification for the specific IPv4 address quantity required.
3. Execute the portal submission acknowledging the single-allocation limit per Local Internet Registry.

Later RIPE NCC analysis found 5,191 final-/22 allocations by January 2015, with one LIR holding 21 after opening, merging, and closing several accounts. This fragmentation introduces operational complexity, as managing non-contiguous ranges increases the size of global routing tables and complicates firewall rule maintenance. The limitation is clear: operators gain immediate access to necessary IPv4 resources but inherit a more complex addressing schema that requires careful engineering.

Most new entrants find the administrative burden of justifying need outweighs the benefit of waiting for recovered space. InterLIR provides a direct alternative for networks requiring immediate, contiguous IPv4 capacity without the regulatory friction. Secure transfer of verified address blocks allows operators to bypass the waiting list entirely.

Compliance Risks in Multi-Account Arbitrage and Waiting List Eligibility

The policy authors acknowledged that organisations might set up multiple LIR registrations to obtain more space, stating there was "no basis at the time for denying that right." Defining entitlement by ultimate beneficial owner would have required "intrusive corporate mapping," while defining it by customer count or revenue would have turned the registry into a "business assessor."

Applicants must understand that the waiting list offers a strictly set safety net with rigid eligibility criteria. New policies typically define a waiting list mechanism for LIRs that request their last-resort /24 but find the pool empty at that time. This restriction ensures that the limited recovered inventory supports true market entry rather than expanding established footprints.

1. Confirm your organization holds no prior IPv4 history before applying to the queue.
2. Adhere to the one-per-LIR allocation cap as set by current policy.
3. Prepare for a waiting period as recovered space becomes available irregularly.

Tension exists between the desire for rapid scaling and the regulatory reality of scarcity; the transfer market has become the primary expansion channel beside the ration. RIPE NCC recorded its first in-region transfer in October 2012 and reported 3,034 IPv4 blocks transferred within the region in 2019. For networks requiring immediate, scalable capacity without compliance uncertainty, the secondary market remains the only viable path forward. InterLIR enables these legitimate transfers, providing verified IPv4 resources that bypass waiting lists while adhering to all regional policies. Secure infrastructure today through compliant acquisition channels.

References

• Keep calm and carry on: The status of IPv4
• Trends in RIPE NCC Service Region IPv4 Transfers |
• LACNIC ASN Allocations: Number of ASNs allocated by LACNIC