How Long an IPv4 Transfer Takes, by Registry
Typical durations from signed agreement to updated registry record. Ranges reflect common experience as of 2026 and the procedures each registry publishes; they are not service commitments. The registry’s own processing time is usually the smallest part.
Registry processing, after a complete request
| Registry | Needs assessment | Typical review | Completion step | Within-registry total |
|---|---|---|---|---|
| RIPE NCC | None | 1–2 weeks | Database update on approval | 1–3 weeks |
| ARIN | /24 to a new recipient: none. Larger: 50% use in 24 months | 1–3 weeks | Within 2 business days of signed RSA and fees | 2–5 weeks |
| APNIC | Usage plan for every recipient | 1–3 weeks | After transfer or membership fee is paid | 2–5 weeks |
| LACNIC | Recipient need | 2–4 weeks | Registry update | 3–6 weeks |
| AFRINIC | Recipient need; recipient must be a member | Variable | After fees are paid | Hard to predict; allow for delays |
| Inter-RIR | Receiving registry’s rules apply | Source review, then receiving review | Coordinated update date in both registries | 4–8 weeks or more |
ARIN’s two-business-day completion figure comes from its transfer page. Other ranges are typical observations, not published targets. Check the registry’s current notices before committing to a date; AFRINIC operations in particular have been affected by its governance situation in recent years.
The whole transaction
Registry processing sits in the middle of a longer sequence. For a buyer starting from scratch:
| Stage | Typical duration | Runs in parallel with |
|---|---|---|
| Open the recipient’s registry account (LIR, ARIN Org ID, APNIC account) | 1–4 weeks | Negotiation |
| ARIN pre-approval, if used | 1–3 weeks | Searching for a seller |
| Block verification | 2–5 days | Contract drafting |
| Contract and escrow agreement | 1–2 weeks | Verification |
| Escrow funding | 1–5 days, longer for first-time escrow onboarding | — |
| Registry processing | See table above | — |
| Escrow release after the record changes | 1–3 business days | Post-transfer setup |
| Post-transfer setup before first announcement | 2–10 days | — |
Running the account setup and pre-approval in parallel with commercial work is the single biggest saving. Doing them in sequence routinely adds a month.
What adds weeks
- Recipient has no registry account. The block has nowhere to go until membership is approved.
- Stale or mismatched documents. A company extract older than the registry accepts, or a legal name that differs between contract and record. Each correction is another review cycle; see documents by registry.
- Holder of record is a predecessor company. The registry first processes a merger or acquisition update to the current entity, then the transfer.
- Weak needs justification. At registries that assess need, vague usage plans attract follow-up questions. Specific deployments, dates, and customer counts get approved.
- Slow replies. Every unanswered registry question pauses the request. Name one person on each side who answers the same day.
- Restriction windows. A block inside its post-transfer holding period cannot move until the period ends; no amount of paperwork shortens it. See the restrictions in the transfer process overview.
Setting a long-stop date
The escrow agreement and contract need a date after which either side may walk away. A workable rule: the within-registry total from the first table, plus four weeks for account setup and clarifications, doubled for inter-RIR transfers. Too short, and a normal clarification round triggers a termination right. Too long, and the buyer’s money sits idle. See escrow and payment.
If timing matters more than price, leasing a block can cover the gap: leased space is usable in days because no registry transfer is involved.