Understanding Provider Independent (PI) Resources

Provider Independent (PI) resources represent a critical component of Internet infrastructure, offering organizations the ability to maintain their IP address space independently of their Internet Service Provider. This comprehensive guide explores what PI resources are, how they differ from Provider Aggregatable (PA) addresses, and what you need to know about obtaining and managing them.

What are Provider Independent Resources?

Provider Independent (PI) resources are IP address blocks assigned directly by a Regional Internet Registry (RIR) to end-user organizations. Unlike Provider Aggregatable (PA) addresses that come from an Internet Service Provider's allocation, PI resources remain with the organization regardless of which provider they use for connectivity.

The defining characteristic of PI resources is portability. When you hold PI address space, you can:

Switch Internet Service Providers without renumbering your network
Use multiple ISPs simultaneously (multi-homing)
Maintain consistent IP addressing across your infrastructure
Build a stable, provider-independent network architecture

PI resources include both IPv4 and IPv6 address assignments, as well as Autonomous System Numbers (ASNs). This guide focuses primarily on PI address space.

The Evolution of PI Resources

Provider Independent addressing emerged as a solution to a fundamental Internet infrastructure challenge. In the early days of the Internet, organizations that changed ISPs faced the costly and disruptive task of renumbering their entire network infrastructure.

Historical Context

The concept of PI addressing developed alongside the growth of the commercial Internet in the 1990s. As businesses became increasingly dependent on Internet connectivity, the need for stable, portable address space became apparent. Organizations needed:

Business continuity: The ability to change providers without service disruption
Multi-homing capabilities: Connection to multiple ISPs for redundancy
Long-term stability: Addresses that wouldn't need to change as business relationships evolved

Current State: IPv4 Exhaustion

The landscape for PI resources changed dramatically with IPv4 address exhaustion. The RIPE NCC, which serves Europe, the Middle East, and parts of Central Asia, depleted its available pool of IPv4 addresses and no longer assigns new IPv4 PI space.

As stated in RIPE NCC documentation: "As the RIPE NCC has run out of IPv4 addresses, no new IPv4 PI address space can be assigned."

This scarcity has created a secondary market for IPv4 addresses and made existing PI assignments particularly valuable. Organizations seeking IPv4 PI space must now:

Purchase or lease existing PI assignments through RIR-governed transfers
Contact current holders or work with transfer facilitation services
Consider IPv6 deployment as an alternative or complement

IPv6 PI assignments, by contrast, remain readily available through the standard application process.

PI vs PA: Understanding the Fundamental Differences

The distinction between Provider Independent (PI) and Provider Aggregatable (PA) address space is fundamental to understanding Internet addressing architecture.

Provider Aggregatable (PA) Addresses

PA addresses are allocated to Local Internet Registries (LIRs) - typically Internet Service Providers - who then sub-allocate or assign them to their customers.

Key characteristics of PA addresses:

Source: Assigned from an LIR's allocation
Aggregation: Designed to be aggregated into larger routing blocks
Portability: Not portable - tied to the provider
Dependency: Assignment ends when service agreement terminates
Routing efficiency: Reduces global routing table size through aggregation

According to RIPE policy: "Assignment of this IP space is valid as long as the criteria for the original assignment are met and only for the duration of the service agreement between yourself and us."

Provider Independent (PI) Addresses

PI addresses are assigned directly by the RIR or through a sponsoring LIR on behalf of the RIR.

Key characteristics of PI addresses:

Source: Assigned directly by the RIR (not from LIR allocation)
Independence: Remain with the organization regardless of provider
Portability: Can be used with any ISP
Persistence: Assignment continues as long as original criteria are met
Routing considerations: Each PI block requires separate routing table entries

The Trade-offs

The choice between PI and PA involves several important trade-offs:

Routing table impact: PA addresses support Internet routing efficiency through aggregation. A single routing table entry might cover thousands of PA assignments. PI addresses, by contrast, typically require individual routing table entries.

As RIPE notes: "The advantage of PA addresses is that the routing information for many customers can be aggregated once it leaves the provider's routing domain."

Routing acceptance: Network operators throughout the Internet make independent decisions about which routes to accept. While PA addresses from known providers are universally routed, PI addresses may face filtering.

