Skip to main content
ELISTEKA Network Resources
IPv6 /32Lease IPv4Sell or Buy IPv4Pricing
Sponsoring LIRASN and PIManaged LIRIP delisting
ToolsGuidesAbout
IPv6 /32Lease IPv4Sell or Buy IPv4Pricing
Sponsoring LIRASN and PIManaged LIRIP delisting
ToolsGuidesAbout

IPv6 guides

How to lease a RIPE IPv6 /32: costs and requirements

ELISTEKA · 26 September 2026

Short answer: A RIPE IPv6 /32 lease gives an eligible network operator the agreed use of a prefix, not ownership or connectivity. Confirm intended use, origin ASN and an upstream that will accept the announcement before applying.

Start with the network you want to operate

A leased IPv6 prefix gives your business the agreed right to use address space for a defined term. It does not include ownership of the resource. Before requesting a /32, describe the services, sites or customers it will support and confirm that your upstream can carry your proposed IPv6 announcement.

ELISTEKA supplies IPv6 address space and coordinates the agreed registry records and authorisations. Arrange connectivity with your network or upstream provider separately. If you need only one site, assess whether a smaller prefix from your connectivity provider would meet the requirement.

Check network fit · Questions for your upstream · Activation checks

Can I use a leased IPv6 /32 with my network?

Start with who will announce the prefix and how traffic reaches your network. Having IPv6 enabled on a server is not the same as being able to bring externally leased address space to that provider.

I operate an ASN and have IPv6 transit
Ask your upstream to confirm acceptance of the externally leased /32 from your origin ASN. Agree the BGP session, prefix filters and required documentation before provisioning.
My provider will announce the prefix for me
Confirm that it offers this arrangement, which ASN will originate the route and how it will deliver traffic to your network. The ROA and route6 object must match the agreed origin, which may be the provider’s ASN.
I have a VPS or dedicated server, but no BGP agreement
Ask about externally supplied address space or BYOIP support for your exact product and location. Do not assume that buying a prefix enables it on an existing server.
I do not have an ASN or an upstream yet
You can start with a technical-fit enquiry. Describe your intended use and any providers under consideration. An agreed origin and supported connectivity arrangement are needed before activation.

Check technical fit for your network. Share your ASN, or select “No ASN yet”, plus your upstream and intended use. This is an initial review, not a reservation or activation.

Questions to send your upstream before leasing

Use the following as a starting point for a support ticket. Replace the bracketed fields and ask for confirmation for your specific service, not just the provider’s network in general.

Subject: Externally leased IPv6 /32 — routing support for [service/location]

We are considering a RIPE IPv6 /32 lease for [intended use] on [service/location]. Our proposed origin ASN is [ASN / not yet arranged]. Before ordering, could you confirm:

  1. Does this service accept externally leased IPv6 space?
  2. Would we announce it through a customer BGP session, or would you originate the route? Which origin ASN should be authorised?
  3. Which prefix lengths do you accept, and are there limits on the number of announcements?
  4. What ROA, route6/IRR records and LOA do you require? How are filter updates requested?
  5. How will the prefix be routed to our equipment or virtual network?
  6. Are there setup or recurring charges, lead times or restrictions on the intended use?
  7. Who should coordinate activation, testing and eventual withdrawal?

If the provider cannot support the proposed setup, resolve connectivity first. The address-space lease alone cannot change its routing policy.

Is a /32 the right fit?

A /32 can contain 65,536 /48 prefixes before reserves. That capacity is useful when planning multiple sites or customer networks; it does not mean every application needs a /32. For a single site or server, first check the IPv6 space available from your connectivity provider.

Use the IPv6 lease fee calculator to compare the monthly and upfront fees for an IPv6 /32 or /29 (the /29 reference prices are €149 monthly or €1,608 for the annual prepayment). Address planning and global BGP announcements are separate decisions: allocating a /48 internally does not mean you must announce that /48 separately to the Internet.

What does the ELISTEKA /32 service cost?

One RIPE IPv6 /32 costs €29 per month, with a 3-month initial commitment. The first invoice is €87 upfront. After that period, continuation is €29 per month under the agreed service terms. Prices exclude VAT where applicable. See the current IPv6 /32 offer before ordering.

Budget separately for your connectivity and any network equipment or operational work. The prefix price alone does not describe the total cost of running an IPv6 network.

What is included, and what must you arrange?

Elisteka: address space and coordination
The agreed right to use one RIPE IPv6 /32, with origin-ASN, exact ROA, route6, LOA, applicable RIPE Database and reverse-DNS coordination reviewed during onboarding.
Your business: network operation
A technical contact, an agreed origin ASN, connectivity, router configuration, an addressing plan and operational handling of your services and abuse reports.
Your upstream: route acceptance
Confirmation that the proposed prefix and origin can be carried under its service, filtering and documentation requirements.

