IPv4 PI Eligibility Requirements

IPv4 Provider Independent (PI) address space represents a valuable Internet resource that enables organizations to maintain their addressing independently of their Internet Service Provider. However, the landscape for obtaining IPv4 PI space has changed dramatically due to address exhaustion. This article examines both the historical eligibility requirements and the current reality of acquiring IPv4 PI resources in 2025.

The Current State of IPv4 PI Assignments

Before diving into requirements, it's critical to understand the current availability situation.

No New Assignments from RIPE NCC

RIPE NCC officially states: "The RIPE NCC no longer allocates or assigns PI address space, except for assignments to Internet Exchange Points."

This means that as of 2025, the RIPE NCC does not assign new IPv4 PI address space to end-user organizations. This restriction results from IPv4 address exhaustion - the depletion of available IPv4 addresses in the RIPE NCC's pools.

Only Exception: Internet Exchange Points

The sole category still eligible for new IPv4 PI assignments from RIPE NCC is Internet Exchange Points (IXPs), and only under very specific criteria outlined in RIPE policy document ripe-826, section 6.1.

Current Options for IPv4 PI Space

Organizations needing IPv4 PI space in 2025 have these options:

1. Transfer market: Purchase existing IPv4 PI assignments from current holders
2. Leasing arrangements: Rent IPv4 space from brokers or holders
3. IPv6 deployment: Transition to IPv6 as the primary addressing strategy
4. PA address alternatives: Use Provider Aggregatable space from an ISP

For comprehensive background on PI resources, see our guide to Understanding Provider Independent (PI) Resources.

Historical IPv4 PI Eligibility Requirements

While new assignments are no longer available, understanding the historical requirements remains important because:

• Existing PI holders must continue meeting these criteria to maintain their assignments
• Transfer recipients must demonstrate they meet equivalent requirements
• The principles inform current IPv6 PI policies
• Audit processes reference these original criteria

Primary Eligibility Criteria

Under the previous RIPE policy for IPv4 PI assignments, organizations needed to demonstrate:

1. Multi-homing Intent

Requirement: "End users must demonstrate the intent to multi-home the address space to at least two autonomous systems that the end-user does not control."

What this meant:

• Connection to two or more different Internet Service Providers
• Use of BGP routing protocol to announce the PI space
• Autonomous systems controlled by the ISPs, not the applicant
• Active multi-homing or concrete plans to implement it

Justification needed:

• Letters of intent from at least two ISPs
• BGP configuration plans
• Network topology showing multi-homed architecture
• Timeline for implementation if not yet deployed

Why multi-homing mattered: Multi-homing represents the fundamental use case for PI addressing. If an organization only connects to one ISP, Provider Aggregatable (PA) addresses from that ISP serve the purpose more efficiently from an Internet routing perspective.

2. Legitimate Need for Independent Addressing

Requirement: Organizations needed to demonstrate genuine business or technical requirements for provider-independent address space.

Valid justifications included:

• Business continuity requirements necessitating ISP independence
• Geographic distribution requiring connections to multiple regional providers
• Specific networking architectures incompatible with PA space
• Infrastructure providing services to third parties requiring stable addressing
• Technical limitations preventing renumbering

Invalid justifications:

• Simple preference for PI over PA space
• Desire to avoid potential future renumbering without multi-homing
• Speculative future needs without concrete plans
• Prestige or marketing considerations

3. Own Infrastructure Use Only

Requirement: PI address space "can only be used for the end user's own infrastructure and can't be leased out."

What qualified as "own infrastructure":

• Internal corporate networks
• Data center equipment operated by the organization
• Servers and services provided by the organization
• Network infrastructure under the organization's control
• Customer equipment hosted in the organization's facilities

Prohibited uses:

• ISP-style address assignments to customers
• Leasing or renting address space to third parties
• Providing addresses to subsidiary organizations
• Sub-assignment to business partners or affiliates

This restriction prevents PI holders from effectively operating as unauthorized LIRs (Local Internet Registries).

4. Service Region Requirements

Requirement: "RIPE NCC will only register resources if the network that will be using them has at least one active element located in the RIPE NCC service region."

RIPE service region includes:

• Europe (all countries)
• Middle East
• Central Asia (parts)

What constituted "active element":

• Router, server, or network device actively using the PI addresses
• Physical presence in the service region
• Not merely registered office or mailing address