RIPE warns: "The disadvantage of [PI addresses] is that networks operators throughout the Internet may choose not to route them."

Flexibility vs. efficiency: PI addresses offer maximum flexibility for the organization but at the cost of Internet routing efficiency. PA addresses optimize global routing but create provider dependency.

Cost considerations: PI resources require direct contractual relationships with the RIR or sponsoring LIR, including annual maintenance fees. PA addresses are typically included in ISP service costs.

IPv4 Provider Independent Resources

IPv4 PI assignments represent the original and most widely deployed form of Provider Independent addressing.

Historical IPv4 PI Assignments

Before IPv4 exhaustion, organizations could request IPv4 PI assignments directly from RIPE NCC by demonstrating:

A legitimate need for the address space
That the addresses would be used for their own infrastructure
A plan for how the space would be utilized

Typical IPv4 PI assignment sizes ranged from /24 (256 addresses) to /20 (4,096 addresses) or larger, depending on justified need.

Current IPv4 PI Availability

New assignments: The RIPE NCC no longer assigns new IPv4 PI space due to address exhaustion. The last unreserved IPv4 addresses from the RIPE NCC were distributed in November 2019.

Existing assignments: Organizations holding existing IPv4 PI assignments maintain their rights to those addresses as long as they meet the ongoing requirements and pay annual fees.

Transfer market: Organizations needing IPv4 PI space must now obtain it through transfers. RIPE Policy 2014-02 allows PI holders to transfer their assignments to other organizations within the RIPE service region.

IPv4 PI Use Cases

IPv4 PI addresses remain essential for:

Multi-homed networks: Organizations connected to multiple ISPs for redundancy use PI space to advertise their own prefixes via BGP, enabling traffic engineering and failover capabilities.

Data centers and hosting providers: Facilities offering colocation and hosting services maintain stable IP addressing for customers regardless of upstream connectivity changes.

Content delivery networks: Organizations with distributed infrastructure across multiple locations and providers rely on PI space for consistent addressing.

Enterprise networks: Large organizations with mission-critical Internet presence use PI addresses to ensure business continuity.

IPv4 PI Requirements and Restrictions

Organizations holding IPv4 PI assignments must:

Maintain a contractual relationship with RIPE NCC (directly or through a sponsoring LIR)
Use the addresses only for their own infrastructure
Keep registration information accurate in the RIPE Database
Pay annual maintenance fees (€75 per assignment as of 2025)

Critical restriction: IPv4 PI addresses "can only be used for the end user's own infrastructure and can't be leased out." This prevents PI holders from operating as informal ISPs.

IPv6 Provider Independent Resources

IPv6 PI assignments offer the same provider independence as IPv4 PI but within the vast IPv6 address space.

IPv6 PI Assignment Sizes

The minimum IPv6 PI assignment is a /48 prefix, providing 65,536 /64 subnets - more than sufficient for most organizational needs.

From RIPE Policy: "The minimum size of the assignment is a /48."

Larger assignments: Organizations requiring more than a /48 can request shorter prefixes (larger blocks) by documenting:

Additional subnet requirements
Special routing needs for multiple sites
Technical justification for the larger space

RIPE policy allows: "Assignments larger than a /48 (shorter prefix) or additional assignments exceeding a total of a /48 must be based on address usage or because different routing requirements exist for additional assignments."

IPv6 PI Eligibility

Organizations can request IPv6 PI assignments if they:

Plan to use the addresses for their own infrastructure
Are not ISPs offering broadband services to customers
Can demonstrate a legitimate need for provider-independent addressing
Meet the contractual requirements for PI resource holders

IPv6 PI Permitted Uses

RIPE policy specifies acceptable uses for IPv6 PI assignments:

Organization infrastructure: Corporate networks, office locations, and IT infrastructure
Software-as-a-Service platforms: SaaS providers using addresses for their own service delivery
Public WiFi hotspots: Guest network access at organization facilities
Point-to-point links: Connections with third-party organizations
Customer server connections: Hosting infrastructure for customer equipment
Internet Exchange Points: IXP infrastructure
Time-limited purposes: Research projects, academic studies, temporary networks

IPv6 PI Prohibited Uses

Organizations cannot use IPv6 PI assignments for:

