LACNIC has announced it will start processing inter-RIR IPv4 Transfers.
LACNIC’s inter-RIR IPv4 transfer policy is compatible with APNIC’s inter-RIR IPv4 transfer policy. This means that APNIC can now begin processing IPv4 transfers between the APNIC and LACNIC regions. Please note that the new LACNIC policy does not allow for inter-RIR transfer of ASNs.
APNIC was the first RIR to implement an inter-RIR IPv4 transfer policy in 2011, and began IPv4 transfers with ARIN in 2012 after the ARIN community developed its inter-RIR IPv4 transfer policy.
In late 2015, the RIPE region also implemented an inter-RIR IPv4 transfer policy and the first IPv4 transfer between the APNIC and RIPE regions was processed in 2016.
Here’s a summary of the current inter-RIR transfer arrangements for quick reference, showing what resources are accepted for transfer between each RIR region based on community-developed policies:
| IPv4 | ASN | IPv6 | |
| APNIC | Yes | Yes | No |
| ARIN | Yes | Yes | No |
| RIPE NCC | Yes | Yes | Yes |
| LACNIC | Yes | No | No |
| AFRINIC | No | No | No |
Figure 1 – Comparison of Internet number resources accepted for inter-RIR transfer, by RIR policy
For more information about how to process inter-RIR transfers, visit the Transfer section of the APNIC website.
The views expressed by the authors of this blog are their own and do not necessarily reflect the views of APNIC. Please note a Code of Conduct applies to this blog.