Top challenges IP brokers face in the IPv4 market

A hosting company needs IPv4 addresses for a new service. Another organisation has a block it no longer uses. A broker can bring them together. But finding a counterparty is only the beginning: the buyer needs addresses that can enter service and remain usable, while the seller needs a clear handover.

The difficult work sits between an attractive listing and a functioning network. Five questions help explain what an IP broker actually has to solve.

Who can make this transaction happen?

An IPv4 block is a group of addresses. The people offering it, the organisation recorded as its holder and the people authorised to act for that organisation need to be understood together. A familiar company name or a document on its own does not settle those relationships.

A useful broker connects the evidence: the specific block, current registration records, the parties involved and their authority to proceed. It also distinguishes a transfer, which changes the registered holder through the applicable process, from a lease, which arranges use for a period.

Intermediation is a service, not a universal requirement. For example, ARIN explicitly says organisations do not have to use a qualified facilitator for a transfer. The reason to employ one is the work it can do.

Are the offers actually comparable?

Two quotes for the same number of addresses may describe different arrangements. One may concern a transfer; another a monthly lease. Fees, expected timing, technical support and responsibility after handover can also differ. A price per address hides those differences unless the broker makes them visible.

Consider a service that must launch soon. A cheaper quote is not necessarily useful if nobody has established when the addresses can be deployed. Compare the whole arrangement against the service you need to run, rather than treating a headline price as the answer.

Who coordinates the registry process?

Regional Internet Registries maintain number-resource records and provide related services. Their transfer procedures are part of the environment in which a transaction takes place. They should not be confused with a broker’s commercial offer or treated as a promise that an application will succeed.

The broker’s practical task is to establish the applicable process, assemble accurate information and make responsibilities clear between the parties. ARIN and the RIPE NCC publish their own transfer information. An arrangement involving more than one registry needs attention to both sides.

Will the addresses work for this service?

A registration change and a working route are different milestones. Someone must coordinate who announces the block, update the relevant records and test access from the networks that matter to the customer.

Past use matters too. An email operator will investigate delivery and relevant blocklists; a hosting company will test its customers’ access paths. No single reputation score answers every operational question. The handover should leave an operator able to investigate a problem, not merely holding a spreadsheet.

What happens after the deal closes?

Imagine a registration question arises after customers have started using the addresses. Who responds? Who understands the history? Who can coordinate the technical work while the matter is resolved? This is where a broker’s advertised support becomes something that can be examined.

Lu Heng’s Note 66 puts this challenge at the centre of the market. His argument is that ordinary matching and paperwork leave the deeper problem untouched: a network can remain exposed to discretionary power at the registry layer after payment and transfer.

In that argument, an intermediary earns its place by carrying work and sustaining continuity under pressure. A reader assessing a service can ask for a concrete account of who does that work and how it continues when an arrangement changes.

A bridge that leaves people able to act

The immediate task is to make an operating arrangement dependable. The larger design question is why the network’s continuity should depend on an administrator that its operator cannot readily replace. Lu Heng develops his proposed alternative—coordination with portability, continuity and meaningful exit—in Note 72.

That question becomes harder to address after addresses have spread through customer systems, access rules and business processes. Examine the dependencies while the choices are still open. A useful broker helps people cross that gap and remain capable of running their networks on the other side.