ISP broadband services: Providing Internet access to residential or business customers
Large networks with separate legal entities: Multi-organization networks without individual assignments
Governmental networks: Government entities providing connectivity to other organizations
Pure colocation services: Facility providers assigning space to hosted customers
Sub-assignment to other organizations: Allocating subnets to independent entities

The key distinction is that PI space must be used for the organization's own infrastructure, not re-distributed to customers or other entities.

Contractual Requirements for PI Resource Holders

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

Direct Assignment Agreement

PI resource holders must establish a contractual relationship with RIPE NCC either:

Directly: Through a direct "Independent Assignment Request and Maintenance Agreement"
Via sponsoring LIR: Through an existing RIPE NCC member organization

Sponsoring LIR Model

Most organizations obtain PI resources through a sponsoring LIR, which:

Submits the PI assignment request on the organization's behalf
Maintains the contractual relationship with RIPE NCC
Handles administrative tasks and fee collection
Provides ongoing support for resource management

The sponsoring LIR model offers advantages:

Lower entry barrier (no direct RIPE membership required)
Simplified administrative processes
Professional support for technical requirements
Consolidated billing and management

Annual Maintenance Fees

PI resource holders pay annual fees to RIPE NCC for resource maintenance. As of 2025:

IPv4 and IPv6 PI assignments: €75 per assignment annually
Autonomous System Numbers: €50 per ASN annually

These fees support RIPE NCC operations, policy development, and registry maintenance.

Ongoing Obligations

PI resource holders must:

Maintain accurate data: Keep registration information current in the RIPE Database
Comply with policies: Use resources in accordance with RIPE community policies
Respond to RIPE NCC: Address inquiries and audit requests promptly
Pay fees on time: Maintain accounts in good standing

Failure to meet these obligations can result in resource recovery.

The Application Process for PI Resources

Obtaining PI resources involves several steps and specific documentation requirements.

Step 1: Find a Sponsoring LIR

Unless you are already a RIPE NCC member LIR, you need a sponsoring LIR to submit your PI assignment request.

Selecting a sponsoring LIR involves considering:

Experience with PI assignment requests
Quality of support and documentation assistance
Fee structure and ongoing service costs
Reputation and relationship with RIPE NCC

Step 2: Determine Your Requirements

Clearly define your PI resource needs:

For IPv6 PI:

Standard /48 for most organizations
Larger assignment if you can justify additional subnets or routing requirements
Multiple /48s if you have distinct sites with different routing needs

For IPv4 PI:

Identify specific size requirements
Locate available PI space on transfer market
Negotiate transfer with current holder

Step 3: Prepare Documentation

Gather required documentation:

Legal verification:

Organizations: Business registration documents, articles of incorporation
Individuals: Passport or valid ID document (verified through third-party service iDenfy)

Technical justification:

Network topology and architecture diagrams
Subnet utilization plans (for requests larger than /48)
Routing requirements documentation
Infrastructure descriptions

Contractual documents:

Signed "Independent Assignment Request and Maintenance Agreement"
For temporary needs: "Temporary Assignment Request and Maintenance Agreement"

Step 4: Create RIPE Database Objects

Before submitting your request, establish presence in the RIPE Database:

Organization object: Represents your legal entity
Maintainer object (mntner): Controls access to your database objects
Person/role NIC handle: Contact information for administrative and technical roles

Step 5: Submit Application

Your sponsoring LIR submits the application through the RIPE NCC portal at https://my.ripe.net/

The submission includes:

Completed request forms
All supporting documentation
Legal verification materials
Technical justifications

Step 6: RIPE NCC Review

RIPE NCC evaluates the request based on:

Policy compliance
Documentation completeness
Technical justification adequacy
Legal verification results

Review timeline: Standard requests typically receive initial review within 5 business days. Complex requests requiring additional documentation may take longer.

Step 7: Assignment and Registration

Upon approval:

RIPE NCC assigns the PI resources
Resources are registered in the RIPE Database
Organization can begin using the address space
Routing can be configured with ISPs

Managing Your PI Resources

Successful PI resource management requires ongoing attention to several areas.

RIPE Database Maintenance

Keep your RIPE Database objects current:

Contact information: Ensure administrative and technical contacts are accurate
Network topology: Update inet6num/inetnum objects as your infrastructure evolves
Routing policies: Maintain accurate route and route6 objects for BGP
Authorization: Keep maintainer credentials secure and accessible

Routing Considerations

Successfully routing PI address space requires:

BGP configuration: Most PI resource holders need:

An Autonomous System Number (ASN)
BGP peering relationships with one or more ISPs
Proper route origin authorization (ROA) using RPKI

ISP coordination: Work with your upstream providers to:

Establish BGP sessions
Configure route advertisements
Implement traffic engineering policies
Test failover scenarios (for multi-homed setups)

Route filtering: Be aware that some networks implement filtering policies that may affect PI address reachability:

Minimum prefix length filters
Regional routing policies
Provider-specific filtering rules

Compliance and Audits

RIPE NCC may conduct audits to verify:

Resources are being used as documented
Registration information is accurate
Policy requirements are met
No unauthorized sub-assignments have occurred

Respond promptly and thoroughly to audit requests with:

Current network topology documentation
Evidence of legitimate use
Updated registration information
Clarification of any questions

Fee Management

Maintain your PI resources by:

Paying annual fees on time
Keeping billing information current
Coordinating with your sponsoring LIR if using that model
Budgeting for potential fee increases

PI Resources and Multi-Homing

One of the primary drivers for obtaining PI resources is multi-homing - connecting to multiple Internet Service Providers simultaneously.

Why Multi-Home?

Organizations implement multi-homing for:

Redundancy: If one ISP experiences an outage, traffic automatically routes through other connections, maintaining Internet availability.

Performance optimization: Use BGP traffic engineering to direct traffic through optimal paths based on latency, capacity, or cost.

Provider independence: Avoid vendor lock-in by maintaining the ability to easily add, remove, or change ISPs.

Load distribution: Distribute traffic across multiple links to maximize available bandwidth.

Multi-Homing Requirements

Effective multi-homing with PI resources requires:

Autonomous System Number: Your own ASN to identify your network in BGP routing.

BGP capabilities: Router hardware and technical expertise to configure and maintain BGP sessions.

PI address space: Provider-independent addresses that you control and can announce from any ISP.

Multiple ISP connections: Physical connectivity to two or more Internet providers.

Multi-Homing Architecture

A typical multi-homed setup includes:

Edge routers: BGP-capable routers at each ISP connection point
Interior routing: OSPF, EIGRP, or static routes within your network
BGP configuration: Sessions with each ISP, route advertisements, and policy implementation
Monitoring: Tools to track routing, detect issues, and measure performance

Common Challenges and Solutions

Organizations working with PI resources often encounter specific challenges.

Challenge 1: Routing Acceptance

Problem: Some networks filter PI routes, potentially limiting reachability.

Solution:

Work with well-connected ISPs who have strong peering relationships
Ensure your routes are properly registered in routing databases (IRR)
Implement RPKI ROAs to validate your route origins
Announce appropriately-sized prefixes (avoid excessive deaggregation)

Challenge 2: IPv4 Scarcity

Problem: No new IPv4 PI space available from RIPE NCC.

Solution:

Explore the IPv4 transfer market
Work with experienced brokers to locate available PI blocks
Consider IPv6 deployment as primary addressing strategy
Evaluate leasing options for temporary needs

Challenge 3: Technical Complexity

Problem: Managing PI resources and BGP routing requires specialized expertise.

Solution:

Partner with experienced sponsoring LIRs who provide technical support
Invest in staff training on BGP and Internet routing
Use managed services for BGP configuration and monitoring
Implement robust change management processes

Challenge 4: Documentation Requirements

Problem: RIPE NCC requests require detailed technical justification and documentation.

Solution:

Start documentation early in the planning process
Create clear network diagrams and topology maps
Document business requirements and use cases
Work with your sponsoring LIR to review submissions before filing

Challenge 5: Ongoing Compliance

Problem: Maintaining compliance with PI resource policies and audit requirements.

Solution:

Establish regular review processes for resource usage
Keep detailed records of network changes and expansions
Maintain current contact information in all databases
Set reminders for annual fee payments and renewal dates

Using Via-Registry for PI Resources

Via-Registry simplifies the entire PI resource lifecycle with comprehensive services:

Application Support

