Introduction
IPv4 addresses are running out. That’s not news anymore—it’s just the reality we operate in. And as the free pool dries up, organizations are flocking to the secondary market to get the blocks they need. But here’s where things get tricky: moving IPv4 addresses across different Regional Internet Registries isn’t straightforward. Not even close. The compliance requirements can snag you at multiple points. I’ve seen transfers get rejected over paperwork inconsistencies. Financial penalties pop up. In worst-case scenarios, addressing rights get revoked entirely. This piece walks through the compliance landscape for inter-RIR IPv4 transfers—what network engineers, IT managers, and ISP operators actually need to know to get through the process without losing weeks (or money).
Understanding Regional Internet Registries (RIRs)
Five RIRs handle IPv4 allocation and transfer policies worldwide. You probably know the names, but here they are anyway:
Need IPv4 addresses?
Browse clean, RIPE-verified subnets at $0.50/IP/month.
- ARIN (American Registry for Internet Numbers) – North America.
- RIPE NCC (Réseaux IP Européens Network Coordination Centre) – Europe, Middle East, parts of Central Asia.
- APNIC (Asia Pacific Network Information Centre) – Asia-Pacific.
- LACNIC (Latin American and Caribbean Internet Addresses Registry) – Latin America and the Caribbean.
- AFRINIC (African Network Information Centre) – Africa.
All five follow a common framework set by ICANN (Internet Corporation for Assigned Names and Numbers). But—and this matters—each region interprets things differently. The specific requirements vary more than you’d expect.
Key Compliance Requirements for Cross-Region Transfers
Justification and Needs Assessment
Most RIRs want the transferee (the buyer) to show they actually need the block. Makes sense, but the paperwork can be tedious. Typically you’re looking at:
- Documentation of current IP utilization—usually above 80%.
- A 24-month growth forecast that demonstrates future demand.
- Evidence that you can’t get the addresses from the RIR’s free pool (assuming anything remains there at all).
The transferor (seller) doesn’t get off easy either. They have to prove they no longer need the addresses. ARIN wants a formal “no-need” attestation. RIPE NCC is a bit more flexible—they’ll accept a declaration that the block is surplus. Different strokes.
Transfer Restrictions and Lock-In Periods
RIRs impose waiting periods to stop speculative flipping. The restrictions vary:
- ARIN: 12-month lock after receiving a transferred block. The seller must have held it for at least 12 months too.
- RIPE NCC: No explicit lock-in for inter-RIR transfers, but the block can’t be transferred again for 12 months after registration.
- APNIC: 12-month hold for both sides.
- LACNIC: 12-month lock for the buyer; seller needs 12 months of holding history.
- AFRINIC: Moratorium on inter-RIR transfers right now. Intra-region transfers still work under tight conditions.
Note: These periods apply to the same block. And “lock” doesn’t always mean the same thing—some RIRs prohibit any further transfer, others just block return to the RIR. Read the fine print.
Documentation and Legal Agreements
Every inter-RIR transfer needs a signed Transfer Agreement between buyer and seller. That’s the baseline. You’ll also likely need:
- Proof of company registration and signatory authorization.
- Utilization reports from the buyer.
- No-objection letters from both RIRs (when required).
- Legacy vs. non-legacy status clarification—legacy addresses (allocated before the RIR system existed) often have looser requirements.
ARIN processes transfers through its Transactional or Specified Transfer mechanism. RIPE NCC uses a “Transfer of Resources” procedure. All of them charge administrative fees. Budget for those upfront.
Regional Nuances and Pitfalls
The table below covers the high-level differences. But a few nuances deserve special attention because they trip up even people who’ve done this before.
| RIR | Inter-RIR Allowed? | Typical Processing Time | Key Nuance |
|---|---|---|---|
| ARIN | Yes | 2–4 weeks | Both parties need to be ARIN members or have an ARIN RSA. |
| RIPE NCC | Yes | 1–3 weeks | No membership required for buyers from other regions, but a RIPE NCC service agreement must be signed. |
| APNIC | Yes | 3–6 weeks | Buyer must show “justified need” with a detailed 24-month plan; APNIC audits utilization after transfer. |
| LACNIC | Yes | 2–5 weeks | Transfers from outside LACNIC fall under a “regional preference” rule—local buyers get priority. |
| AFRINIC | Currently Suspended | N/A | Moratorium tied to address exhaustion concerns; intra-region transfers need strict justification. |
One thing that catches people off guard: RIPE NCC’s “run-off” rule. If a block was previously used in another region, the buyer has to prove those addresses weren’t part of a hijacked or fraudulent allocation. ARIN does something similar with a “due diligence” check on the seller’s ownership history. Don’t assume clean title—verify it.
Best Practices for Smooth Transfers
A few things I’d recommend based on how these transfers actually play out:
- Pre-qualify the seller. Check their RIR membership, address history, any liens or disputes. Do this before you sign anything.
- Use a professional escrow service. Many RIRs want payment and transfer synchronized. Escrow protects both sides.
- Prepare documentation early. Utilization reports, incorporation documents, signatory authorizations—get them ready before you initiate the transfer.
- Engage with both RIRs at the same time. Inter-RIR transfers need parallel processing. A delay in one region stalls everything.
- Consider a specialized broker. Someone with multi-RIR experience handles paperwork, talks to the RIRs, and flags problems before they become deal-breakers.
How IP4 Market Ensures Compliance
IP4 Market (ip4.market) handles IPv4 transactions across regions, and compliance is baked into how the platform works. Every seller goes through verified ownership checks and compliance pre-screening—we make sure the blocks are clean and actually transferable before they’re listed. Our team tracks policy changes across ARIN, RIPE NCC, APNIC, LACNIC, and AFRINIC closely. What we provide:
- Documentation templates tailored to each RIR’s requirements.
- Integrated escrow and payment processing.
- Real-time status tracking for multi-RIR transfers.
- Access to compliance specialists who’ve handled these transactions before.
The goal is straightforward: reduce rejection risk and cut down your transfer timeline while keeping everything within regulatory bounds.
Frequently Asked Questions
Q: Can I transfer IPv4 addresses from ARIN to RIPE NCC directly?
A: Yes. ARIN and RIPE NCC have a bilateral inter-RIR transfer agreement in place. Both RIRs need to approve the request.
Q: What happens if the transfer is rejected by one RIR?
A: The whole transaction falls through. Fees paid to the transferring RIR may not be refundable. Pre-verify compliance with both RIRs before you sign a contract.
Q: Are legacy address blocks subject to the same rules?
A: Not always. Legacy blocks (pre-RIR allocations) often have more lenient transfer policies. But they require extra due diligence to confirm ownership and rule out prior fraudulent use.
Q: How long does a typical inter-RIR transfer take?
A: From agreement to final registration, expect 4–8 weeks. It depends on which RIRs are involved and how complete your documentation is.
Conclusion
Compliance in cross-region IPv4 transfers isn’t optional. You can’t shortcut it. Understanding what each RIR wants in terms of justification, lock-in periods, and documentation—that’s what separates transfers that close from transfers that collapse. Follow the best practices. Use experienced partners. The IPv4 market isn’t getting any simpler, and the organizations that move efficiently will be the ones that get the addresses they need without unnecessary headaches.
