Skip to content
Guide Transfer • •

How Inter-RIR Transfers Work (2026): Step-by-Step Process

Five phases from the eligibility check to the new ROAs, with what the RIPE NCC, ARIN, APNIC and LACNIC each ask of the source and of the recipient.

An inter-RIR transfer moves IPv4 addresses, and between the RIPE NCC, ARIN and APNIC also ASNs, from one Regional Internet Registry to another. The request always starts at the source RIR. Once the source RIR approves, the destination RIR checks the recipient and both registries update their records on an agreed date. LACNIC takes part for IPv4 only, and AFRINIC allows no inter-RIR transfer in either direction.

What is an Inter-RIR Transfer?

An inter-RIR transfer is the movement of Internet number resources (primarily IPv4 addresses and ASNs) from one Regional Internet Registry's service region to another. Unlike intra-RIR transfers that occur within a single RIR's region, inter-RIR transfers involve coordination between two separate registries, each with its own rules.

Moving an ASN or a PI block to another LIR inside the RIPE region is not an inter-RIR transfer: for that, see change your sponsoring LIR.

Key characteristics of inter-RIR transfers:

  • Requires approval from both the source and destination RIRs
  • Must comply with reciprocal, compatible policies between RIRs
  • Takes more documentation than a transfer inside one RIR
  • Only available between RIRs with compatible inter-RIR transfer policies

Which RIRs Support Inter-RIR Transfers?

As of September 2026, four of the five RIRs support inter-RIR transfers:

Participating RIRs

RIPE NCC (Europe, Middle East, Central Asia)

  • Policy: ripe-807 section 3; procedure: ripe-769
  • Supports both IPv4 and ASN transfers
  • Requires 50% utilization plan over 5 years for incoming transfers from needs-based RIRs
  • Contact: inter-rir@ripe.net

ARIN (North America)

  • Policy: NRPM 8.4, Inter-RIR Transfers to Specified Recipients
  • Supports IPv4 and ASN transfers
  • A first /24 needs no justification (NRPM 8.5.4); larger or additional blocks need 50% use within 24 months (8.5.5)
  • The source must not have received IPv4 from ARIN in the 12 months before approval (NRPM 8.4)
  • 36-month waitlist restriction after transferring resources out

APNIC (Asia-Pacific)

  • Policy: APNIC inter-RIR transfers
  • Supports IPv4 and ASN transfers
  • Requires 24-month utilization plan for incoming transfers
  • 5-year hold period for resources from the 103/8 free pool

LACNIC (Latin America and Caribbean)

  • Policy: LAC-2019-01, inter-regional IPv4 transfers
  • IPv4 only (no ASNs); in force since July 2020, announced operational on 17 August 2020
  • 3-year hold period before LACNIC-allocated space can be transferred
  • 1-year re-transfer restriction
  • Minimum transfer size: /24

Non-Participating RIR

AFRINIC (Africa)

  • AFRINIC ratified a transfer policy covering IPv4 and ASNs, inter-RIR included where reciprocal policies exist, in February 2026 (AFPUB-2020-GEN-006-DRAFT03, see AFRINIC policy proposals)
  • As of September 2026 that policy is not in AFRINIC's Consolidated Policy Manual, and ARIN and the RIPE NCC still list AFRINIC as closed to inter-RIR transfers
  • Transfers inside the AFRINIC region have existed since 2017

Policy Compatibility and Reciprocity

Inter-RIR transfers can only occur between RIRs with reciprocal, compatible, needs-based policies. This means:

Compatible RIR pairs (as of September 2026):

Pair IPv4 ASN
RIPE NCC and ARIN yes yes
RIPE NCC and APNIC yes yes
RIPE NCC and LACNIC yes no
ARIN and APNIC yes yes
ARIN and LACNIC yes no
APNIC and LACNIC yes no
AFRINIC and any RIR no no

Sources: RIPE NCC inter-RIR transfers, ARIN transfers. LACNIC ASNs move only through a merger or acquisition inside the LACNIC region.

