Short answer: A hosting or cloud provider may lease an IPv4 /24 when it needs 256 addresses for customer or infrastructure services and can originate the range through an accepted ASN and upstream. Prepare routing and registry records first. Elisteka's IPv4 space is fully leased, so new requests enter the waiting list.
For a wider protocol choice, read IPv4 vs IPv6 for small networks in 2026.
When a hosting provider needs a /24
A /24 may suit customer workloads, service segmentation, migrations or network policy. Check actual capacity, address reputation, reverse DNS and upstream acceptance. A lease is not a substitute for connectivity or an ASN.
Prepare RIPE and routing information
- Resource and organisation records: identify the registered holder and the organisation responsible for use.
- Origin ASN and upstream: confirm the ASN that will originate the route and the upstream's prefix, IRR and RPKI policy.
- IPv4 route object: coordinate the appropriate IRR
routeobject for the prefix and origin ASN. - RPKI ROA: agree who controls the resource certificate and who will create or update the ROA for the exact prefix, ASN and maxLength.
- Abuse contact: provide a monitored mailbox and a process for investigating reports.
- Reverse DNS: plan PTR records and confirm who coordinates delegation or updates.
For IPv6, the corresponding IRR object is generally route6. A route object describes routing intent, a ROA authorises an origin for RPKI validation, and BGP carries the actual route. None guarantees upstream acceptance.
Typical onboarding steps
- Submit the IPv4 waiting-list request with organisation, intended use, quantity, ASN and abuse contact.
- Complete manual business and technical review, including eligibility, abuse readiness and upstream arrangements.
- Agree lease scope, term, price, responsibilities and acceptable use.
- After approval, agreement and payment, coordinate route, ROA, reverse DNS and handover.
- Verify the intended route and operational contacts before production use.
Price and current availability
The published IPv4 /24 reference price is €105 per month excluding VAT. All current Elisteka IPv4 space is fully leased. New requests go to the waiting list; an application does not reserve a block or guarantee a start date. See published IPv4 and IPv6 prices.
Frequently asked questions
Who may need a leased IPv4 /24?
Hosting providers, cloud platforms and network operators that need a distinct 256-address range for customer or infrastructure services may consider a /24. Confirm routing and upstream requirements before applying.
What is the published /24 lease price?
The reference price is €105 per month excluding VAT. Elisteka’s IPv4 space is fully leased; new requests go to the waiting list, not immediate allocation.
Which RIPE and routing records should I prepare?
Prepare organisation and resource-holder details, the intended origin ASN, an IPv4 route object, RPKI ROA plan, IRR information, a monitored abuse contact and reverse-DNS requirements.
Does a ROA announce the prefix?
No. A ROA authorises an origin ASN for RPKI validation. It does not create a BGP announcement or force an upstream to accept a route.
What happens during onboarding?
The provider submits an enquiry, completes manual business and technical review, agrees terms, then coordinates route, ROA, reverse DNS and handover after approval and payment.
Can I use the lease for proxy or spam services?
Proxy or VPN relay and spam are not permitted under standard acceptable-use rules. Automated data collection requires separate approval where permitted.
Prepare your ASN, upstream and abuse contact, then request a place on the IPv4 waiting list or email sales@elisteka.com.