IPv4 Transfer Process — Complete Step-by-Step Guide
The IPv4 transfer process involves transferring IP address ownership between organizations through their Regional Internet Registry (RIR). The process typically takes 1–4 weeks depending on the RIR. ipv4.center manages the entire transfer process end-to-end, handling contracts, due diligence, and RIR communication.
Transfer Timeline by RIR Region
Each Regional Internet Registry has its own transfer policies, timelines, and requirements
| RIR | Timeline | Key Requirements |
|---|---|---|
RIPE NCC | 1–2 weeks | LIR membership, Org ID, recent registration papers |
ARIN | 2–4 weeks | ARIN account, needs-based justification |
APNIC | 2–3 weeks | APNIC membership |
LACNIC | Intra: 3–5 weeks, Inter: 4–8 months | LACNIC membership |
AFRINIC | 3–5 weeks (intra-RIR only) | AFRINIC membership. No inter-RIR transfers available. |
Step-by-Step Transfer Process
How ipv4.center manages your IPv4 transfer from start to finish
Step 1: Due Diligence & Verification
The IPv4 block is screened for blacklist entries, BGP routing history, and ownership legitimacy through official RIR WHOIS records. Both buyer and seller undergo KYC verification.
Step 2: Buyer-Seller Agreement
Both parties agree on price, terms, and timeline. A legally binding purchase agreement is prepared and signed by both organizations.
Step 3: Escrow Payment
The buyer deposits funds into a secure escrow account. Payment is held until the RIR transfer is officially confirmed — protecting both parties.
Step 4: Transfer Agreement & Documentation
A Transfer Agreement is prepared and signed by both parties. Required documents include company registration papers, authorized signatory ID, and RIR membership details.
Step 5: RIR Transfer Submission
The transfer request is submitted to the relevant RIR. Our team manages all communication with the registry, handles any follow-up requests, and monitors processing status.
Step 6: Transfer Confirmation & Payment Release
Once the RIR confirms the transfer and updates the registration, escrow funds are released to the seller. The buyer gains full ownership of the IPv4 block.
Required Documents for IPv4 Transfer
Prepare these documents to ensure a smooth and fast transfer process
- Company registration certificate
- Government-issued ID
- Active RIR membership
- Proof of IPv4 address allocation
- Network justification plan
- Authorization letter
- Tax registration certificate
- Signed Transfer Agreement
Intra-RIR vs Inter-RIR Transfers
Understanding the two types of IPv4 address transfers and their differences
Intra-RIR Transfers
An intra-RIR transfer moves IPv4 addresses between two organizations registered with the same Regional Internet Registry. These are the most common and straightforward transfer type.
- Both parties are members of the same RIR
- Faster processing — typically 1–4 weeks
- Lower fees — only one registry involved
- Simpler documentation requirements
- Available across all five RIR regions
Inter-RIR Transfers
An inter-RIR transfer moves IPv4 addresses between organizations registered with different Regional Internet Registries. These require coordination between two registries and have additional complexity.
- Parties are members of different RIRs
- Longer processing — 2–8 months depending on regions
- Higher fees — both source and destination RIRs may charge
- More complex documentation across both registries
- Not available from AFRINIC (intra-RIR only)
Common Transfer Issues and How to Avoid Them
While most IPv4 transfers proceed smoothly when managed by an experienced broker, certain issues can cause delays or complications. Understanding these common pitfalls helps you prepare adequately and avoid unnecessary setbacks during your IPv4 transfer.
Incomplete documentation is the most frequent cause of transfer delays. Each RIR has specific requirements for company registration papers, authorized signatory identification, and membership credentials. For RIPE NCC transfers, company registration documents must be recent (within 3 months). ARIN requires needs-based justification for the receiving party. Ensuring all documents are current, properly formatted, and complete before submission significantly reduces processing time.
RIR membership issues can also stall transfers. Both buyer and seller must have active membership or sponsorship arrangements with the relevant RIR. If the buyer does not yet have an LIR account (RIPE) or Org ID (ARIN), this setup process must be completed before the transfer can begin. ipv4.center helps buyers establish the necessary RIR memberships as part of the transfer management process.
Address space disputes or holds occasionally affect transfers. If the IPv4 block has unresolved disputes, pending abuse complaints, or administrative holds placed by the RIR, the transfer cannot proceed until these are resolved. Comprehensive due diligence before committing to a purchase — including WHOIS verification, blacklist screening, and BGP history review — helps identify and avoid these issues entirely.
Frequently Asked Questions
Common questions about the IPv4 transfer process
IPv4 transfer timelines vary by RIR. RIPE NCC transfers are the fastest at 1–2 weeks (no transfer fee). ARIN transfers typically take 2–4 weeks due to needs-based justification requirements. APNIC averages 2–3 weeks. LACNIC intra-RIR transfers take 3–5 weeks, while inter-RIR transfers take 4–8 months. AFRINIC transfers take 3–5 weeks but are intra-RIR only — no inter-RIR transfers are available. ipv4.center proactively manages each step to minimize delays.
An intra-RIR transfer occurs between two organizations within the same Regional Internet Registry (e.g., RIPE to RIPE). An inter-RIR transfer moves IPv4 addresses between organizations in different RIR regions (e.g., ARIN to RIPE). Inter-RIR transfers involve coordination between both registries and may have additional requirements and longer processing times.
Yes, you generally need an active membership or sponsorship arrangement with the RIR where you want to hold the addresses. For RIPE NCC, you need an LIR account (or a sponsoring LIR). For ARIN, you need an Org ID and may need to demonstrate justified need. For APNIC, LACNIC, and AFRINIC, equivalent membership is required. ipv4.center can help you set up the necessary membership.
RIR transfer rejections are rare when proper documentation is provided. Common rejection reasons include incomplete paperwork, unresolved disputes on the address space, or failure to meet needs-based justification (ARIN). If a transfer is rejected, our team works with the RIR to resolve the issue. If the transfer cannot be completed, escrow funds are returned to the buyer in full.
Yes, inter-RIR transfers are supported between most RIR pairs. RIPE NCC, ARIN, and APNIC all support inter-RIR transfers. LACNIC supports inter-RIR transfers, though they take significantly longer (4–8 months vs 3–5 weeks for intra-RIR). AFRINIC supports intra-RIR transfers only — no inter-RIR transfers are available from AFRINIC. Inter-RIR transfers typically take longer than intra-RIR transfers and may involve fees from both the source and receiving registries.