Summary

  • The RIPE NCC Executive Board has temporarily restricted the acquisition of additional LIR accounts, including requests already in progress and certain merger or acquisition cases. It has not required existing accounts to close or consolidated.
  • The move pauses account growth while the community debates whether the IPv4 waiting list should continue to measure eligibility per LIR or set one allocation per RIPE NCC member.
  • That distinction matters because the current published policy caps RIPE NCC allocations at one /24 per LIR, while one membership can contain several LIR accounts.

On 29 September, RIPE NCC members encountered a new boundary around account structure. A Board decision adopted two weeks earlier temporarily stopped members from acquiring additional Local Internet Registry (LIR) accounts. It also suspended requests already submitted or under way, including account additions prompted by changes in the business structure of two RIPE NCC members, such as a merger or acquisition. The Board can revisit the restriction at any time.

The decision is narrower than a closure order. Existing multiple-account members do not have to consolidate, and the Board set no timetable for phasing accounts out. The RIPE NCC says an acquirer may transfer resources from an acquired member to its own LIR under current procedures; the acquired account is not automatically required to remain. Those distinctions matter in transactions, but the pause still changes which account structures members can add while the policy debate runs.

The scale is small in one sense and system-wide in another. RIPE NCC staff reported that, on 1 August 2026, 410 members — about 2.1% of membership — held 708 additional accounts, 3.4% of all LIR accounts. In the previous two years, 41 members opened 67 additional accounts. The RIPE NCC says those accounts generate work across billing, compliance, audits, transfers, account closure and voting-right assignment. Its explanation does not include an audited cost per account or a quantified savings estimate, so the case for simplification is operationally described but not priced publicly.

The harder question sits in the allocation rule. RIPE-826, the published IPv4 policy, puts requests on a first-come, first-served waiting list, offers exactly one /24 when space is available, and limits total RIPE NCC allocation to a single LIR to 256 addresses. RIPE NCC’s own account of the post-run-out procedure describes eligibility for that recycled /24 at LIR-account level. But the operating arrangement permits one member to hold multiple LIR accounts. “One per LIR” and “one per member” are different policies when those units do not coincide.

The Board minutes make the unresolved choice explicit. One possible outcome is to align policy language with the present operating procedure, allowing members to continue to receive allocations through eligible LIR accounts. Another is for the community to decide that each member should receive only one waiting-list allocation and write that limit into policy. The Board did not choose between them. Its account freeze creates time for that decision; it is not itself an amendment to the allocation rule.

History explains why the distinction survived. RIPE NCC staff describe extra accounts as an exception first used to separate business units and preserve structures after mergers. IPv4 exhaustion and the final-/8 rule later made each eligible LIR account economically consequential. In 2015 the Board temporarily suspended new accounts; the membership voted in May 2016 to allow them again. The stated concern was that a ban could encourage separate legal entities and separate memberships, changing both transparency and the number of votes.

That episode shows that accounting units can affect more than registry workload, even though a separate legal entity does not automatically establish a separate operating network or a distinct public interest.

A later one-member cap could make eligibility easier to express and avoid treating an internal account as a newcomer. But without a clear definition of “member” for controlled entities and acquisitions, it could move the incentive elsewhere. Keeping a per-LIR rule may fit the current allocation mechanism yet preserve a reason to expand accounts. The evidence does not establish which outcome would be fairer to applicants, more efficient, or less costly; those are questions for a policy process supported by transparent operating data.

For a company acquiring another RIPE NCC member, the practical checklist is therefore not simply “keep or close the account.” It is to distinguish the legal member, LIR account, registered resources, allocation history and any waiting-list application; confirm which records can transfer; and identify whether the account freeze affects the requested structure. The RIPE NCC says existing resource-transfer procedures can move resources after a merger. It does not say that the freeze suspends every transfer or disables an acquired network.

The institutional boundary is consequential. The Board controls the temporary ability to add an account; the RIPE community’s address-policy process determines the allocation policy. A useful interim restriction can prevent the present exception from expanding while that process works. It cannot substitute for deciding which unit should receive scarce addresses, how acquisitions are treated, or how any new rule avoids rewarding a change in corporate form rather than a real newcomer.

Heng Lu’s Note 64 offers a design lens rather than evidence about RIPE NCC: keep an initial operational rule narrow, then make later choices explicit and local to the process that owns them. Applied here, that means documenting the pause separately from policy, publishing the burden and eligibility data, and letting the address-policy process state whether the relevant unit is the LIR or the member. The registry has bought time; the community still has to define the rule.

The two account figures answer different questions. The 708 accounts describe the existing stock across 410 members; 67 accounts acquired over two years are a recent flow, not an annual forecast. Neither number shows how much staff time a typical account consumes, how costs vary by member, or whether all multi-account structures exist for the same reason. They also do not identify which members have a current allocation request. The percentages establish that the arrangement is concentrated, not what a transition would cost or who should qualify for addresses.

“Temporary” has no stated end date. The resolution allows the Board to revisit the restriction but does not provide an automatic expiry or a date by which the community must settle the allocation question. If policy work takes longer than expected, an interim measure can become the practical operating rule for an extended period. A clear review point and an account-status notice would help members plan mergers and restructuring without confusing a paused account request with a ban on existing resources or services.

Sources