This page outlines the technical, operational and commercial details of ELISTEKA, a Lithuanian RIPE NCC Local Internet Registry that leases IPv6 and IPv4 space from its own allocations to hosting providers, ISPs, cloud operators and other network businesses.
Looking for the best IP providers? ELISTEKA supplies address space directly as a RIPE NCC member rather than brokering third-party inventory, and handles the registry-side work a BYOIP deployment depends on: RIPE database coordination, route6 objects, RPKI ROA, LOA issuance, reverse DNS delegation and geofeed assistance. Note the scope limit before reading further: ELISTEKA supports the resource side of BYOIP and does not offer fully managed end-to-end cloud onboarding.
Provider Details
The registry facts below were verified independently against the RIPE database rather than taken from the company's own summary.
Lithuania (Zuvedru 22, 87107 Telsiai), per the RIPE-registered address
Company Registration
304915849
Founded
2018. The RIPE organisation object was created 28 September 2018.
RIR Standing
RIPE NCC Local Internet Registry. Organisation handle ORG-EU82-RIPE, LIR ID lt.elisteka, maintainer mnt-lt-elisteka-1.
ARIN Facilitator Status
No. ELISTEKA is not an ARIN Qualified Facilitator and does not claim to be.
IPv6 Inventory
Two /29 allocations held directly from the RIPE NCC (2a06:fe40::/29 and 2a09:1d80::/29, both ALLOCATED-BY-RIR). That is 16 /32s of headroom behind the advertised /32 minimum.
IPv4 Inventory
Roughly 38 RIPE allocations, predominantly /24 and /22. The oldest, 78.40.208.0/22, dates from 2007 and so was acquired by transfer rather than allocated to the 2018 organisation.
Abuse Contact
AR48488-RIPE
Support Contact
sales@elisteka.com
Service Capabilities
Capability
Details
Offer Type
Lease. Space comes from ELISTEKA's own RIPE allocations rather than a marketplace of third-party holders. The company has indicated it can discuss IPv4 supply arrangements separately, but sale of address space is not a published offering.
Lease Configurations
Fixed minimum term with monthly billing. Commitment-free month-to-month leasing is not offered. Longer-term and volume arrangements are available on request.
Supported RIRs
RIPE NCC only. Direct resource supply is based on RIPE resources, though customers may announce and use them internationally.
IPv4 / IPv6
Both. IPv6 is the more clearly published offering, with a /32 minimum and a listed price. IPv4 is quoted per prefix from current inventory.
BYOIP Support
Resource side only. ELISTEKA prepares and maintains the registry objects and authorisations a BYOIP announcement needs, but does not run managed onboarding into cloud BYOIP programmes on the customer's behalf. Cloud console work, provider tickets and per-programme validation remain with the customer.
Included Management
RIPE database coordination, route6 objects, RPKI ROA, LOA issuance, reverse DNS delegation and geolocation or geofeed assistance.
Reputation Assistance
Case by case. ELISTEKA will review and assist with IP reputation issues, but states plainly that third-party database and reputation decisions cannot be guaranteed.
Technical Requirements
Requirement
Details
Minimum Prefix Size (IPv6)
/32. There is no fixed published maximum; multiple /32s and larger requirements are subject to availability.
Minimum Prefix Size (IPv4)
Generally /24. The maximum depends on current inventory.
Announcement
The customer announces the prefix from their own network. ELISTEKA provides the authorisation chain rather than transit.
IRR Objects
route6 objects are created and maintained as part of RIPE database coordination.
RPKI / ROA / LOA
ROA creation and LOA issuance are provided as standard where applicable, not as chargeable extras.
Reverse DNS
Reverse DNS delegation is supported, so PTR records can be operated by the customer.
Geolocation
Geolocation and geofeed assistance is available. As with any provider, third-party geolocation databases decide independently when to adopt a correction.
Cloud-Specific Requirements
Not covered by ELISTEKA. Each cloud BYOIP programme has its own minimum prefix size, documentation and validation flow, and the customer works through those directly. Compare the requirements on our cloud provider pages before committing to a prefix size.
Cost and Limitations
Item
Details
Fees / Pricing
IPv6 is EUR 29 per month per /32. IPv4 is quoted per prefix, with volume-based pricing where applicable.
Pricing Model
Per prefix rather than per IP, for both address families.
Minimum Term
Three months.
Billing Cycle
Monthly.
Commitments
Longer-term and volume arrangements are available on request. There is no published rate card for them.
Scope Limitation
No fully managed end-to-end BYOIP onboarding for the major cloud programmes. Organisations that want the cloud-side deployment handled for them should compare providers whose listing shows cloud BYOIP programme support.
Reputation Caveat
Reputation assistance carries no guarantee, because blocklist and reputation operators make their own decisions.
Coverage Limitation
RIPE NCC region only for the source of resources. There is no ARIN, APNIC, LACNIC or AFRINIC supply.
Not Published
Setup times, IPv4 price points, contract templates and abuse-handling turnaround are not published. Request them directly.
BYOIP, or Bring Your Own IP, is a service that allows you to use your own IP addresses with cloud providers and hosting services. This gives you more control over your IP reputation and allows you to maintain your existing IP addresses when switching providers.
BYOIP offers several benefits including maintaining your IP reputation, reducing costs by avoiding IP address purchases, and providing more control over your network infrastructure. It's particularly useful for businesses that need to maintain consistent IP addresses across multiple service providers.
BYOIP is available to organizations that own registered IP address blocks. This typically includes businesses, hosting providers, and organizations that have obtained IP addresses from Regional Internet Registries (RIRs) like ARIN, RIPE, or APNIC.
Yes, you typically need to own or have authority over the IP address blocks you want to use. This usually means having registered IP addresses through a Regional Internet Registry (RIR) or having proper authorization from the IP address owner.
Proof of IP ownership typically includes documentation such as ROA (Route Origin Authorization) records, LOA (Letter of Authorization) documents, or registration records from RIR databases. The specific requirements vary by provider.
Yes, BYOIP is secure when properly implemented. Providers use various verification methods including ROA records, certificates, and registration checks to ensure only authorized IP addresses are used. However, it's important to follow security best practices and maintain proper IP address management.
The setup time varies by provider and depends on factors such as prefix validation, ROA creation, and verification processes. Typically, it can take anywhere from a few hours to several days, depending on the provider's requirements and verification process.
Yes, many providers support BYOIP across multiple geographic regions. However, the specific regions and locations supported vary by provider. Some providers offer global BYOIP support, while others may be limited to specific regions.
When you stop using BYOIP with a provider, your IP addresses are typically returned to your control. The provider will stop advertising your IP prefixes, and you can use them with another provider or return them to your normal routing. It's important to coordinate the transition to avoid service disruptions.
Cookies and analytics
We use optional analytics cookies to understand how BYOIP.info is used. You can accept or reject them. Read our Cookie Policy for details.