Policy compatibility requirements:

  • Both RIRs must have inter-RIR transfer policies in place
  • Policies must include reciprocal provisions allowing bidirectional transfers
  • Both RIRs must apply needs-based assessment (though requirements may differ)
  • Transfer must comply with both source and destination RIR policies

General Inter-RIR Transfer Requirements

While specific requirements vary by RIR, all inter-RIR transfers share common prerequisites. Per-region rules are in Inter-RIR Transfer Eligibility by Region.

Source Organization Requirements

Eligibility criteria:

  • Must be the registered holder of the resources in the source RIR
  • Resources must meet minimum hold period requirements (varies by RIR)
  • Fees paid: the RIPE NCC requires every LIR account's annual contribution paid before a transfer (Billing Procedure 2026), and ARIN starts processing once the $500 transfer fee is received
  • Cannot have outstanding disputes regarding the resources
  • Signing parties and their representatives are checked against Dutch and EU sanctions lists by the RIPE NCC (ripe-863)

Hold periods by RIR:

  • ARIN: a source that received IPv4 from ARIN (allocation, assignment or transfer) in the previous 12 months cannot transfer out (NRPM 8.4)
  • RIPE NCC: IPv4 and 16-bit ASNs cannot be transferred for 24 months from the date the holder received them; 32-bit ASNs and IPv6 carry no restriction (ripe-807 section 2.2.1). Resources received through a merger or acquisition keep the clock running
  • APNIC: 5 years for space delegated from 103/8; no other hold period is published
  • LACNIC: 36 months (3 years) after LACNIC allocation; additionally, blocks received via transfer cannot be re-transferred for 12 months (LACNIC policy)

Documentation required:

  • Company registration documents
  • Authorization letter from legal representative
  • Proof of current resource registration
  • A signed and notarized Officer Acknowledgement Letter (ARIN source)

Recipient Organization Requirements

Basic eligibility:

  • Must have active presence in the destination RIR's service region
  • Must hold the contract the destination RIR requires: membership or a sponsoring LIR contract in the RIPE region, a Registration Services Agreement at ARIN, an APNIC account (Member or Non-Member), LACNIC membership
  • Must demonstrate legitimate need for the resources
  • Must be current with obligations to the destination RIR
  • Must comply with destination RIR's technical requirements

Needs assessment requirements:

  • ARIN: none for a first /24 (NRPM 8.5.4); 50% use within 24 months for a larger or additional block (8.5.5)
  • RIPE: 50% utilization plan over 5 years (for transfers from needs-based RIRs)
  • APNIC: 24-month utilization plan
  • LACNIC: Needs justification per LACNIC policies

Technical Requirements

Minimum transfer sizes:

  • ARIN, APNIC and LACNIC set a /24 minimum (256 addresses), so every inter-RIR IPv4 transfer moves at least a /24
  • ASN transfers: Individual ASNs or blocks per RIR policy

Resource requirements:

  • Resources must be validly registered in the source RIR
  • Must not be designated as special-use or reserved space
  • Must be publicly routable address space
  • Legacy resources follow their own rules (see Legacy Resources under Special Considerations)

Step-by-Step Inter-RIR Transfer Process

The inter-RIR transfer process involves multiple stages and coordination between both RIRs.

Phase 1: Pre-Transfer Preparation

Step 1: Verify eligibility

  • Confirm resources meet hold period requirements in source RIR
  • Verify recipient has active presence in destination RIR region
  • Check that both RIRs have compatible inter-RIR transfer policies
  • Check that no dispute or lien sits on the resources

Step 2: Create or verify RIR accounts

  • Source organization: Active account in source RIR
  • Recipient organization: Active account or LIR sponsor in destination RIR
  • The legal entity name must match across every document

Step 3: Prepare needs justification (recipient)

  • ARIN recipients: request pre-approval when the block is larger than a first /24 (valid for two years, based on a 24-month projected need)
  • RIPE recipients: Prepare 5-year 50% utilization plan
  • APNIC recipients: Document 24-month utilization requirements
  • LACNIC recipients: Prepare needs justification per LACNIC policy

Step 4: Gather required documentation

