Inter-RIR IPv4 Transfers

An inter-RIR transfer moves address space from one Regional Internet Registry's region to another's. Since 2012, the registries have published 6,568 of them, moving 106,391,552 IPv4 addresses. The largest corridor is ARIN to RIPE NCC with 50.0M addresses.

Inter-RIR transfers, all time
6,568
since 2012-10-08
IPv4 addresses, all time
106.4M
106,391,552
Inter-RIR, last 12 months
1,330
16.0M IPv4 addresses
Latest inter-RIR transfer
2026-10-08

Inter-RIR Transfer Matrix, All Time

IPv4 addresses moved from the registry in the row to the registry in the column.

IPv4 addresses transferred between Regional Internet Registries
From ↓ / To →RIPE NCCARINAPNICLACNICAFRINIC
RIPE NCC-
12.3M
736 transfers
3.8M
339 transfers
37K
49 transfers
0
ARIN
50.0M
2,390 transfers
-
23.5M
895 transfers
266K
50 transfers
0
APNIC
4.5M
977 transfers
2.5M
539 transfers
-
23K
26 transfers
0
LACNIC
1.7M
77 transfers
7.7M
480 transfers
191K
10 transfers
-0
AFRINIC0000-

Inter-RIR Transfer Matrix, Last 12 Months

IPv4 addresses transferred between Regional Internet Registries
From ↓ / To →RIPE NCCARINAPNICLACNICAFRINIC
RIPE NCC-
1.7M
56 transfers
727K
63 transfers
19K
26 transfers
0
ARIN
8.7M
887 transfers
-
2.8M
183 transfers
76K
8 transfers
0
APNIC
319K
59 transfers
50K
24 transfers
-
512
1 transfers
0
LACNIC
987K
14 transfers
459K
7 transfers
131K
2 transfers
-0
AFRINIC0000-

Net IPv4 Flow per Registry

IPv4 addresses received from other registries minus addresses sent to them, all time.

Net inter-RIR IPv4 flow per registry
RegistryReceivedSentNet
RIPE NCC56,102,14416,156,416+39,945,728
APNIC27,525,8886,946,816+20,579,072
AFRINIC000
LACNIC325,1209,518,336-9,193,216
ARIN22,438,40073,769,984-51,331,584

Inter-RIR Transfers per Year

Inter-RIR transfers and IPv4 addresses per year
YearTransfersIPv4 addressesLargest corridor
20261,12112,950,784ARIN to RIPE NCC (6.1M)
20251,42520,942,848ARIN to RIPE NCC (10.4M)
202480414,418,944ARIN to RIPE NCC (7.9M)
202354611,066,880ARIN to RIPE NCC (7.7M)
202247710,688,256ARIN to RIPE NCC (6.4M)
20216403,225,344ARIN to RIPE NCC (1.9M)
20203182,348,800ARIN to APNIC (906K)
20193123,597,824ARIN to APNIC (1.5M)
20183019,492,992ARIN to APNIC (6.6M)
20172153,707,136ARIN to RIPE NCC (1.6M)
20161995,297,152ARIN to APNIC (3.4M)
2015917,007,744ARIN to APNIC (3.8M)
2014941,101,824ARIN to APNIC (1.1M)
201317542,720ARIN to APNIC (543K)
201282,304ARIN to APNIC (2,304)

Latest Inter-RIR Transfers

Frequently Asked Questions

What is an inter-RIR transfer?
A transfer of IPv4 addresses (or AS numbers) from an organisation in one Regional Internet Registry's service region to an organisation in another, for example from ARIN to RIPE NCC. The registration moves to the receiving registry, and both registries publish the transfer in their transfer logs.
Which registries allow inter-RIR transfers?
An inter-RIR transfer needs compatible transfer policies in both registries. ARIN, APNIC, LACNIC and RIPE NCC have such policies. The matrix on this page shows which registry pairs have actually exchanged address space.
How are inter-RIR transfers counted here?
Each transfer is counted once, even though it appears in the logs of both the source and the receiving registry. IPv4 volume is the number of addresses in the transferred blocks; IPv6 and ASN transfers count as transfers but add no IPv4 addresses.
Why does net flow matter?
Net flow shows whether a region has, on balance, received IPv4 address space from other regions or given it away. A positive net flow means organisations in that registry's region received more addresses through inter-RIR transfers than they sent.