• ARIN's IPv6 guidance starts from a settled fact: the free pool of IPv4 addresses is depleted.
  • The registry publishes a request path through ARIN Online, sizing help in Your First IPv6 Request, implementation case studies and planning material.
  • Section 4.10 of ARIN's Number Resource Policy Manual provides one /24 every six months for IPv6 transition work. It is a bridge, not a general IPv4 supply.

What ARIN actually publishes

ARIN's IPv6 Information page is not a launch announcement. It is a standing guide for operators who need to request IPv6 address space and, over time, move networks from IPv4. The page states the premise directly: because the free pool of IPv4 addresses has been depleted, customers should request IPv6 space for new networks and eventually transition existing networks.

It describes IPv6 as the successor to IPv4: a much larger address pool, many more connectable devices, improved addressing and routing. Then it gives the operational sequence: research and plan; decide how much space to request; submit the request through ARIN Online; implement IPv6 on hardware and applications. Your First IPv6 Request handles sizing. Case studies collect experience from ISPs, hosting providers, enterprise businesses, universities and governments. Planning notes, a CIDR chart and a Business Case for IPv6 series sit alongside.

The transition reserve, precisely

ARIN keeps an IPv4 reserve dedicated to IPv6 transition support. The policy reference is Section 4.10 of the Number Resource Policy Manual. Qualifying networks can receive one /24 every six months to support transition work. That detail matters because it limits what the reserve can do: it is a bridge for dual-stack operations while services move, not a substitute for a normal IPv6 allocation or a general supply of IPv4 addresses.

Cost signals and a dated item to check

ARIN states that IPv6 is easy to obtain, that ISPs generally face no additional costs, and that fees were recently reduced for end users. It also warns that staying IPv4-only carries extra costs that will likely increase over time. Those are cost signals, not a forecast of any specific operator's bill.

ARIN's 2026 announcement archive adds a dated item for planning: it lists a notice that ARIN's IPv6 Fee Waiver expires on 31 December 2026. The listing is a prompt to check eligibility and timing against ARIN's own fee and waiver documentation. It does not state how any particular network will be charged.

Why the registry record matters

IANA's IPv4 Address Space registry shows the 256 /8 blocks with statuses including ALLOCATED, LEGACY and RESERVED. ARIN appears there as an allocating registry for newer blocks and as administrator for many legacy assignments. The structural point is simple: the IPv4 supply is fixed and already distributed. IPv6 does not change that history; it gives operators a different address space to plan around.

What this means for operators

For a network team, the expensive moment is rarely the request itself. It is discovering during a new network build, a hosting migration or an application rollout that equipment, software and support processes were never prepared for dual stack. ARIN's page points to the preparatory work: make sure equipment, software and staff are ready, estimate how many addresses are needed, and design the network before implementation.

The useful operational reading is therefore a sequence, not a slogan. Inventory applications. Decide who owns routing policy and support. Size the IPv6 request against the network plan. Treat the transition /24 as a bridge. Then test the implementation with the same care the registry describes in its case studies. A registry page cannot make that plan for an organization, but it does define the points that a credible plan has to answer.