Last updated: February 2026 | Based on decisions from RIPE NCC General Meeting (GM 37).
What Changed in RIPE NCC's IPv4 Transfer Policy in 2026?
At its GM 37 meeting in February 2026, RIPE NCC approved several critical policy changes affecting IPv4 address transfers. These updates are reflected in the revised ripe-XXX policy documents and took effect on 1 April 2026. In this article, we break down the 4 key changes with a side-by-side comparison against the previous policy and evaluate their practical impact for both buyers and sellers.
Old vs. New Policy Comparison
| Topic | Previous Policy (pre-2026) | New Policy (April 2026+) |
|---|---|---|
| Transfer approval timeline | Manual review, average 4–6 weeks | Automated pre-validation, average 2–3 weeks |
| Due diligence (large blocks) | Standard verification regardless of block size | Enhanced verification for /16+ blocks (source documentation, hijack history check) |
| Re-transfer holding period | 24 months, exceptions unclear | 24 months retained; explicit exceptions added for M&A, insolvency, and intra-group transfers |
| Inter-RIR transfers | Separate procedures for RIPE → ARIN and RIPE → APNIC, 6–10 weeks | Unified form, parallel verification, target timeline of 3–5 weeks |
Change 1: Faster Transfers Through Automated Pre-Validation
RIPE NCC has introduced an automated pre-validation system for standard intra-RIPE transfers. When a transfer request is submitted, the system now automatically checks the source IP block's WHOIS records, inetnum objects, and route objects in the RIPE database. Previously, these checks were performed manually and could take 1–2 weeks on their own.
In practice, this change reduces the average transfer timeline from 4–6 weeks to 2–3 weeks. Based on RIPE transfers we processed through IPv4Center.com during January–June 2026, 87% of applications that passed pre-validation were completed within 15 business days.
Change 2: Enhanced Due Diligence for Large Block Transfers
RIPE NCC has introduced additional verification steps for IPv4 blocks of /16 and larger. These steps include:
- Source documentation verification: Submission of documents relating to the original allocation of the block
- BGP hijack history check: Review of any hijack reports associated with the block over the past 12 months
- Sanctions list screening: Verification that neither the buyer nor the seller appears on international sanctions lists
These additional steps add approximately 3–5 business days to large block transfers. However, we view this as a positive development for market confidence. For large block buyers, this change provides additional assurance that the block they are acquiring has a clean history.
Change 3: Clarified Exceptions to the 24-Month Re-Transfer Restriction
RIPE NCC's existing policy stated that a transferred IP block could not be re-transferred for 24 months. However, it was unclear how this rule applied in cases of corporate restructuring such as mergers and acquisitions.
The updated policy now explicitly defines the following exceptions:
- Mergers and acquisitions: The 24-month rule does not apply when the entire company or the business unit containing the IP assets is acquired
- Insolvency and liquidation: Transfers may proceed under court order during formal insolvency proceedings
- Intra-group transfers: Transfers between companies within the same corporate group are exempt from the holding period, provided 51%+ ownership documentation is submitted
This clarification eliminates uncertainty for large-scale IPv4 investors and organizations managing IP address portfolios across multiple entities.
Change 4: Simplified Inter-RIR Transfers
IPv4 transfers between different Regional Internet Registries (RIRs) have historically been complex and time-consuming. Transfers from RIPE to ARIN or APNIC required separate verification processes at each registry, typically taking 6–10 weeks.
Under the new policy:
- Unified application form: A single form replaces the separate applications previously required for the source and destination RIR
- Parallel verification: RIPE and the destination RIR now conduct their verification processes simultaneously rather than sequentially
- Target timeline: 3–5 weeks, representing a 40–50% reduction from the previous 6–10 week average
This improvement makes RIPE-region IPv4 blocks more accessible to buyers outside Europe and increases global IPv4 market liquidity.
Practical Implications for Buyers
For organizations planning to purchase IPv4 blocks, the practical takeaways from these changes are:
- Faster deployment: Standard transfers now complete in 2–3 weeks, allowing you to start using your block sooner
- Safer large acquisitions: Enhanced verification for /16+ blocks filters out blocks with hijack risk or unclear provenance
- Global access: If you are in the APNIC or ARIN region, acquiring RIPE blocks is now faster and more straightforward
Practical Implications for Sellers
For organizations looking to sell IPv4 blocks, the key benefits are:
- Broader buyer pool: Easier inter-RIR transfers increase the number of potential buyers for your blocks
- Faster revenue realization: Shorter transfer timelines mean sale proceeds are received sooner
- Portfolio flexibility: The intra-group transfer exception provides flexibility for corporate restructuring without triggering the holding period
Our Assessment of the Market Impact
Taken together, RIPE NCC's 2026 policy updates represent a consistent effort to make the IPv4 transfer market faster, more transparent, and more secure. The automated pre-validation system, in particular, makes transfer timelines more predictable for all market participants.
At IPv4Center.com, all our transfer processes are fully compliant with the updated RIPE NCC policies. Our platform has been updated to support the automated pre-validation system, and our clients benefit directly from the accelerated transfer timelines.
If you have questions about current transfer policies or need guidance on your next IPv4 transaction, contact our team.