Organizations with infrastructure primarily outside the RIPE region should apply through the appropriate RIR (ARIN, APNIC, LACNIC, or AFRINIC).

Size Requirements

Minimum Assignment Size

Standard minimum: /24 (256 addresses)

From RIPE policy: "It allows multihomed End Users with a requirement for one or more IPv4 PI addresses to qualify for a /24."

The /24 minimum reflects routing realities: "It is generally understood that the minimum prefix size which is generally routable on the Internet is a /24."

Practical implication: Organizations needed to justify at least a /24 even if their immediate requirements were smaller. Requesting smaller blocks (like /25 or /26) was not possible under PI policy.

Maximum Assignment Size

There was no explicit maximum, but larger assignments required proportionally stronger justification based on:

• Current address utilization
• Infrastructure size and complexity
• Number of network elements
• Growth projections over 1-2 years

Typical IPv4 PI assignments ranged from /24 to /20, with larger blocks rare and requiring exceptional justification.

Justification Standards

RIPE policy stated: "The current IPv4 PI assignment policies implemented by the RIPE NCC are based on the principal of justification by quantity of addresses."

Organizations needed to document:

Immediate utilization (within 3 months):

• Specific devices or services
• IP address allocation plans
• Network architecture details

One-year projection:

• Growth plans
• New services or infrastructure
• Business expansion details

Two-year outlook:

• Strategic plans
• Major projects
• Infrastructure evolution

Documentation Requirements

Applicants needed to provide:

Legal documentation:

• Business registration documents
• Articles of incorporation or equivalent
• Proof of legal entity status

Technical documentation:

• Network topology diagrams
• IP address utilization plans
• Current address usage (if applicable)
• Infrastructure descriptions

Multi-homing evidence:

• ISP commitment letters or contracts
• BGP session plans
• ASN documentation (if already held)
• Letters of intent from upstream providers

Justification narrative:

• Business case for PI addressing
• Why PA space insufficient
• Multi-homing requirements explanation
• Long-term network strategy

Contractual Requirements for IPv4 PI Holders

Organizations holding IPv4 PI assignments must maintain specific contractual relationships and meet ongoing obligations.

RIPE NCC Contractual Relationship

Requirement: "End Users of provider independent resources are responsible for maintaining a contractual link to the RIPE NCC either through a sponsoring LIR or else directly to the RIPE NCC for the purposes of managing these resources."

Two models:

1. Direct contract: Organization becomes a direct RIPE NCC customer (relatively rare)
2. Sponsoring LIR: Work through a RIPE NCC member organization (most common)

Sponsoring LIR Model

The sponsoring LIR acts as intermediary between the PI holder and RIPE NCC:

LIR responsibilities:

• Submitting assignment requests on behalf of the end user
• Managing contractual relationship with RIPE NCC
• Collecting and remitting annual fees
• Maintaining RIPE Database accuracy
• Facilitating communication with RIPE NCC

End user responsibilities:

• Paying annual fees (to sponsoring LIR)
• Providing accurate information
• Using resources in accordance with policies
• Maintaining eligibility criteria

Annual Maintenance Fees

IPv4 PI holders pay annual fees to RIPE NCC:

2025 fee structure: €75 per IPv4 PI assignment annually

This fee covers:

• RIPE Database maintenance
• Registry services
• Policy development processes
• Community coordination

Payment through sponsoring LIR: Most PI holders pay fees to their sponsoring LIR, who remits to RIPE NCC. The LIR typically adds service fees for their administrative work.

Total costs: Expect €200-500 annually including:

• RIPE NCC fee (€75)
• Sponsoring LIR service fee (€100-300 typically)
• Additional services (optional)

Ongoing Policy Compliance

IPv4 PI holders must continue to meet the original assignment criteria:

Continued eligibility: "PI address space can only remain assigned to a network as long as the criteria for the original assignment are maintained."

This means:

• Maintain multi-homing or capability to multi-home
• Continue using addresses for own infrastructure only
• Keep at least one network element in RIPE service region
• No unauthorized sub-assignment or leasing

RIPE NCC audits: The RIPE NCC may audit PI holders to verify:

• Resources used as documented
• Assignment criteria still met
• No policy violations
• Registration information accurate

Consequences of non-compliance: Failure to maintain eligibility criteria or comply with policies can result in:

• Warning notices from RIPE NCC
• Required corrective action
• Potential resource recovery in severe cases

Registration and Database Requirements

PI holders must maintain accurate RIPE Database entries:

Required objects:

• inetnum object: Documents the IPv4 PI assignment
• Organisation object: Represents the legal entity
• Person/role objects: Contact information
• Maintainer (mntner): Controls access to database objects

Information accuracy: Keep current:

• Contact details (administrative, technical)
• Organization information
• Network topology data
• Routing policies

Update obligations: Notify RIPE NCC of changes to:

• Legal entity status
• Contact information
• Resource usage
• Network configuration

IPv4 PI Transfer Requirements

Since new IPv4 PI assignments are unavailable, the transfer market provides the primary mechanism for obtaining IPv4 PI space.

Transfer Eligibility Requirements

RIPE Policy 2014-02 "Allow IPv4 PI Transfer" enables PI holders to transfer their assignments within the RIPE region.

Transferring party requirements:

• Hold valid IPv4 PI assignment
• Maintain good standing with RIPE NCC
• Fulfill contractual obligations
• No outstanding policy violations

Receiving party requirements:

• Demonstrate need for IPv4 address space
• Meet contractual requirements for PI resource holders
• Establish or have sponsoring LIR relationship
• Commit to policy compliance

Transfer Documentation

Both parties must provide:

Legal documentation:

• Transfer agreement between parties
• Proof of legal entity status
• Authorization signatures
• Financial transaction evidence (if required by RIPE NCC)

Technical justification:

• Receiving party's planned use
• Network infrastructure description
• Multi-homing plans or capability
• IP address utilization plans

Contractual requirements:

• Sponsoring LIR agreement for receiver
• Fee payment commitments
• Policy acknowledgment
• Database maintenance responsibilities

Transfer Process Requirements

Successful transfers require:

1. Contractual establishment: "If the receiving party does not have a contractual relationship with the RIPE NCC, it shall establish one prior to the evaluation of the transfer request. In the case of ASSIGNED PI, a sponsoring LIR may be used instead."

2. Policy compliance: "Both parties would need to fulfill the contractual requirements for independent resources before the transfer could take place."

3. Registration updates: Transfer of database maintainer, organization objects, and contact information to receiving party.

4. Fee responsibility: Receiving party assumes annual maintenance fee obligations.

Market Considerations

Organizations pursuing IPv4 PI transfers should consider:

Pricing: IPv4 addresses trade at market prices, currently ranging from €30-50 per IP address depending on block size and market conditions.

Brokers: Many organizations work with IPv4 address brokers who:

• Locate available PI blocks
• Facilitate negotiations
• Manage transfer documentation
• Guide through RIPE approval process

Due diligence: Verify before purchasing:

• Clean title (no disputes)
• Good standing with RIPE NCC
• No policy violations
• Accurate registry information
• No encumbrances or claims

Special Case: Internet Exchange Points

Internet Exchange Points represent the only category still eligible for new IPv4 PI assignments from RIPE NCC.

IXP Definition Requirements

Organizations must meet the IXP definition from IPv6 policy, requiring:

• A neutral facility enabling multiple networks to exchange traffic
• Three or more autonomous systems peering
• Clear peering policy
• Public ASN for the IXP (not private)

IXP PI Assignment Sizes

Initial assignment: /26 (64 addresses) for new IXPs

Upgrade eligibility: Upon demonstrating >50% utilization of existing space:

• /26 → /24 (256 addresses)

Maximum assignment: /22 (1,024 addresses) with full justification

IXP Restrictions

Usage limitation: "This space will be used to run an IXP peering LAN only; other uses are forbidden."

Prohibited uses include:

• IXP infrastructure management networks (use separate PI or PA space)
• Member organization services
• Route servers beyond peering LAN
• Non-IXP-related purposes

Return requirements: "IXPs must return unused assignments or PI space within 180 days of disuse."

IXP Application Requirements

IXPs applying for IPv4 PI must also:

• Have or apply for IPv6 PI assignment for their peering LAN
• Document member networks and peering relationships
• Provide peering LAN architecture
• Demonstrate neutral, multi-lateral peering facility

Alternative Solutions to IPv4 PI Assignments

Given IPv4 PI unavailability for most organizations, consider these alternatives:

IPv6 PI Deployment

Advantages:

• Readily available through standard application process
• Standard /48 assignments provide ample space
• Same provider independence as IPv4 PI
• Future-proofs infrastructure

Considerations:

• Requires IPv6 deployment expertise
• May need dual-stack with IPv4 PA temporarily
• Not all services and users fully IPv6-enabled yet