We guide you through the complete application process:

Requirements assessment and planning
Documentation preparation and review
Technical justification development
Application submission and follow-up

Sponsoring LIR Services

As an experienced RIPE NCC member, we provide:

Sponsoring LIR services for PI assignments
Direct liaison with RIPE NCC
Ongoing administrative support
Fee management and billing coordination

IPv6 PI Assignments

Get your IPv6 PI resources through our streamlined process:

Standard /48 assignments typically approved within 1-2 weeks
Support for larger assignments with proper justification
Complete technical documentation assistance
RIPE Database setup and configuration

Learn more about our IPv6 PI Resources Service.

IPv4 PI Transfers

Navigate the IPv4 transfer market with expert guidance:

IPv4 PI block identification and sourcing
Transfer process management
Documentation and approval support
Post-transfer registration and configuration

Explore our IPv4 PI Resources Service.

Ongoing Management

We provide continued support for your PI resources:

Annual maintenance and fee management
RIPE Database updates and maintenance
Compliance support and audit assistance
Technical consulting for routing and BGP

Frequently Asked Questions

What's the difference between PI and PA addresses?

PI (Provider Independent) addresses are assigned directly by the RIR and remain with your organization regardless of ISP. PA (Provider Aggregatable) addresses come from your ISP's allocation and must be returned if you change providers. PI offers portability and independence; PA offers routing efficiency and typically lower costs.

Can I still get IPv4 PI addresses?

Not directly from RIPE NCC. IPv4 exhaustion means no new IPv4 PI assignments are available. However, you can obtain IPv4 PI space through the transfer market by purchasing existing assignments from current holders.

How much does an IPv6 PI assignment cost?

The RIPE NCC annual maintenance fee is €75 per assignment (as of 2025). Additionally, your sponsoring LIR will charge service fees for application support and ongoing management. Total costs vary by provider but typically range from €200-500 annually including all fees.

Do I need my own ASN to use PI addresses?

Not strictly required, but highly recommended. PI addresses offer maximum value when combined with your own ASN for BGP routing, enabling multi-homing and provider independence. You can technically use PI space with static routing through a single ISP, but this negates most PI benefits.

How long does it take to get an IPv6 PI assignment?

With complete documentation, standard IPv6 PI assignment requests typically receive approval within 1-2 weeks. The timeline depends on documentation quality, justification completeness, and current RIPE NCC workload. Complex requests for larger assignments may take longer.

Can I subdivide my PI assignment to other organizations?

No. RIPE policy explicitly prohibits sub-assignment of PI resources to other organizations. PI space must be used exclusively for your own infrastructure. If you need to provide addresses to customers, you should become an LIR and obtain PA allocation instead.

What happens if I no longer need my PI assignment?

You should return the PI resources to RIPE NCC. This terminates your maintenance fees and allows the address space to be reclaimed for future use. For IPv4 PI, you may alternatively transfer the assignment to another organization through the transfer process.

Will my PI addresses be routed globally?

Likely, but not guaranteed. Network operators make independent routing decisions. Most well-connected ISPs route properly-registered PI addresses. To maximize routing acceptance: use reputable ISPs, implement RPKI, maintain accurate IRR records, and announce appropriately-sized prefixes.

Summary

Provider Independent (PI) resources offer critical capabilities for organizations requiring stable, portable IP address space:

Independence: Maintain your addresses regardless of ISP relationships
Flexibility: Switch providers, implement multi-homing, and control your routing
Stability: Build infrastructure on addresses that won't change
IPv4 reality: New IPv4 PI assignments unavailable; transfer market active
IPv6 availability: IPv6 PI readily available through standard application process
Requirements: Contractual relationship with RIPE NCC, annual fees, policy compliance
Trade-offs: Routing considerations vs. provider independence benefits

Next Steps

Ready to obtain PI resources for your organization?

Assess your needs: Determine whether IPv4 PI, IPv6 PI, or both suit your requirements
Plan your network: Document topology, routing needs, and infrastructure plans
Find support: Partner with an experienced sponsoring LIR like Via-Registry
Begin the application: Gather documentation and start the assignment process

Via-Registry provides comprehensive support for all aspects of PI resource acquisition and management. Contact our team to discuss your specific requirements.