IPv4 acquisition
Buy IPv4 address blocks with the transfer path in view
Search current IPv4 blocks, then assess registry eligibility, holder authority, reputation evidence, routing responsibilities, and commercial terms before you commit.
- Public search
- Filter current listings from /24 through /18
- Registry scope
- ARIN, RIPE NCC, APNIC, LACNIC and AFRINIC
- Marketplace role
- Workflow, administrative processing and registry-coordination support
Buyer due diligence
An address block is more than its price per IP
Use a listing to start the review. Verify the resource, counterparty, transfer path, and operating conditions independently before deciding that a block fits.
- Registry eligibility
- Confirm the current RIR, receiving organization, applicable transfer policy, and any membership or justification requirements.
- Holder authority
- Request evidence that the seller can initiate the transfer. i.lease does not warrant title, authority, or transferability.
- Reputation evidence
- Review dated checks, their sources and scope, and unresolved abuse history. A single “clean” label is not a substitute for your own review.
- Routing handover
- Agree who maintains ROAs, route objects, LOAs, rDNS, geolocation, and the routing change window after transfer.
- Commercial terms
- Separate the bid or buyout amount, fees, payment conditions, transfer costs, approval dependencies, and acceptance evidence.
Purchase workflow
Move from a network requirement to an accepted transfer
The buyer and seller transact directly. i.lease provides the marketplace workflow and administrative coordination; registry decisions and transaction outcomes are not guaranteed.
- 01
Define the requirement
Set the block size, target RIR, receiving organization, intended use, geography, timing, and routing model.
- 02
Review current listings
Compare availability, status, listed terms, registry path, and the evidence needed for your independent review.
- 03
Confirm the transaction
Complete account and compliance checks, agree the counterparty terms, and document payment and transfer conditions.
- 04
Verify and accept
Track the registry change, independently verify completion, and confirm the operational handover before settlement is released.
Ownership decision
Buy when long-term control justifies the transfer work
Buying can fit durable network capacity and ownership plans, but it also carries registry, due-diligence, routing, reputation, and lifecycle responsibilities.
Need capacity without acquiring the block?
Compare managed IPv4 leasing when your demand is temporary, phased, or better matched to an operating term.
Compare IPv4 leasingBuyer questions
What to confirm before buying IPv4 addresses
Requirements differ by resource, counterparty, and registry path. Treat these answers as a starting point and verify the facts for the transaction you are considering.
Do I need an RIR organization or Org ID to buy an IPv4 block?
The receiving-organization and justification requirements depend on the target RIR and transfer path. Confirm them before bidding; an account or listing alone does not establish eligibility.
Can an IPv4 block move between RIR regions?
Only when the source and recipient registry policies support the path, the resource is eligible, and both organizations meet the applicable requirements. Verify the specific inter-RIR route before relying on it.
How long does an IPv4 transfer take?
There is no guaranteed timeline. Documentation, counterparty response, compliance review, and RIR processing can all affect completion and approval.
Does i.lease verify ownership or guarantee a listing?
No. Public listings can change or close, and i.lease does not warrant ownership, title, authority, transferability, registry approval, pricing, or transaction success. Buyers must complete their own review.
Start with current IPv4 availability
Browse the public feed first. When a block fits your requirement, create a buyer account to continue the marketplace workflow.
