IPv6 Address Allocation
Secure unlimited IPv6 addresses for future-proof network infrastructure
IPv6 Address Allocation: Future-Proof Your Network
IPv4 is exhausted. IPv6 offers 340 undecillion addresses (3.4×10³⁸) - enough for every device on Earth and beyond. Get your IPv6 allocation now.
Part of our comprehensive Registry Services
Block Sizes
/48 to /32 blocks
1-2 Weeks
Typical allocation
Free Allocation
RIPE NCC policy
TL;DR Summary
Provider Independent IPv6 /48 or /44 allocation with full routing support.
Why IPv6?
The transition to IPv6 is inevitable. RIPE NCC exhausted its IPv4 pool in November 2019. IPv6 provides virtually unlimited addresses and significant technical advantages.
IPv4 Exhaustion
All five Regional Internet Registries have exhausted their IPv4 pools. New networks require IPv6 or expensive IPv4 transfers.
340 Undecillion Addresses
IPv6 provides 2¹²⁸ addresses - 340,282,366,920,938,463,463,374,607,431,768,211,456 unique addresses. Enough for 670 quadrillion addresses per square millimeter of Earth's surface.
Native Modern Support
All modern operating systems, devices, and infrastructure fully support IPv6. Major ISPs, CDNs, and cloud providers run IPv6 natively.
Built-In Security
IPsec is mandatory in IPv6 specifications. No NAT means end-to-end connectivity with proper firewall policies. Simplified network security architecture.
Simpler Routing
No NAT traversal issues. Hierarchical addressing structure improves routing efficiency. Auto-configuration (SLAAC) reduces management overhead.
Better Performance
Stateless address auto-configuration. Improved multicast capabilities. Simplified header structure for faster packet processing.
Available IPv6 Block Sizes
RIPE NCC allocates IPv6 blocks based on network requirements.
All allocations are free of charge.
| Block Size | Available Subnets | Typical Use Case | Delivery |
|---|---|---|---|
| /48 | 65,536 /64 subnets | Small ISP, enterprise network, datacenter | 1-2 weeks |
| /44 | 1,048,576 /64 subnets | Medium ISP, multiple datacenter locations | 1-2 weeks |
| /40 | 16,777,216 /64 subnets | Large ISP, national network operator | 2-3 weeks |
| /32 | 65,536 /48 blocks | Very large ISP, regional provider | 2-3 weeks |
Each /64 subnet provides 18,446,744,073,709,551,616 host addresses. IPv6 allocations are free per RIPE policy.
IPv6 Allocation Process
We handle the complete RIPE NCC allocation process on your behalf
Requirements Analysis
Document current network size, growth projections, and IPv6 deployment plan
RIPE Submission
Submit allocation request to RIPE NCC with justification and network plan
RIPE Approval
RIPE NCC reviews and approves allocation based on demonstrated need
Allocation & Configuration
Receive IPv6 block, configure reverse DNS, setup ROA, and implement routing
Total timeline: 1-2 weeks from submission to full deployment
RIPE NCC Requirements
IPv6 allocations require documented justification and deployment plan
RIPE NCC policy requires demonstration of current IPv6 need or detailed deployment plan within 24 months.
Documentation Required
- Network infrastructure description
- Current IPv4 usage statistics
- IPv6 deployment timeline (24 months max)
- Addressing plan showing subnet hierarchy
- Number of end-sites requiring assignments
- LIR membership or sponsorship arrangement
Allocation Criteria
- Plan to provide IPv6 to customers/infrastructure within 24 months
- Documented addressing architecture
- Justification for requested block size
- Compliance with RIPE NCC IPv6 policy (ripe-733)
Full allocation policy available at RIPE NCC
Dual-Stack Implementation
Run IPv4 and IPv6 simultaneously for seamless transition
Dual-stack networking allows your infrastructure to support both IPv4 and IPv6, ensuring compatibility during the global transition period.
Deployment Strategies
- Enable IPv6 on all network infrastructure (routers, switches, firewalls)
- Configure dual-stack routing (BGP for both address families)
- Implement Happy Eyeballs (RFC 8305) for automatic protocol selection
- Deploy IPv6-capable DNS servers with AAAA records
- Update monitoring systems to track both protocols
- Configure separate or combined firewall policies
Dual-Stack Benefits
- Zero service disruption during transition
- Maintain IPv4 compatibility while deploying IPv6
- Gradual migration path reduces risk
- Automatic fallback if one protocol fails
- Support legacy applications and clients
- Future-proof infrastructure investment
We recommend dual-stack deployment for all production networks. This provides maximum compatibility while building IPv6 expertise.
Technical Specifications
What's included with IPv6 allocation
Allocation Details
- RIPE NCC allocated PI or PA space
- Free of charge per RIPE policy
- Minimum /48 allocation (typical)
- Larger blocks based on justified need
- Global BGP routing visibility
Included Services
- Reverse DNS (PTR) zone delegation
- ROA (Route Origin Authorization) setup
- RIPE database object creation
- IPv6 BGP session configuration
- Dual-stack implementation guidance
Ongoing Support
- Addressing plan consultation
- Subnet hierarchy design
- Routing policy configuration
- Monitoring setup assistance
- RIPE NCC policy compliance
IPv6 vs IPv4: Technical Comparison
Understanding the key differences
IPv6
Pros
- ✓340 undecillion addresses available
- ✓Free allocation via RIPE NCC
- ✓Mandatory IPsec support
- ✓No NAT required - end-to-end connectivity
- ✓Simplified routing tables
- ✓Auto-configuration (SLAAC)
- ✓Better multicast support
- ✓Mobile IPv6 built-in
Cons
- ✗Not all legacy systems support IPv6
- ✗Requires dual-stack during transition
- ✗Learning curve for administrators
- ✗Some older software incompatible
New deployments, modern infrastructure, future-proof networks
IPv4
Pros
- ✓Universal compatibility
- ✓Established tooling and knowledge
- ✓No transition complexity
Cons
- ✗Exhausted address space
- ✗Expensive to acquire (€30-50+ per IP)
- ✗Requires complex NAT solutions
- ✗Increasingly scarce
- ✗Ongoing transfer costs
Legacy system support, specific application requirements
Deploy dual-stack: Use IPv6 as primary with IPv4 fallback. This provides maximum compatibility while positioning for the IPv6-only future.
IPv6 Use Cases
Common scenarios requiring IPv6 allocation
Internet Service Provider
Provide IPv6 connectivity to residential and business customers. Required for modern ISP operations.
/32 to /48 block depending on customer base. Dual-stack deployment with DHCPv6 or SLAAC.
Hosting & Cloud Provider
Offer IPv6-enabled hosting services. Essential for modern web applications and compliance with mobile carrier requirements.
/48 block for multiple datacenter locations. IPv6-capable control panel and DNS management.
Enterprise Network
Deploy IPv6 across corporate infrastructure. Prepare for IPv4 cost increases and address exhaustion.
/48 block for hierarchical addressing. Dual-stack deployment with gradual service migration.
Datacenter Operations
Provide IPv6 addresses to colocation customers and managed infrastructure. Differentiate from IPv4-only competitors.
/44 to /48 block. Automated provisioning and reverse DNS delegation for customers.
Frequently Asked Questions
Common questions about IPv6 allocation
Request Your IPv6 Allocation
Need assistance with IPv6 deployment planning?
Our technical team handles all aspects of IPv6 allocation and implementation.
Or view IPv4 allocation options