IPv4 has reached its limit. RIPE NCC exhausted its last /22 allocation back in 2019. ARIN expired in 2015, APNIC in 2011. And yet, in 2026, demand for IPv4 continues to grow—cloud deployments, IoT, legacy enterprise systems that can't migrate to IPv6 overnight. Too much has been built specifically for IPv4.
We work with IPv4 transfer as part of our infrastructure business, and the process is much more complex than most people expect. Here's what I wish someone had explained to me earlier before starting work.
How IPv4 Transfer Actually Works
An IPv4 broker acts as an intermediary between the seller (the organization with unused addresses) and the buyer (who needs them). In the RIPE NCC region, which covers Europe, the Middle East, and Central Asia, the process is as follows:
1. Due Diligence
The broker verifies that the seller actually owns the rights to the address block. There are no liens, disputes, or pending transactions. Even at this stage, unexpected issues can be uncovered—I've seen addresses that looked perfect on paper, but were accompanied by old violation reports that required prior resolution.
2. Needs Assessment
The buyer must demonstrate a legitimate need for the addresses within 24 months. This is not a formality—the RIPE NCC evaluates each request. You need documentation supporting your infrastructure development plans and justifying the need for the specific block size.
3. Rights Transfer Request
Both parties submit rights transfer requests through the RIPE NCC portal. The broker coordinates and processes the paperwork. If you've never used the RIPE NCC portal before, expect some back-and-forth—the interface is functional, but not entirely user-friendly.
4. Processing
The RIPE NCC verifies all data, confirms the identity of both parties, and processes the transfer. Typically, it takes 2-6 weeks. It can take longer if there are questions about the needs assessment.
5. Payment
Funds are typically held in an escrow account until the transfer is completed. This protects both parties—the seller doesn't release the block without receiving payment, and the buyer doesn't pay for something the RIPE NCC might reject.
What developers and system administrators should know
Here are some practical details that are rarely covered in the documentation:
Minimum address size to transfer: /24 (256 addresses) in most regions. You can't simply buy a handful of individual IPs.
Pricing in 2026: Expect $35–52 per IP for a clean /24 block, so roughly $9,000–$15,000 total. Cheaper blocks exist ($15–26 per IP), but they often come with reputation baggage. Prices vary by region-APNIC (Asia) tends to be more expensive than ARIN (US) or RIPE (Europe)-and by block size: smaller blocks (/24) paradoxically cost more per address than larger ones (/16) because they're easier to deploy. After a spike in 2021–2022 and a correction in 2024–2025, the market is volatile. IPv4 addresses have effectively become a tradable asset.
RIPE NCC Membership: You must be a member or sponsored by one. If your organization is not a member, this adds steps, time, and additional costs.
ROA Records: If RPKI/ROA records are configured in the block, they must be updated during the transfer. Do not skip this step, otherwise you will experience routing issues.
BGP Announcements: Schedule a time for the routing update after the transfer is complete. An announcement before the transfer is complete may cause problems.
Pitfalls Our Brokers Have Encountered
Unclean Blocks
Some blocks carry "baggage"-old spam reports, abuse listings in Spamhaus or UCEPROTECT. A good broker verifies the block's reputation before finalizing the transfer. I always check a block against the major blacklists before confirming it. Resolving someone else's reputation issues is not something you want to be doing in the first month of using a new IP address range.
Documentation Delays
The RIPE NCC requires specific documentation, and missing even one can delay a transfer for weeks. Your broker should handle this, but it's worth double-checking that everything is complete before submitting your request.
Post-Transfer Routing
After the transfer is complete, BGP advertisements, RPKI/ROA records, and possibly IRR objects need to be updated. Plan for this in advance. I've seen cases where availability issues arose after the transfer was completed due to improper coordination of routing updates.
Sometimes address errors or unverified blocks led to the deal being abandoned, even though significant time had already been invested in the transaction.
Address Allocations Before Regional Internet Registries (RIRs)
Pre-RIR address allocations—space allocated before the advent of Regional Internet Registries—may have additional transfer conditions. These older blocks sometimes require additional verification steps.
IPv6 Reality
Despite IPv6 adoption reaching ~50% globally, most production workloads still require IPv4. Dual-stack remains the norm. I don't see significant changes in the next 3-5 years, meaning IPv4 brokerage services will remain relevant during this period.
If you're building infrastructure and need addresses now, waiting for IPv6 to be implemented isn't the best strategy. The secondary market through a reputable broker is often the only realistic option.
Key Takeaways
- Use a broker that understands the processes of your specific RIR (RIPE NCC, ARIN, APNIC)
- Always check the block's reputation before purchasing
- Budget 2-8 weeks for the transfer process
- Schedule a routing update before the transfer is completed
- Check your RIPE NCC membership status early in the process
Working with a reputable provider that regularly processes transfers can save significant time and avoid costly mistakes.
The author works with IPv4 transfers and infrastructure hosting. Feel free to reach out with questions about the transfer process.
Top comments (0)