Hosting and cloud providers
Address space for VPS, dedicated hosting, cloud platforms and supporting infrastructure, subject to review of the intended service and abuse controls.
RIPE IPv6 leasing
RIPE IPv6 /32 Leasing for Network Operators
A professionally reviewed IPv6 prefix service for hosting providers, ISPs and infrastructure businesses that need a substantial allocation with coordinated routing and registry records.
Applications are reviewed individually. Provisioning and activation remain manual.
The service
One standard /32, coordinated for professional use.
Elisteka’s public IPv6 service provides the agreed right to use one RIPE IPv6 /32 under a commercial lease. A /32 gives a network operator a large, stable IPv6 address space for an organised addressing plan across services, sites or customers. The lease does not transfer ownership of the number resource.
The service combines the prefix with the practical records and documentation needed for an agreed routing arrangement. Customer ASN coordination, an exact ROA, a route6 object, reverse DNS delegation, an LOA and applicable RIPE Database coordination are reviewed as part of onboarding. The final implementation depends on the customer’s network, upstream and verified technical references.
Who it is for
IPv6 for operators building real network services.
The /32 service is designed for legal businesses operating professional networks rather than individual or short-term retail use. Typical applicants include organisations that need clear routing responsibility and enough address space to plan beyond a single deployment.
ISPs and WISPs
A structured IPv6 allocation for subscriber or access-network planning where the ASN, upstream and operational arrangement can be confirmed.
Network and infrastructure businesses
IPv6 for managed platforms, network services and infrastructure operations that require a documented business and technical relationship.
Routing and registry records
Customer ASN, ROA and route6 coordination.
An agreed origin ASN is required before activation. The application collects the current ASN or an explanation of an arrangement still being finalised, allowing Elisteka to review the proposed routing setup before any production change.
Customer ASN
The prefix may be prepared for announcement from the customer’s agreed ASN. Elisteka confirms the ASN, upstream relationship and relevant technical contacts. An application does not guarantee that every proposed routing arrangement can be supported.
ROA and RPKI
An exact Route Origin Authorisation can associate the agreed /32 with the approved origin ASN. The intended prefix, ASN and maximum length are checked before publication. The ROA supports route-origin validation; it does not guarantee that every network will accept or propagate a route.
route6
A RIPE Database route6 object can document the IPv6 prefix and origin ASN. Elisteka prepares or coordinates the applicable object using the validated service details. Registry publication and global routing are separate checks, and third-party routing policy remains outside Elisteka’s control.
Operational documentation
Reverse DNS, LOA and clear technical references.
Reverse DNS
Where required, the relevant ip6.arpa zone can be delegated to the customer’s agreed authoritative nameservers. Nameserver and delegation requirements are confirmed before the change is prepared.
Letter of Authorization
An LOA can identify the agreed prefix, origin ASN and service relationship for the customer and its upstream. It records the authorised arrangement without transferring ownership of the IPv6 resource.
RIPE coordination
Elisteka coordinates the resource records and customer references applicable to the approved setup. Records are based on verified details supplied during onboarding and are reviewed before activation.
Manual onboarding
Review first, then provision the agreed service.
Manual review is intentional during the initial service launch. It keeps business, contractual and technical decisions tied to a named application rather than treating an online form as automatic approval.
- 01
Application
Provide the legal business, intended use, network and ASN information.
- 02
Business review
Elisteka reviews the applicant and asks for clarification where evidence is incomplete.
- 03
Technical agreement
Confirm the ASN, upstream, route records, rDNS nameservers and operational contacts.
- 04
Contract and payment
Agree the service order, applicable term and invoice before provisioning begins.
- 05
Provisioning
Prepare the approved registry, authorisation, reverse-DNS and documentation changes.
- 06
Verification
Check the agreed records and routing arrangement before confirming activation.
Pricing
Choose annual or monthly billing for one /32.
The founding annual offer is the primary launch option. The monthly alternative has a minimum initial commitment so it is not a single-month service.
Founding offer
€239 first year
Standard annual renewal is €299/year unless otherwise agreed in the applicable service agreement.
Monthly alternative
€29 / month
Three-month minimum. €87 is billed upfront for the first 3 months. After that initial period, service continues at €29/month, subject to the applicable service agreement.
Need a larger IPv6 allocation? Contact us. Larger allocations are reviewed and quoted manually.
Request IPv6 /32FAQ
RIPE IPv6 /32 leasing questions.
Do we need our own ASN?
An agreed origin ASN is required for activation. If your ASN arrangement is still being finalised, explain it in the application so it can be reviewed with the rest of the technical setup.
Is ROA support included?
Yes. An exact ROA for the agreed prefix and origin ASN is included in the coordinated service where applicable, with verification before activation.
Can reverse DNS be delegated?
Yes. Provide the intended authoritative nameservers or describe the requirement. The applicable ip6.arpa delegation is agreed before provisioning.
Does the lease transfer ownership?
No. The service grants an agreed right to use the leased IPv6 prefix. Ownership of the number resource is not transferred.
How quickly is service activated?
Timing depends on business review, technical confirmation, contract, payment and manual provisioning. Elisteka agrees expected timing with the approved customer rather than promising automatic activation.
Are routing and geolocation guaranteed?
No. Elisteka coordinates the agreed records, but route acceptance, global propagation and decisions made by third-party geolocation databases remain outside Elisteka’s control.
Start the review
Tell us about your network and intended use.
The application requests business and technical information only. No payment is collected through the website.