Why the registry layer is a structural risk for IP address ownership

Your customer sees an API endpoint, a hosted application or a dependable internet connection. Behind that service sits an address—and behind the address sits a registry relationship. Buying the block does not remove that dependency. A dispute far upstream can become your team's problem even when your own equipment is working.

Registry-layer risk is the exposure created when continued recognition of your address resources depends on an institution your business does not control. LARUS's answer is first-party IPv4 continuity: take that upstream responsibility seriously, put a documented rights foundation behind the supply and help your network keep serving customers.

The registry layer: useful records, concentrated influence

Regional Internet Registries maintain number-resource records and related services. The five RIRs are AFRINIC, APNIC, ARIN, LACNIC and RIPE NCC. Their role includes recording allocations, assignments and transfers so networks can identify resources and contacts.

That coordination matters. It is also different from running your network. A registry entry does not carry your customers' packets, buy transit or configure your routers. BGP exchanges routes; upstream providers supply connectivity; RPKI and IRR records help networks assess routing authorisations. Each part must work for the service to be dependable.

The record

Who is listed against the prefix, and which information other operators can verify.

The authority

Who can change recognition, certificates or the conditions attached to registration.

The service

Whether customers can continue reaching the addresses on which their operations depend.

These layers interact, but they are not interchangeable. A sound continuity strategy protects the customer's service across them rather than stopping at a correct database entry.

An acquisition does not buy independence from the registry

In the IPv4 market, “ownership” often means acquiring a registered position and control of a block. The purchase can be valuable. Yet the registry relationship continues after the seller is paid, along with its policies, administrative powers and jurisdiction.

ARIN's published agreement, for example, combines defined resource rights with limited remedies. RIPE NCC's terms state that registration does not confer property rights. These are the registries' stated positions. A business should not confuse those arrangements with protection for everything it has built on its addresses.

The imbalance is commercial as well as legal: the registry relationship can affect infrastructure worth far more to you than the fees paid to the registry. An address purchase leaves your business holding that exposure. Adding a broker changes the sales channel, not the upstream foundation.

For a fuller explanation of the distinction, read what IP address ownership means.

AFRINIC shows why the rights foundation matters

A global network can depend on a registry incorporated in a particular country. That makes local corporate rights and court remedies commercially relevant to operators elsewhere. The AFRINIC proceedings bring this dependency into view.

The published June 11, 2025 order in SC/COM/MOT/000399/2025 directs changes to AFRINIC's records to include Cloud Innovation as a member under section 91 of the Companies Act. It also records the receiver's undertaking concerning rectification. The court materials let customers examine this foundation directly.

That foundation matters to LARUS's offer. Cloud Innovation's mandate to LARUS appoints the customer-facing commercial, operational and technical platform for the covered address estate. It connects the registry-side position to a first-party operator customers can work with.

The lesson for your network is practical: choose the party and rights structure behind the addresses, not just the prefix and monthly price. A listing alone cannot do that work.

How registry exposure becomes a customer problem

Jurisdiction and institutional control

A registry's local legal or governance dispute can affect processes used by networks across borders. Your service footprint may be global while a critical decision remains concentrated in one institution.

Changing policies and administrative dependency

Transfer procedures, service terms and resource recognition can change. When your organisation holds the resources directly, your team must manage that relationship alongside its day-to-day network responsibilities.

Routing data and authorisations

Changes to records, route objects or certificates can affect how other networks evaluate your routes. Registration and reachability are separate, but inaccurate or unavailable supporting information can still create operational work. Our BGP, IRR and RPKI guide explains the practical connection.

The cost of renumbering

Addresses can be embedded in customer allowlists, VPNs, partner systems and monitoring. An urgent replacement may require coordination well beyond your own team. The real cost includes customer time, support load and confidence in your service.

Responsibility spread across intermediaries

A marketplace, broker, resource holder and connectivity provider can each perform a useful task. But a longer chain does not create stronger registry-side rights. For continuity, you need to know who stands behind the supply and owns the customer relationship.

LARUS puts continuity behind your address supply