For source organization:

  • Company registration papers from national authorities
  • Letter of authorization from authorized signatory
  • Confirmation of resource ownership
  • Signed and notarized Officer Acknowledgement Letter (ARIN)

For recipient organization:

  • Company registration documents
  • Network infrastructure documentation
  • Utilization plans and needs justification
  • Contact information for authorized representatives

Phase 2: Initiate Transfer Request

Step 5: Submit request to source RIR

The transfer request is always initiated by the transferring party at the source RIR.

RIPE source:

  • Send request to inter-rir@ripe.net
  • Include both party details and resource information
  • Provide confirmation letter from authorized signatory

ARIN source:

  • Submit through ARIN Online portal
  • Pay non-refundable processing fee ($500 for IPv4 transfers)
  • Admin or Tech POC must submit the request

APNIC source:

  • Complete APNIC's Inter-RIR Transfer Template (resources, original delegation dates, legacy flag, both parties)
  • E-mail it to admin@apnic.net
  • For an inbound transfer, APNIC contacts the recipient account for the justification once the other RIR has sent the request

LACNIC source:

Step 6: Source RIR review

The source RIR reviews the transfer request and checks that:

  • Resources are registered to the source organization
  • Hold period requirements are met
  • Source organization is current with obligations
  • All required documentation is complete and accurate
  • Resources are eligible for transfer

No RIR publishes a duration for this step.

Phase 3: Destination RIR Processing

Step 7: Source RIR contacts destination RIR

Once the source RIR approves the transfer, they will formally contact the destination RIR to coordinate the transfer.

Inter-RIR coordination includes:

  • Verification of policy compatibility
  • Confirmation of resource details
  • Exchange of transfer documentation
  • Timeline coordination

Step 8: Recipient submits documentation to destination RIR

The recipient organization must now work with the destination RIR:

For ARIN recipients:

  • Complete the needs assessment or use an existing pre-approval (a first /24 needs neither)
  • Sign Registration Services Agreement (RSA)
  • Pay the recipient processing fee and the annual Registration Services Plan fee
  • Submit justification documentation

For RIPE NCC recipients:

  • Choose the registration status. ALLOCATED PA can only be held by RIPE NCC members. ASSIGNED PI can be held through a sponsoring LIR, with no further assignments allowed. Legacy space can keep LEGACY status without any contract, but RPKI then needs one
  • The contract (membership or sponsoring LIR) must exist before the RIPE NCC evaluates the request
  • Submit the plan for using at least 50% of the space within five years (transfers from needs-based regions, ripe-807 section 3.2)
  • Provide the registration document of the legal entity; natural persons prove identity with an ID document checked through iDenfy
  • Show at least one active network element in the RIPE NCC service region

If your block lands in the RIPE region as PI and you do not want membership, we can sponsor an IPv4 PI block for €135 per year (€60 plus the €75 RIPE NCC fee, as of September 2026), setup on quote.

For APNIC recipients:

  • Submit 24-month utilization plan
  • Provide evidence of past delegation compliance
  • Supply organization documentation
  • Confirm active presence in APNIC region

For LACNIC recipients:

  • Submit needs justification
  • Provide required documentation
  • Confirm compliance with LACNIC policies

Step 9: Destination RIR needs assessment

The destination RIR evaluates whether the recipient qualifies for the resources:

Assessment criteria:

  • Legitimate presence in the destination region
  • Demonstrated need for the specific amount of resources
  • Technical capability to utilize the resources
  • Compliance with destination RIR policies
  • Current standing with the RIR

The recipient's paperwork decides the pace here: the contract, the needs plan and the identity checks must all be in place.

Phase 4: Final Approval and Transfer

Step 10: Bilateral RIR approval

Both RIRs must approve the transfer before it can proceed:

Source RIR confirms:

  • Willingness to de-register resources
  • No outstanding issues with source organization
  • Resources are clear for transfer

Destination RIR confirms:

  • Recipient meets all eligibility requirements
  • Needs assessment is approved
  • All fees are paid
  • Documentation is complete

Step 11: RIRs coordinate the transfer