Provider Aggregatable (PA) Addresses

When suitable:

• Single-homing acceptable
• Can accommodate renumbering if changing ISPs
• Cost-sensitive deployments
• Simpler technical requirements

Limitations:

• Provider dependency
• Lost on ISP change
• Multi-homing more complex

IPv4 Address Leasing

How it works:

• Rent IPv4 space from brokers or LIRs
• Typically PA space (not PI)
• Term-based agreements
• Renewable contracts

Considerations:

• Ongoing monthly/annual costs
• Not owned, just licensed
• May require periodic renumbering
• Less stable than PI ownership

LIR Membership

Alternative approach:

• Become RIPE NCC LIR member
• Receive PA allocation (includes last /22 of IPv4)
• Allocate to your own infrastructure
• Full control over address space

Requirements:

• Higher annual costs (€1,400+ membership)
• Additional responsibilities
• Policy compliance obligations
• More complex administration

Summary: Key Requirements for IPv4 PI

Historical eligibility criteria (for existing holders and transfers):

• Multi-homing intent or capability
• Own infrastructure use only
• At least one network element in RIPE region
• Legitimate need for provider-independent addressing
• Minimum /24 size
• Detailed technical justification

Current acquisition reality:

• No new assignments from RIPE NCC (except IXPs)
• Transfer market primary source
• Recipients must meet original eligibility criteria
• Contractual relationship with RIPE NCC required
• Annual fees: €75 plus sponsoring LIR costs

Ongoing obligations:

• Maintain multi-homing capability
• Use for own infrastructure only
• Keep RIPE Database current
• Pay annual maintenance fees
• Comply with RIPE policies
• Respond to audits

Frequently Asked Questions

Can I still get a new IPv4 PI assignment from RIPE NCC?

No, except for Internet Exchange Points. RIPE NCC no longer assigns IPv4 PI space to end-user organizations due to IPv4 address exhaustion. You must obtain IPv4 PI through the transfer market.

What if I don't plan to multi-home immediately?

Historically, RIPE accepted multi-homing intent with concrete implementation plans. For transfers, you should demonstrate multi-homing capability even if not immediately implemented. However, requirements may be more flexible for transfers than original assignments were.

Can I use IPv4 PI addresses for customers in my data center?

Only if those customers are using your infrastructure as colocation or hosting customers where you maintain control. You cannot sub-assign PI space to customers as an ISP would. The customers use addresses assigned to your infrastructure, not independently allocated to them.

How do I find IPv4 PI space to purchase?

Check RIR transfer listings for available resources, contact current IPv4 holders directly, or work with Via-Registry for assistance in locating suitable IPv4 PI blocks through our transfer facilitation services.

What happens if I stop multi-homing my IPv4 PI space?

Technically, you no longer meet the original assignment criteria. RIPE NCC may inquire during audits. In practice, enforcement varies, but maintaining multi-homing capability (even if not actively using multiple ISPs at all times) is advisable.

Can I transfer my IPv4 PI to someone outside the RIPE region?

Inter-RIR transfers have specific policies. Some RIRs accept transfers from RIPE, but requirements vary. This is more complex than intra-RIPE transfers and requires coordination between both RIRs.

Do IPv4 PI addresses need to be globally routed?

Not required by RIPE policy, but typically the purpose of PI addressing. RIPE explicitly states that assignment doesn't guarantee routing. Ensure proper BGP configuration, IRR registration, and RPKI implementation to maximize routing acceptance.

Next Steps

If you need IPv4 PI address space:

Understand PI resources fully: Read our comprehensive guide on Understanding Provider Independent (PI) Resources.

Explore the transfer market: Contact Via-Registry for assistance in:

• Locating available IPv4 PI blocks
• Negotiating transfers
• Managing transfer documentation
• Obtaining RIPE NCC approval

Consider alternatives: Evaluate if IPv6 PI, PA addresses, or LIR membership better suits your needs.

Plan your network: Document your multi-homing architecture, infrastructure requirements, and address utilization plans.

Via-Registry provides comprehensive support for IPv4 PI acquisition and management. Contact our team to discuss your specific requirements and explore available options.

Learn more about our IPv4 PI Resources Service.

---

This article is part of our comprehensive resource library on IP addressing and Internet resources. For personalized guidance on IPv4 PI requirements and acquisition, contact our team or explore our service offerings.