Skip to content
Fresh IPv4 news just dropped — 🎉 see what you’re missing

IPv4 Transfer Process: Stages and Checkpoints

Reviewed by Philippe Girard, RIR policy & compliance lead

An IPv4 transfer is a change of the holder of record at the regional internet registry. The commercial agreement and the registry update are separate milestones. Until the registry approves and records the change, its record continues to identify the existing holder.

The seven stages below describe a typical purchase transfer between unrelated holders. Escrow applies when the parties use it; recipient needs assessment applies only where the receiving registry and transfer route require it. Account setup and any available recipient pre-approval can run alongside negotiations. Mergers and acquisitions follow a separate path, and inter-RIR transfers require coordination between both registries.

Check policy before starting the process

Use the RIR transfer-policy comparison to establish the source restrictions, recipient requirements, minimum size and applicable exceptions. The regional references explain the conditions and link to the controlling policies.

For a transfer between registries, also establish the supported inter-RIR route. For registry charges, use the fee-model reference.

Confirm both parties are eligible

Do this before anyone spends time on due diligence.

Source. Identify the registered holder and establish who may act for it. Check both the resource’s receipt history and restrictions tied to recent activity in the source account. Resolve a predecessor company or corporate event through the relevant registry procedure. A voluntary transfer lock is a separate eligibility check.

Recipient. Establish the account and resource relationship required by the receiving registry. For RIPE allocated PA space this means the appropriate member account; PI sponsorship is a different relationship. Start account verification alongside negotiations and confirm the intended resource status before filing.

Verify the block

Check the registry record, transfer history, routing history, RPKI state, reputation, and any disputes. A block that fails here is cheaper to walk away from than to fix. The full list of checks, with what passes and what does not, is in the block verification checklist.

Sign the agreement and fund escrow

The sale contract and the registry’s paperwork are different documents. RIPE NCC requires a transfer agreement signed by both parties’ authorised representatives, separate from the commercial contract. ARIN asks for documentation case by case, accepts redacted copies with prices removed, and offers a standard NDA.

If the parties use escrow, the buyer deposits funds with the escrow holder under the agreed terms. The contract should tie release to verification that the registry record shows the recipient, together with any other agreed completion conditions. See escrow and payment.

Get recipient approval where policy requires it

Identify the test for this specific receiving registry and route. Use the needs-justification worksheet to reconcile current holdings, utilization and dated demand. Where pre-approval is available, confirm its validity and scope before relying on it.

RIPE’s ordinary intra-region transfers do not require recipient needs assessment. For inbound transfers from needs-based regions, the recipient must supply a plan for at least 50% use within five years. M&A and historical-resource procedures can have different requirements.

Submit the transfer request

File through the registry’s portal with the documents it lists for your case. At ARIN, the admin or tech contact of each organisation files its own request in ARIN Online; ARIN links the two tickets and invoices the processing fee before work starts. In the RIPE region only the offering side files, under Resources → Request Transfer in the LIR Portal. Documents by registry breaks these down; the common core is company registration extracts for both sides, proof that the signatories may sign, and identity verification for natural persons.

For inter-RIR transfers, the source registry evaluates first and then hands over to the receiving registry, which assesses the recipient under its own policy. Both registries update their databases on an agreed date.

Answer registry questions and wait for approval

Registry staff check the documents, the signatories’ authority, the policy conditions, and sanctions. RIPE NCC rejects transfers where either party is on the EU sanctions list. At ARIN, approval is followed by an invoice for remaining fees and, where needed, an RSA that must be signed within 90 days; ARIN completes the transfer within two business days of receiving both. Each unanswered clarification adds a full round trip, typically several business days. Timelines by RIR gives the usual durations for each stage.

Confirm the registry update and release funds

Confirm that the public record shows the recipient. Query it yourself rather than relying on an email. Before running these commands, replace the prefix and both registry endpoints with those for your transferred block. The values below illustrate a RIPE lookup; 203.0.113.0/24 is documentation space and will not verify your organisation’s holding. For an inter-RIR transfer, query the receiving registry and follow any referrals; use WHOIS and RDAP to identify the authoritative endpoint and read its record format.

PREFIX='203.0.113.0/24'             # Replace with your transferred prefix
WHOIS_HOST='whois.ripe.net'         # Replace with the authoritative WHOIS server
RDAP_BASE='https://rdap.db.ripe.net' # Replace with the authoritative RDAP base URL

whois -h "$WHOIS_HOST" "$PREFIX"
curl --fail-with-body -sS -L "$RDAP_BASE/ip/$PREFIX" \
  | jq '{handle, startAddress, endAddress, entities: [.entities[]? | {handle, roles}]}'

Expected result after substituting your values: the record’s range matches the transferred block and its holder identifiers match the recipient’s registry account. Check that the response is the relevant allocation or assignment, rather than a covering parent record. Where escrow is used, instruct release once this check and the other contractual conditions are satisfied.

Mergers and acquisitions are a different path

Establish whether the legal holder changes. A share acquisition can leave the same entity holding the resource, while a statutory merger or business-asset transaction can require a registry update. Use the M&A evidence and registration guide for the qualifying event, successor chain and regional exceptions. An ordinary prefix transaction does not become M&A merely because the contract uses that label.

After the update

The registry update moves the block; it does not make it routable for you. Some registries delete associated objects on transfer — APNIC removes route and domain objects, for example — and every ROA issued by the seller has to be replaced. Work through the post-transfer checklist before the first announcement.

Related

Last updated on