Skip to content
Networks

Services

Lease IPv6 address space

IPv6 allocations from a /48 upward, provisioned alongside your IPv4 or on their own. No scarcity premium and no waiting list. Dual-stacking is usually the cheaper way to scale.

Why now

Why take IPv6 now

The economics run the opposite way to IPv4, which is the whole point.

  • No scarcity premium

    IPv6 is abundant, so you are not paying the per-address market rate that makes IPv4 expensive. For most deployments the allocation costs a fraction of the equivalent IPv4 footprint.

  • Takes pressure off your IPv4

    Every service you dual-stack is one that no longer needs another IPv4 address. Growing on IPv6 is usually cheaper than buying or leasing more IPv4 to keep up.

  • Increasingly expected

    Large mobile networks and cloud platforms are IPv6-first in several regions. Dual-stacking removes a class of reachability problem before it reaches your support queue.

Sizes

Allocation sizes

Standard allocations. Larger on request; tell us the deployment and we will size it.

Prefix/64 subnetsTypical use
/4865,536A single site or end customer
/441,048,576Several sites, or downstream assignment
/4016,777,216Large deployments and hosting platforms

Need something larger than a /40? Ask, because IPv6 space is not the constraint.

Included

What comes with it

The same handling as our IPv4 leases, with nothing held back for a higher tier.

  • Reverse DNS delegation
  • Direct support, no ticket queue
  • RPKI / ROA configured for the prefix
  • Letter of Authorization for your announcement
  • Allocation from our own RIPE NCC address space
  • Announce via your own ASN, your data center's, or one of our tunnels

How it works

How it works

  1. 01

    Tell us the deployment

    The size you need, from a /48 upward, and how you will route it: with your own ASN, your data center's, or through one of our tunnels.

  2. 02

    We allocate and configure

    The prefix comes from our own allocation at the RIPE NCC, with its Letter of Authorization, RPKI/ROA and reverse DNS set up for you.

  3. 03

    You announce it

    Your upstream accepts the announcement under the LOA, exactly as with IPv4. Dual-stack one service at a time: each one stops needing another IPv4 address.

Contact

Need an IPv6 allocation?

Tell us the size you need, from a /48 upward, and how you plan to route it. We usually reply in 1-3 business hours.

Contact us

FAQ

IPv6 questions

Do I need IPv6 if my IPv4 works fine?

Not urgently, but it is cheaper to add now than to keep buying IPv4 as you grow. The usual trigger is either cost, since IPv4 per-address pricing starts to hurt at scale, or a reachability complaint from users on an IPv6-only mobile network.

What size should I take?

A /48 is the standard site allocation and is enough for most single deployments, since it still contains 65,536 /64 subnets. Take a /44 or /40 if you assign space downstream to customers or run many separate sites. If you are unsure, describe the deployment and we will suggest a size.

Can I announce it with my own ASN?

Yes. We issue a Letter of Authorization for the prefix and your upstream accepts the announcement, exactly as with IPv4. If you have no ASN, your provider can usually announce on theirs, or you can route it through one of our tunnels.

Does it work over a GRE or WireGuard tunnel?

Yes. We can deliver IPv6 over the same tunnel setup we use for IPv4, so a single endpoint can carry both. Worth mentioning up front so we configure it in one pass.

How is IPv6 priced against IPv4?

Far lower, because the scarcity that drives IPv4 pricing does not apply. We quote per allocation rather than per address. Tell us the size and duration and we will come back with a price.