LACNIC IPv4 Transfer Guide
LACNIC manages IPv4 resources for Latin America and the Caribbean. This guide by IPv4Center.com covers the complete LACNIC transfer process, including intra-RIR and inter-RIR transfer policies.
Key Facts
Essential information about LACNIC IPv4 transfers at a glance.
LACNIC Transfer Policies
LACNIC governs IPv4 transfers through policies outlined in the LACNIC resource transfer policy. Understanding which type applies to your situation is the first step.
Intra-RIR Transfer (Within LACNIC)
- Transfer between two LACNIC members
- Both parties must be current LACNIC members in good standing
- Source must have held resources for at least 12 months
- Recipient must demonstrate need for the addresses
- Minimum transfer size is /24 (256 IPs)
Inter-RIR Transfer (Between Registries)
- Transfer between LACNIC and another RIR (RIPE, ARIN, APNIC)
- Both source and destination RIRs must approve
- Follows the more restrictive policy of the two RIRs
- Takes longer (4–8 weeks typically)
- Useful when buyer/seller are in different regions
LACNIC Transfer Process
Follow these steps to complete a LACNIC IPv4 transfer successfully.
Verify LACNIC Membership
Both parties must be active LACNIC members in good standing. If you are not yet a member, you can apply through the LACNIC member portal. Annual membership fees must be current.
Pre-Transfer Due Diligence
Conduct thorough verification of the IP block including blacklist checks, WHOIS verification, and BGP routing history review.
Negotiate Terms and Sign Agreement
Agree on pricing, payment terms, and timeline. A formal transfer agreement should be executed between buyer and seller, with escrow payment recommended for added security.
Submit Transfer Request to LACNIC
Both the source and recipient organizations submit the transfer request through the LACNIC system. The source organization initiates the process, and the recipient confirms acceptance.
LACNIC Review and Approval
LACNIC staff reviews the transfer request to verify compliance with transfer policies. They check membership status, holding period requirements, and the recipient's justification for the resources.
Resource Update and Completion
Once approved, LACNIC updates the WHOIS records to reflect the new holder. The recipient can then configure RPKI/ROA records and begin announcing the block via BGP.
Required Documents
Prepare these documents before initiating a LACNIC transfer to avoid delays.
- Active LACNIC membership for both buyer and seller
- Legal entity registration documents (certificate of incorporation or equivalent)
- Government-issued ID of authorized representatives
- Network utilization plan (justification for resource need)
- Signed transfer agreement between both parties
- Authorization letter from the organization's legal representative
- Proof that source has held resources for at least 12 months
Eligibility Requirements
Key requirements that must be met for a LACNIC IPv4 transfer.
Active LACNIC Membership
Both the transferring and receiving organizations must be active LACNIC members with all fees paid and in good standing. New members can apply but should factor application time into the transfer timeline.
12-Month Holding Period
The source organization must have held the IPv4 resources for at least 12 months before initiating a transfer. This prevents rapid flipping of resources and ensures legitimate use history.
Resource Justification
The receiving organization must demonstrate justified need for the IPv4 addresses. This includes a network utilization plan showing how the addresses will be deployed within a reasonable timeframe.
No Outstanding Obligations
Neither party can have outstanding debts or unresolved policy violations with LACNIC. All membership fees and any applicable transfer fees must be current.
LACNIC vs Other RIRs
How LACNIC transfer policies compare to RIPE NCC and ARIN. See also our RIPE transfer and ARIN transfer guides.
| Feature | LACNIC | RIPE NCC | ARIN |
|---|---|---|---|
| Needs Justification | Required | Not required | Required (8.3) |
| Holding Period | 12 months | None (24-month lock) | None |
| Timeline | 2–6 weeks | 1–2 weeks | 2–4 weeks |
| Inter-RIR Transfers | Supported | Supported | Policy 8.4 |
| Minimum Size | /24 | /24 | /24 |
| Membership Required | Yes, both parties | Yes (LIR status) | Org ID required |
Frequently Asked Questions
Common questions about LACNIC IPv4 transfers.
How long does a LACNIC IPv4 transfer take?
What is the minimum block size for LACNIC transfers?
Can I transfer IPv4 from RIPE to LACNIC?
What is the 12-month holding period?
Does LACNIC require a needs justification?
Does IPv4Center.com handle LACNIC transfers?
Ready for a LACNIC Transfer?
IPv4Center.com handles the entire LACNIC transfer process — from documentation and justification to WHOIS updates. Whether you're buying or selling LACNIC IPv4 resources, we make it seamless.