IP Leasing: Plan to Launch

Turn an IPv4 plan into working customer services

Your next subscriber, hosted server or cloud customer needs a working connection. The IP leasing contract process should help you deliver it: choose the capacity, agree the service, prepare routing and put the addresses to work.

Leasing keeps more capital available for your network while giving you the address space to grow. With LARUS, you work directly with the first-party IPv4 operator behind the supply, routing coordination and renewal relationship. Build on Unlimited IPv4 and make continuity part of the plan from the start.

Start with the customers you want to connect

An IP leasing contract gives your business access to address space for an agreed period and service. Start with the result you need: more broadband subscribers, dedicated hosting addresses, reachable APIs or a new location.

Bring the number of addresses you need now, your growth forecast and your intended launch date. Add your ASN and preferred deployment locations so the address plan fits the network you already operate. This makes the conversation about getting your service live, rather than buying a block and working out its use later.

• Size the first deployment. Match the block to the connections or services you are launching.
• Plan the next expansion. Include new customers and locations so address supply supports your sales pipeline.
• Keep control of your network. Align the supply with your routing design and upstream connections.

Agree a service that supports your launch

A useful lease makes the operational details easy to act on. Your commercial team needs a clear cost and renewal path; your network team needs the prefixes, routing arrangements and a direct support contact. Bringing those decisions together keeps the launch moving.

What to settle in an ISP IPv4 lease—and what it does for your business

Decision	Agree with your provider	Customer benefit
Capacity and use	Address block, intended services and expansion plan	Connect the customers you have and prepare for those you are winning
Term and billing	Service period, recurring cost and renewal dates	Keep the deployment budget and ongoing costs clear
Routing and activation	Origin ASN, authorization, route records and activation sequence	Get your network and upstreams ready for the same launch
Support and continuity	Operational contact, escalation path and continuity plan	Know who can act when your customer services need help

If you are comparing an IP service level agreement, connect its measures to your actual service: what is supported, how an incident reaches the right team and how progress is communicated. A headline number is less useful than a support path your engineers can use.

Keep capital available for the network

Every amount you avoid tying up in an address purchase can help fund access equipment, transit, staff or another deployment. Leasing brings IPv4 into your operating plan, alongside the services it helps you sell.

Compare the recurring address cost, any setup work and the service period against your customer revenue and rollout schedule. Block size, duration and market conditions can change the price. Use current IPv4 pricing and market data rather than a rate copied from an old article.

Choose a renewal timetable that gives your team room to plan ahead. For a growing ISP, the commercial question is how reliably you can add capacity and keep customers connected as the business expands.

Choose a provider that stands behind the supply

Your customers depend on the addresses after the agreement is signed. A broker can arrange a transaction; your network needs an operator that stays involved in supply, routing coordination and renewals.

Registration and routing sit beneath both purchased and leased IPv4. Buying an address block does not remove that registry dependence. LARUS brings direct first-party supply and Continuity together, so you can focus on the services earning your revenue.

Lu Heng explains the reasoning in his note on registry risk and business continuity. The practical question for your ISP is who remains able to support the network when the underlying environment changes.

Prepare routing, then launch with confidence

Give the technical team your planned origin ASN and upstream arrangements early. This lets the authorization and routing work follow the way you want to run your network.

1. Align authorization and routing records. Coordinate the letter of authorization, relevant IRR route objects and RPKI Route Origin Authorization with the intended prefix and ASN. This helps upstreams recognize the routes you plan to announce.
2. Check the addresses against your workload. Review IP reputation and readiness, and prepare reverse DNS where your services need it. Email delivery and API access need different practical checks.
3. Test real connections. Announce the agreed prefixes, confirm reachability through your upstreams and test the applications your customers will use.
4. Move into service with a support path. Keep the operational contacts, prefix details and renewal dates accessible to the team running the network.

RPKI origin validation checks whether a prefix is announced by an authorized ASN; it does not rate address reputation or application performance. The BGP origin-validation specification explains that distinction. Combine correct routing with service-level testing so the launch reflects what your customers actually experience.

Make continuity part of growth

A successful lease keeps working beyond the first activation. Track customer demand, plan renewals ahead of the service end date and bring expansion needs into the same operating relationship.

Keep reputation monitoring and incident response close to the services they protect. A delivery problem needs the relevant reputation check; an unreachable prefix needs routing investigation. Direct access to the operator helps the right issue reach the right people.

LARUS Continuity connects Unlimited IPv4 with a long-term operating relationship. Your business gets a path for ongoing supply and support as it grows, rather than a new address search every time you win more customers.

IP leasing process: your questions answered

What is the IP leasing contract process?

Define the address capacity and services you need, agree the lease and support arrangement, prepare routing, test the deployment and activate. Keep renewal and expansion in the plan so your supply follows customer demand.

Why lease IPv4 instead of buying it?

Leasing helps put addresses into service while preserving capital for equipment and growth. Direct LARUS supply also connects the initial deployment to an ongoing operator relationship and Continuity.

How long should an IP lease run?

Match the service period to your customer commitments and rollout plans. Agree how renewal and additional capacity will work early, so the next stage of growth does not become a last-minute purchasing exercise.

What affects the price?

The address quantity, service period, deployment needs and market conditions shape the commercial offer. Compare current pricing with the revenue and expansion the addresses will support.

Can I use leased addresses for my own customers?

Bring your subscriber, hosting or cloud-service model into the first conversation. LARUS serves network operators, so your address and routing plan can be built around the services you deliver.

What should I have ready to start?

Your initial address quantity, growth plan, intended use, deployment locations, ASN and target launch date give the team a useful starting point. Your next step is to choose the IPv4 plan that fits the network you want to build.