Build with Unlimited IPv4 and a first-party partner focused on keeping your business connected. LARUS brings the documented statutory shareholder-rights foundation, resource operations and a Continuity offer into one commercial relationship. Your team can focus on growing the network instead of making an address acquisition its own upstream risk project.

The practical benefits start with your business: keep block-acquisition capital available for expansion, obtain capacity through the operating partner behind the supply, and choose the support and renewal commitment your services need.

Capacity, Production, Enterprise and Critical plans give that decision a clear shape. Critical includes Guaranteed Renewal. For customer-facing infrastructure, continuity belongs in the offer you choose from the start.

This is the distinction Lu Heng develops in his explanation of the broker question: the important commercial difference is the party carrying the upstream responsibility. LARUS is built around that first-party role.

Protect the records and the running network

The internet needs unique addresses, accurate records and dependable authorisation information. Those functions should survive the failure or replacement of an institution. Protecting an existing registry's authority is not the same objective as protecting the networks that use its records.

Lu Heng's registry continuity argument separates those objectives. It puts the running network and portable, verifiable records at the centre of reform.

• Preserve uniqueness: prevent conflicting recognition of the same resources.
• Keep records accurate and portable: a change of coordinator should not erase the holder's history.
• Protect service through disputes: avoid making customers collateral damage in institutional conflict.
• Separate coordination from expanding control: maintaining a register should not become a claim to govern every use of a network.
• Make critical functions auditable and replaceable: continuity should not depend on one organisation remaining indispensable.

Distributed registration and the case for stronger ownership

Lu Heng's decentralised registration proposal goes beyond copying a database. It argues for verifiable resource ownership and distributed coordination so that an institution cannot remain the sole gatekeeper of recognition.

That is a proposed reform. Implementing it involves real routing, authorisation and migration work as well as record integrity. A stored ledger alone does not keep ROAs valid or routes reachable. The destination is stronger holder rights and resilient network operation together.

Choose continuity before your next capacity decision

Start with what your customers need to keep: the API endpoints, services and network identity they trust. Then compare the operating relationship behind each offer.

• Who supplies and operates the resources behind the listing?
• What documented rights foundation supports that supply?
• Who handles the upstream relationship while your team serves customers?
• What support and renewal commitment fits the business?
• How much capital could you keep available by leasing instead of acquiring blocks?

LARUS brings those questions into one Continuity conversation. For a business that takes its network seriously, the address strategy should be as dependable as the service you intend to sell.

Frequently asked questions

What is the registry layer in internet governance?

It is the system of organisations, records and services used to coordinate number resources. It supports verification and uniqueness, while network operators and routing protocols provide actual connectivity.

Do organisations legally own their IP addresses?

The answer depends on the resource history, agreements and applicable law. Registry terminology is not a universal property ruling. For the business, the key question is whether its rights and operating relationship support continued service.

Does an RIR own the addresses it registers?

Recording resources does not itself establish ownership of every address. Coordination, institutional powers and the holder's rights must be distinguished.

Does registry status determine where an address can be routed?

It is one part of the operating picture. BGP, connectivity and authorisation records matter too. Keep those layers aligned so your customers can reach the service.

Why can registry governance create operational risk?

It concentrates influence over recognition and related services outside the operator's business. A dispute or administrative change can create work and uncertainty for networks that depend on those services.

What does the AFRINIC situation show?

It makes the dependency tangible: a registry's corporate and court processes matter to global resource holders. LARUS addresses that issue through its documented foundation and first-party continuity role, rather than asking customers to ignore it.

Could distributed ledger technology replace RIRs?

Lu Heng proposes distributed registration with stronger ownership and portable records. The aim is to preserve coordination without making an institution irreplaceable. Turning that proposal into an operating system also requires dependable authorisation and routing transitions.

What is the difference between registry state and operational use?

Registry state records recognition and resource information. Operational use means running services on reachable addresses. A continuity offer needs to connect both to the customer's outcome.

What should businesses do about registry-layer risk?

Make continuity part of the capacity decision. Compare the rights foundation, first-party operating responsibility and renewal commitment—not only the price of the block. LARUS brings those elements together with Unlimited IPv4.