The two RIRs work together to execute the transfer:

  • Source RIR prepares to de-register resources
  • Destination RIR prepares to register resources
  • Both RIRs coordinate timing to minimize routing disruption
  • Transfer is executed simultaneously in both systems

Step 12: Resources are transferred

Source RIR actions:

  • De-registers resources from source organization
  • Updates WHOIS database
  • Marks resources as transferred out
  • Issues transfer confirmation

Destination RIR actions:

  • Registers resources to recipient organization
  • Updates WHOIS and routing databases
  • Confirms transfer completion

Phase 5: Post-Transfer Actions

Step 13: Move RPKI, IRR and reverse DNS

  • Before the transfer: the source removes the prefix from its ROAs, reviews maxLength on what remains and deletes the IRR objects that no longer apply (ARIN's source checklist)
  • On completion the source RIR shrinks or revokes its resource certificate; the RIPE NCC issues the recipient's certificate within a few minutes when the resources are certifiable
  • Until the recipient publishes new ROAs, its announcements show as RPKI Unknown, not Invalid; create the ROAs on the day the block lands and check them with the RPKI checker
  • Outbound from the RIPE region, the reverse delegation is removed from DNS immediately, so agree the new delegation with the recipient in advance
  • Recreate route and domain objects in the destination registry and tell your upstreams the block now originates from the same ASN under a new registry

Step 14: Verify transfer completion

Confirm the following:

  • Resources appear in destination RIR's WHOIS database
  • WHOIS records show correct organization details
  • Resources are de-registered from source RIR
  • All routing information is updated

Step 15: Maintain compliance

Ongoing obligations:

  • Pay annual fees to destination RIR
  • Keep registration information current
  • Comply with resource utilization commitments
  • Maintain active presence in destination region
  • Respond to RIR communications promptly

No RIR publishes a duration for inter-RIR transfers. The RIPE NCC completes most transfers inside its own region within one or two business days, and says transfers between RIRs take longer because both registries must synchronise; ARIN says the time "can vary" and promises only that the move is executed within two business days of receiving the signed RSA and the fees. What to expect per RIR pair is in Transfer Timeline and Approval Process.

Costs and Fees

Inter-RIR transfer costs include fees from both RIRs plus any broker or consultant fees:

ARIN Fees

  • Source Transfer Request fee: $500, non-refundable, paid by the ARIN source (IPv4 or ASN)
  • Recipient Transfer Processing fee: $187.50 for a /24, $375 for a /22, on the 2026 fee schedule
  • Registration Services Plan, one fee per Org ID: $275 per year for a /24 or smaller, $550 up to a /22 in 2026 ($288.75 and $577.50 from 2027)
  • The recipient signs a Registration Services Agreement (NRPM 8.5.1)
  • An ARIN source cannot use the IPv4 waitlist for 36 months after transferring out

RIPE NCC Fees

  • Transfers are free of charge at the RIPE NCC
  • Direct membership: €1,800 per LIR account per year plus a €1,000 sign-up fee under the RIPE NCC Charging Scheme 2026 (ripe-848); ripe-867, adopted in May 2026, sets €1,894 for 2027 with one ASN included
  • Without membership, a PI assignment or an ASN can be held through a sponsoring LIR: we sponsor a transferred-in IPv4 block registered as PI for €135 per year (€60 plus the €75 RIPE NCC fee), setup on quote
  • Every LIR account's annual contribution must be paid before the RIPE NCC processes a transfer (Billing Procedure 2026)

APNIC Fees

  • Transfer fee: 20% of the annual fee for the resources moved, paid by the APNIC source on an inter-RIR transfer (APNIC fee schedule)
  • An APNIC recipient needs an APNIC account, Member or Non-Member; as a Member, the base annual fee is AUD 1,295 in 2026 (AUD 1,356 in 2027) plus AUD 500 sign-up

LACNIC Fees

  • Inter-RIR administrative fee: US$1,000 for a /24 up to a block smaller than a /19, US$1,500 for a /19 or larger (LACNIC inter-regional transfers)
  • The receiving organisation pays a non-refundable US$200 down payment before LACNIC analyses the justification
  • Active LACNIC membership required

The Block Itself

Registry fees are the small line. IPv4 changed hands at about $23.50 per address for /22 to /24 blocks in August 2026, so about $6,000 for a /24, according to broker IPv4.Global's monthly averages (online and private sales mixed, priced at agreement date). Broker commission, legal review and escrow come on top and are negotiated per deal.

Special Considerations

Legacy Resources

IPv4 legacy space (allocated before the RIR system):

  • The RIPE NCC accepts inbound legacy IPv4 and ASNs from ARIN and APNIC and legacy IPv4 from LACNIC
  • The resources can keep LEGACY status; no contract with the RIPE NCC or a sponsoring LIR is needed unless you want RPKI
  • ARIN treats legacy space under its own agreements; check the ARIN transfers page before you start

ASN Transfers

Inter-RIR ASN transfers:

  • Only between the RIPE NCC, ARIN and APNIC; LACNIC moves IPv4 only
  • The RIPE NCC treats 16-bit ASNs as scarce: 24 months from receipt before they can be transferred (ripe-807 section 2.2.1); 32-bit ASNs carry no restriction
  • The ASN keeps its number; only the registry and the holder's contract change

IPv6 Transfers

Status as of September 2026:

  • ARIN excludes IPv6 from inter-RIR transfers
  • The RIPE NCC's inter-RIR table lists IPv4 and ASNs for ARIN and APNIC, and IPv4 only for LACNIC
  • If you need IPv6 in the new region, request it there: in the RIPE region an IPv6 PI /48 through a sponsoring LIR costs €300 setup plus €135 per year with us (€435 the first year)

Partial Transfers

Splitting address blocks:

  • Minimum size /24 must be maintained
  • Source RIR must approve the split
  • CIDR boundary alignment required

Best Practices for Successful Inter-RIR Transfers

1. Plan Early and Allow Sufficient Time

Start before you need the addresses. The recipient side is what takes time:

  • Account for potential documentation issues
  • Allow time for needs assessment preparation
  • Consider RIR processing backlogs
  • Plan for unexpected delays

2. Understand Both RIRs' Policies Thoroughly

Research requirements:

  • Read official policy documentation from both RIRs
  • Understand needs assessment criteria
  • Know hold period and restriction requirements
  • Familiarize yourself with fee structures

Official policy sources:

3. Prepare Complete Documentation Upfront

Checklist:

  • Company registration papers (recent, official)
  • Letters of authorization (properly signed and notarized if required)
  • Network diagrams and infrastructure documentation
  • Utilization plans with detailed justification
  • Contact information for all authorized representatives
  • Any additional RIR-specific requirements

4. Consider Pre-Approval

ARIN recipients:

  • Submit pre-approval request before initiating transfer
  • Valid for two years (ARIN pre-approval)
  • Reduces transfer processing time
  • Provides certainty before committing to purchase

5. Use Experienced Professionals When Needed

Consider using:

  • Transfer brokers: find the counterparty and hold the escrow
  • A sponsoring LIR: holds PI space or an ASN for a non-member in the RIPE region
  • Legal advisers: review the sale agreement
  • Technical consultants: assist with routing updates

6. Verify Post-Transfer Compliance

After transfer completion:

  • Confirm WHOIS accuracy
  • Update all routing information
  • Set up annual fee payments
  • Maintain utilization commitments

7. Know the Four Usual Failure Modes

Most refusals come from four causes. A hold period not yet over: check the receipt date against ripe-807's 24 months, ARIN's 12-month rule and LACNIC's one or three years before you sign anything.

Paperwork that does not match: the legal name on the registry object, the company register extract and the authorization letter must be identical, and ARIN wants the Officer Acknowledgement Letter notarized. A needs plan that does not add up: ARIN wants 50% use within 24 months above a first /24, the RIPE NCC 50% within five years, APNIC a 24-month plan, so size the request to what you can show.

A pair that does not exist: no ASN moves to or from LACNIC and nothing moves to or from AFRINIC. On the routing side, remove the prefix from the source ROAs before de-registration and publish the recipient's ROAs on completion, so the block never sits Invalid.

Using Via-Registry for Inter-RIR Transfers

We check eligibility on both sides, prepare the forms and justifications, handle the correspondence with both RIRs and keep you updated until the registries switch. Transfers are quoted per case through our inter-RIR transfer service. If the block lands in the RIPE region as PI, we can sponsor it afterwards under our LIR.

Frequently Asked Questions

Can any IPv4 addresses be transferred between RIRs?

Not all IPv4 addresses are eligible for inter-RIR transfer. Resources must meet hold period requirements, must not be special-use addresses, and must be properly registered in the source RIR. Legacy resources may have additional restrictions. Additionally, AFRINIC does not participate in inter-RIR transfers, so no resources can be transferred to or from the African region.

How long does an inter-RIR transfer typically take?

No RIR publishes a duration for inter-RIR transfers. The RIPE NCC completes most transfers inside its own region within one or two business days and says transfers between RIRs take longer, because both registries must synchronise; ARIN's one firm figure is two business days to execute the move once the signed RSA and the fees are in. The recipient's contract, needs plan and identity checks are what usually set the pace.

Do I need to be an LIR member to receive transferred resources?

In the RIPE region, PA allocations can only be held by RIPE NCC members; PI space and ASNs can be held through a sponsoring LIR, and legacy space needs no contract at all unless you want RPKI. ARIN has no membership requirement: the recipient signs a Registration Services Agreement and pays the Registration Services Plan fee. APNIC recipients need an APNIC account (Member or Non-Member); LACNIC recipients become members.

Can I transfer IPv6 addresses between RIRs?

ARIN excludes IPv6 from inter-RIR transfers, and the RIPE NCC's inter-RIR table lists IPv4 and ASNs only. Request IPv6 in the destination region instead; in the RIPE region a PI /48 through a sponsoring LIR is €300 setup plus €135 per year with us.

What happens if my transfer request is rejected?

If either RIR rejects the transfer, you'll receive an explanation of the rejection reasons. Common issues include insufficient needs justification, incomplete documentation, or policy non-compliance. Most rejections can be resolved by addressing the specific concerns and resubmitting. We prepare the resubmission when the refusal is about paperwork or the needs plan.

How active is the inter-RIR transfer market?

Transfer volume stays high. The RIPE NCC alone recorded 5,935,616 IPv4 addresses transferred in July 2026 (RIPE NCC member update, August 2026). Its inter-RIR transfer statistics list every cross-region move by month.

Are there restrictions on re-transferring resources?

ARIN blocks a source that received IPv4 from ARIN in the previous 12 months and bars it from the waitlist for 36 months after transferring out. The RIPE NCC locks IPv4 and 16-bit ASNs for 24 months after receipt; 32-bit ASNs and IPv6 are free to move. LACNIC locks received space for one year and LACNIC-allocated space for three.

How much does an inter-RIR transfer cost?

The registry side is small: ARIN charges the source $500 and the recipient a processing fee ($187.50 for a /24) plus its annual Registration Services Plan fee ($275 for a /24 or smaller in 2026); APNIC charges the source 20% of the annual fee for the resources moved; LACNIC charges US$1,000 or US$1,500 by block size; the RIPE NCC charges nothing. The block itself cost about $23.50 per address for /22 to /24 sizes in August 2026 (IPv4.Global), about $6,000 for a /24. Broker, legal and escrow fees are negotiated per deal.

Summary

An inter-RIR transfer starts at the source RIR, needs both registries' approval and ends with a registry switch on an agreed date. The recipient's paperwork decides the pace: a first /24 into ARIN needs no justification, and a RIPE NCC recipient without membership holds non-legacy space as PI through a sponsoring LIR. Plan the ROAs and route objects for the day the block lands, and check the pair first: LACNIC moves IPv4 only, AFRINIC nothing.

Next Steps

Related guides:

Questions about a specific pair or block? Contact us with the source RIR, the destination RIR and the block size.

Back to Resources