Technical guide
How to Buy Public IP Addresses
Learn how to buy public IPv4 addresses, compare the real cost of ownership, and see why serious networks choose LARUS Unlimited IPv4 for continuity without tying up growth capital.
Compare IPv4 optionsYour customers need an address they can keep reaching. If your network depends on public IPv4, the decision is bigger than finding a block with the right price: you are choosing how much continuity, capital and operating confidence your business gets with it.
Buying an IPv4 block gives you a registered resource to deploy. It does not remove the registry relationship behind continued use, routing or renewal. LARUS brings Unlimited IPv4 and a first-party continuity partner to that decision, so you can keep your network growing without making a purchase price carry the whole burden of your future service.
Which public IP address do you need?
A public IP address identifies an internet-facing connection or service. A private IP identifies a device inside a local network. Your laptop can have a private address while your router uses a public address to reach the internet.
Public does not mean static. A dynamic public IP can change; a static public IP stays assigned to your service while you retain that service. Start with the result you need, then choose the address path that protects your customer experience.
- One fixed IP for an office or remote access
- Ask your internet provider for a static public IPv4 address. Confirm that it supports the inbound connections your application needs. If your connection uses carrier-grade NAT, ask about a public-IP option; changing your router's private address will not create one.
- A stable address for a hosted server or cloud service
- Request a reserved or static public IP from the hosting or cloud provider. For example, an AWS Elastic IP is a static public IPv4 address for supported AWS resources. This is a provider service, not a transfer of an independent IPv4 block to your organisation.
- IPv4 capacity for an ISP, hosting platform or network
- Compare buying an address block with leasing capacity you can deploy through your network or an agreed provider. Match the block, routing arrangement and operating support to the service your customers expect. The steps below explain the purchase route and the continuity decision that follows it.
For a closer look at shared connections, read CGNAT versus public IPv4.
How to buy a public IPv4 address block
For a portable block, buying means coordinating the transaction, registry transfer and network deployment. A listing is only the beginning. The result you want is working capacity that keeps your services reachable and your team ready for the next customer.
-
Define the capacity and deployment
Write down the address count, countries or regions, target date and services you will run. Include your hosting or transit provider early. A /24 contains 256 IPv4 addresses; the provider's routing and service design determines how you can deploy them. Confirm that the block size fits your network before choosing a listing.
-
Find a block that fits your network
Use a specialist marketplace or work directly with a resource holder. The i.LEASE IPv4 purchase marketplace, powered by LARUS, is the existing purchase route. Compare the exact prefix, registry region, price and availability with your deployment needs.
-
Check the block before committing
Check the registered holder in WHOIS or RDAP, the seller's authority to arrange the transfer and the block's routing history. Review reputation against the services you intend to run, including relevant blocklists. Agree how payment and the registry handover fit together. A useful check is specific to the block and your use, not just a “clean IP” label.
-
Coordinate the registry transfer
The seller and recipient complete the applicable registry transfer process. For example, ARIN's specified-recipient process involves both parties and has a minimum transfer size of /24. Confirm the route for the actual source and destination registries, the fees and the expected handover before setting your launch date.
-
Arrange the ASN and routing
If you operate your own autonomous network, an Autonomous System Number (ASN) identifies it in BGP, the protocol networks use to exchange reachability information. Arrange suitable connectivity and who will originate the prefix. If your provider announces the addresses for you, agree that arrangement with them; buying a block does not mean you must build your own BGP network.
-
Complete the handover and test real service
Align the registration, routing records and origin ASN. A Route Origin Authorization (ROA) identifies the ASN authorised to originate a prefix; an IRR route object records routing information used by network operators. Coordinate any requested letter of authorisation, reverse DNS and router configuration. Then test external reachability and your actual applications before moving customer traffic.
Keep the routing records aligned after launch. Our guide to BGP, IRR and RPKI mismatches explains why an address can be registered correctly yet still have a routing problem.
What does a public IP address cost?
Compare the full service outcome, not only the number on the first quote. An ISP's monthly static-IP charge, a cloud provider's public-IP charge and the acquisition price of an IPv4 block pay for different things. The cheapest-looking route can still leave your capital tied up and your team carrying the upstream relationship.
- Provider-supplied IP: compare the address charge, connectivity or hosting service and any setup costs.
- Purchased block: compare the acquisition price, transaction and registry fees, then transit, resource management, routing and ongoing support.
- LARUS leasing: compare the capacity and Continuity plan your business needs while keeping block-acquisition capital available for growth.
Use IPv4 pricing and market data to understand the market, then compare an actual block or plan against your requirements. Size, region, history and the operating arrangement all affect the decision.
For a purchase quote, start with the exact block in the i.LEASE marketplace. Compare its acquisition cost and ongoing operations with a LARUS capacity and Continuity plan for the same address count and intended start date.
Buying an IPv4 block is not the same as buying continuity
Your network earns its value by serving customers. A purchase commits capital to the resource, but it does not make the registry relationship disappear. Continued use can still depend on registry rules, the operating structure and the relationship supporting the resource. The purchase price is therefore only one part of the continuity decision.
If your business cannot afford to renumber, treat continuity as the product. In practice, that means keeping your services on a stable network identity, adding capacity as customers arrive and knowing who is responsible for the address relationship behind your delivery. You do not need to turn a large purchase into your only continuity plan.
- Keep your service identity working: give customers, allowlists and connected systems a stable address path as your network grows.
- Keep capital available: put money into customers, coverage and network performance instead of locking every expansion into another block purchase.
- Keep one direct operating relationship: work with the first-party platform behind the address supply instead of adding a broker between your team and the resource.
LARUS is the only first-party operating partner built around this documented continuity position. If your team wants the evidence behind it, Cloud Innovation's shareholder-rights court materials and its mandate to LARUS show the rights foundation and the customer-facing commercial, operational and technical platform behind the relevant address estate.
Build with Unlimited IPv4: the headroom to add services, launch new capacity and keep supplying customers without making every next step wait for another acquisition. LARUS offers Capacity, Production, Enterprise and Critical Continuity plans; Critical includes Guaranteed Renewal. Choose the support and renewal commitment your services deserve, while keeping your growth capital working where it creates revenue.
For a business that takes its network seriously, the choice is clear: buy a block and carry the full upstream exposure yourself, or put your customer-facing continuity behind LARUS.
Questions about buying public IP addresses
How do I get a public IP address?
For one office connection or hosted service, start with your ISP or hosting provider's static-IP offering. You usually need an address attached to that service, rather than an independent block transfer. Ask whether it is dedicated to your service and supports the connections you need. For portable IPv4 capacity on an operator's network, compare an address-block transfer with LARUS leasing.
Can I get public IPv4 addresses directly from a RIR?
RIR membership does not automatically give a business the customer-ready capacity it needs. For example, ARIN's general IPv4 pool was depleted in 2015; its current request page describes waiting-list and specific reserved-pool routes. A transfer or leasing arrangement is often the practical path for a deployment that needs usable capacity now. Compare the continuity structure behind each route, not only the registration label.
Do I need an ASN for a static public IP?
Not for a typical provider-supplied static IP. Your provider routes that service. For an independent network or portable block, decide with your network team and upstream provider whether you will originate the prefix yourself or have the provider do it.
Will a static public IP make my connection more secure?
Its main benefit is a stable address for uses such as allowlists, site-to-site connections or hosted services. It does not replace access controls, updates or a firewall, and it does not bypass an ISP's traffic restrictions. Choose it for the connection your application needs, then build continuity around the services that depend on it.
Can I keep a purchased IPv4 block forever?
A purchased block is not a continuity guarantee by itself. Continued use still depends on the registry relationship and how the resources are operated. If your customers depend on a stable network identity, compare who keeps your services supplied, how easily you can add capacity and whether you want to lock growth capital into every expansion. That is where LARUS Unlimited IPv4 is built to be different.
Keep your network moving
Buy capacity. Choose continuity.
Compare a purchased block with Unlimited IPv4 and first-party LARUS Continuity. Keep your capital working on growth while your customers get the stable network identity your service depends on.
