IP broker: the short answer
An IP broker helps a buyer discover IPv4 supply, compare counterparties, coordinate evidence, and move a proposed transaction through the applicable registry and operating checks. A broker can reduce search and coordination work, but it cannot approve an RIR transfer, create a routing authorization, make every network accept a prefix, or guarantee that an address block will stay free of reputation issues.
Buying IPv4 is a chain of separate decisions: define the required prefix, verify who can transfer it, satisfy the source and recipient RIR path, agree commercial terms, prepare routing and records, and test the handover. Use the broker as a coordinator whose scope is written down, then verify the exact block and every material claim independently.
| Broker activity | Useful output | What it does not prove |
|---|---|---|
| Discover supply | Candidate prefixes, seller contacts, indicative availability, and a comparison of stated terms | That a listing is reserved, transferable, or suitable for the buyer's workload |
| Coordinate the RIR path | A checklist of source, recipient, account, identity, and transfer documents | That the applicable RIR will approve the request or that a policy from another region applies |
| Organize due diligence | Dated RDAP, BGP, RPKI, IRR, DNS, reputation, and abuse evidence for the exact prefix | That a score is a permanent “clean IP” verdict or that every network will accept the block |
| Support closing and handover | Milestones for payment, registry update, route activation, contacts, and operational ownership | That the broker controls the RPKI key, origin ASN, upstream filters, DNS, or the buyer's application |
What is an IP broker?
An IP broker is an intermediary for a commercial transaction involving internet number resources. In an IPv4 purchase, the broker may connect a buyer with a resource holder, explain the proposed transfer route, collect documents, coordinate a contract or escrow workflow, and help schedule the technical handover. The exact service varies, so the engagement should identify the broker's legal entity, fee basis, conflicts, included work, exclusions, and post-closing support.
The broker is not the RIR, seller, escrow provider, legal adviser, routing operator, or reputation database. Those roles can overlap in one engagement, but they create different evidence and responsibilities. A broker's description of a prefix is an input to diligence, not a replacement for the registry record, the signed agreement, or the buyer's acceptance tests.
Broker, RIR, seller, and network operator roles
| Party or system | Primary responsibility | Question for the buyer |
|---|---|---|
| Resource holder or seller | Offers the resource and provides evidence of authority, condition, and transaction terms | Who is the registered holder, who is authorized to sign, and what exactly is being transferred? |
| IP broker | Finds or coordinates counterparties, documents, negotiation, and agreed milestones | Which tasks are included, what is the fee, and what happens if the transfer is rejected or delayed? |
| Regional Internet Registry | Applies its current policy and records an approved allocation, assignment, or transfer | Which RIR path applies, and which source and recipient requirements must be met? |
| Escrow or payment provider | Holds or transfers funds under the agreed conditions | Which event releases funds, who handles a dispute, and which fees or taxes are separate? |
| Network operator or upstream | Evaluates and accepts route, origin, filtering, and operational requests | Will the intended ASN, prefix length, ROA, IRR object, and abuse contacts pass the actual provider's checks? |
How to use an IP broker to buy IPv4
- Define the requirement. Write down the prefix size, usable capacity, RIR region, intended workload, deployment location, origin ASN, upstreams, start date, timeline, budget, and whether leasing or an existing provider assignment could solve the need.
- Confirm the transfer path. Identify the source and recipient RIR, whether the transaction is intra-RIR or inter-RIR, the organization or account requirements, and the person authorized to submit documents. A broker's route summary should be checked against the current RIR policy.
- Evaluate the broker. Verify the legal entity, jurisdiction, named contacts, fee unit, deposit or escrow treatment, conflicts, complaint path, references that can be verified, and the exact activities covered after the registry approves the transfer.
- Inspect the exact prefix. Ask for the CIDR, authoritative RDAP or WHOIS record, transfer history where available, route visibility, origin ASN, IRR object, RPKI ROA, reverse DNS, geofeed or correction path, abuse contact, and dated reputation observations.
- Negotiate conditional terms. Put the exact prefix, parties, price, currency, fees, taxes, milestones, evidence, rejection or delay outcome, replacement, refund, confidentiality, and responsibility for routing and records into the agreement.
- Close against evidence. Tie payment and acceptance to the agreed registry and handover milestones. Confirm that registry records, routing authorizations, DNS, contacts, monitoring, and application tests are updated in the intended order.
- Operate and exit. Keep the transfer file, renewal or support terms, abuse escalation, reputation baseline, route owner, RPKI and IRR owners, and a renumbering or withdrawal plan. A completed transfer does not remove ongoing operational work.
For a case-specific request, start with the IPv4 purchase workflow. If the need is temporary or uncertain, compare managed IPv4 leasing before committing capital.
What to verify before paying an IP broker
| Area | Request and record | Boundary |
|---|---|---|
| Authority | Registered holder, authorized signatory, exact CIDR, contractual chain, and disclosed disputes or encumbrances | A commercial invoice alone does not prove that the signer can transfer the resource |
| Registry | Current RIR policy, source and recipient eligibility, account requirements, agreements, and approval status | A broker cannot substitute for the RIR's review or guarantee an approval date |
| Routing | Origin ASN, upstream acceptance, LOA where required, IRR route object, ROA prefix and maxLength, and activation order | A route or ROA does not by itself prove ownership, contractual authority, or end-to-end reachability |
| Records | Reverse DNS control, registry contacts, geofeed or correction process, and named operational owners | One database's result does not force every resolver, geolocation provider, or filter to update |
| Reputation | Dated, source-specific mail, fraud, blocklist, geolocation, reachability, and application observations | “Clean” is not a permanent property and cannot guarantee acceptance by every recipient |
| Commercial exit | Broker fee, escrow, taxes, refund rules, replacement, support, dispute handling, and post-transfer obligations | The lowest headline price may exclude routing, legal, registry, monitoring, or renumbering work |
How much does an IP broker cost?
There is no universal IP broker fee. A broker may charge a percentage of the transaction, a fixed coordination fee, a buyer-side or seller-side fee, a minimum amount, or a combination of these. Ask whether the fee is based on the block total, the per-address quote, the completed transfer, or an earlier milestone. Record currency, tax, escrow, registry, legal, and technical costs separately.
Compare the complete cost over the same horizon: total acquisition cost = resource price + broker and escrow fees + registry and legal work + routing and record setup + migration and operating work. Do not treat a broker estimate, an asking price, or one marketplace sample as a completed-sale benchmark. The exact CIDR, RIR path, eligibility, payment terms, and handover risk change the comparison.
Should you use an IP broker?
A broker may be useful when the buyer needs help finding counterparties, coordinating several organizations, or assembling evidence for a complex transfer. Direct contact may fit an organization that already knows the resource holder, understands the applicable RIR policy, and can own the contract, registry, routing, and technical handover itself. Leasing may fit temporary capacity or a requirement that is not yet stable enough to justify a transfer.
Choose the path that gives the team a named owner for authority, routing, RPKI, IRR, DNS, reputation, abuse handling, renewal, and exit. The purchase decision is complete only when those responsibilities are explicit.
IPv4 IP broker FAQs
What does an IP broker do?
An IP broker can discover candidate IPv4 supply, introduce counterparties, coordinate documents and negotiation, and help organize registry and technical milestones. The engagement determines the actual scope.
Can an IP broker approve an IPv4 transfer?
No. The applicable RIR applies its policy and records an approved transfer. A broker can coordinate the request and explain the documented path, but cannot replace the registry decision.
Is there a universal certification for IPv4 brokers?
No. RIR programs, lists, and transfer procedures differ by region and can change. Verify the exact current program and its limits with the relevant RIR instead of treating a badge or marketing label as approval.
How do I choose an IPv4 broker?
Check the legal entity, named contacts, fee and escrow terms, conflicts, verifiable transaction experience, evidence standards, complaint path, and post-transfer scope. Require the broker to state what it cannot guarantee.
How long does an IPv4 broker transaction take?
Timing depends on supply, buyer and seller readiness, RIR eligibility, documentation, agreements, payment, and routing handover. A broker should provide milestones and dependencies, not an unconditional completion promise.
What should I verify before paying for an IPv4 block?
Verify the exact CIDR and holder authority, the RIR path and approval conditions, the contract and escrow, routing and RPKI evidence, DNS and abuse ownership, dated reputation observations, and the refund or replacement outcome if a milestone fails.
Does an IP broker guarantee a clean or globally routable block?
No. Reputation and reachability vary by source, time, network, application, and policy. Treat them as acceptance criteria with evidence and remediation owners, not as a permanent guarantee.
Should I lease IPv4 instead of buying through a broker?
Compare the planning horizon, capital, registry control, renewal risk, routing responsibilities, reputation work, and exit plan. Leasing can fit temporary or variable capacity; buying can fit an eligible long-term requirement.