The standard offer is an address-space lease. It is not a bundled server, Internet transit connection or automatic ASN registration. Confirm any requirement outside the published scope before agreeing the service order.

Prepare these details before applying

  • Your legal company name, registration details and business contact.
  • Your intended use: for example, VPS hosting, an access network or infrastructure services.
  • The proposed origin ASN and the technical contact responsible for the announcement.
  • Your upstream arrangement and any documentation or filtering requirements it imposes.
  • Your reverse-DNS nameservers if you need delegation, and your preferred start date.

If the ASN or upstream arrangement is still being finalised, explain that in the application. An agreed origin ASN is required before activation; submitting an application does not itself reserve or activate a prefix.

From request to activation

  1. Request: submit your business and network information.
  2. Review: agree intended use, routing responsibility and the required records.
  3. Contract and payment: confirm the service order and invoice.
  4. Provisioning: coordinate the agreed ROA, route6 object, LOA and reverse DNS where applicable.
  5. Verification: check the records and the agreed routing arrangement before confirming activation.

Provisioning is reviewed manually. Timing depends on complete information and the agreed technical setup; there is no automatic activation promise.

What should be checked before using the prefix?

Keep one agreed handover record: prefix, origin ASN, announced lengths, upstream contact, record maintainers and activation date. Then check each layer separately:

  1. Authorisations: verify that the ROA permits the planned origin and announcement length, and that the route6 record matches the agreed route.
  2. Upstream acceptance: have the announcing operator confirm that the route is being exported and accepted. An established BGP session alone is not proof of route acceptance.
  3. External visibility: inspect the prefix through RIPEstat and an independent looking glass. One observer does not prove universal reachability.
  4. Actual traffic: test a configured service from an external IPv6 network and check the return path. Investigate internal routing and firewall policy if the route is visible but the service is unreachable.
  5. Operational handover: verify reverse DNS where agreed and document who handles routing changes, abuse reports and lease termination.

For ROA validation states and troubleshooting, use the IPv6 routing checklist. For larger allocations and ISP capacity planning, see the IPv6 /29 leasing guide for ISPs. This guide is a planning workflow, not a tested router configuration or confirmation that a particular hosting product supports BYOIP.

Common questions before applying

What is an IPv6 /32?

An IPv6 /32 is a prefix with 96 remaining address bits. It can be planned into smaller customer, site or service prefixes; it is not a single IPv6 address.

Who typically needs a /32?

ISPs, hosting providers and network operators that need structured IPv6 addressing across multiple networks or customers. The intended use, origin ASN and upstream must fit the proposed lease.

Do I need an ASN?

An agreed routing arrangement with a suitable origin ASN and an upstream willing to accept the announcement is required before activation. Elisteka checks the ASN and upstream during manual review.

Can I apply before my ASN or upstream is ready?

Yes: describe what is still being arranged. An agreed origin ASN and supported routing arrangement are required before activation. This is not a promise that an incomplete setup can be activated.

Will this work with my current hosting provider?

Ask the provider whether it accepts externally leased IPv6 space, the intended origin ASN and the proposed prefix lengths. A server with IPv6 connectivity does not by itself establish that the provider offers BYOIP or BGP service.

What happens at the end of the lease?

Plan how services will move to replacement addresses and how the announcement, authorisations and registry records will be withdrawn. Confirm notice periods and responsibilities in the service agreement before ordering.

Questions to resolve before paying

Ask who announces the prefix, who maintains each record, what your upstream needs, how changes are requested, and what happens when the lease ends. Review the service terms and acceptable use policy. Read the routing checklist with your network engineer.

Technical references

  • RIPE NCC: obtaining and registering IPv6 address space
  • RIPE Database: the route6 object

Discuss your IPv6 /32 requirements

Still checking your setup? Check technical fit before completing the full application.

Share your company, intended use and proposed origin ASN. Request an IPv6 /32 lease or email sales@elisteka.com. No payment is collected through the application form.

All IPv6 guides

Plan your address space

Compare IPv4 lease prices and requirements and RIPE IPv6 /32 leasing for your network. All IPv4 space is currently leased, so IPv4 enquiries join a waiting list without a guaranteed start date. IPv6 requests are reviewed individually for availability, technical fit and agreed terms.

Related guides

  • RPKI ROA for leased prefixes
  • IPv6 /29 capacity for ISPs
  • IPv6 routing checklist

Discuss your network requirements

Tell us your network use, origin ASN and upstream for a manual IPv6 review.

Request an IPv6 lease review
ELISTEKA Network Resources

IPv4 and RIPE IPv6 leasing for professional network operators.

sales@elisteka.comabuse@elisteka.com
LinkedInCrunchbase

Services

IPv6 /32Lease IPv4Sell or Buy IPv4Sponsoring LIR

Resources

PricingIPv4 and IPv6 fee calculatorGuidesAbout

Policies

PrivacyTermsSeller termsAcceptable use
© 2026 ElistekaCompany information