Education and research networks
IPv4 for Campus and Research Networks
Lease IPv4 for a research project or buy capacity for long-term campus services. i.lease helps source ranges and coordinate authorized registry and routing work with your network team.
- Project or ongoing use
- Compare a lease for a defined period with a purchase for persistent demand.
- Supply and coordination
- Review available ranges, commercial terms and the scope of registry and routing support.
- Institutional control
- Your team retains decisions about workloads, network changes and acceptance.
Capacity choices
Use existing space, lease or buy
Compare the period of use, funding and end-of-project needs. Range availability, pricing and transfer eligibility must be confirmed for the specific request.
Start with the space you already have
Map the institution’s authorized allocations to campus services, labs, instruments and partner connections. Check utilization, reserves and where IPv6 or translation can meet the need before adding public IPv4.
Prepare your capacity detailsLease for a project or transition
Add capacity for a research project, temporary lab or staged rollout. Compare recurring cost, permitted use, assignment scope and routing prerequisites. Agree on the term, renewal decision, return duties and exit plan.
Explore managed IPv4 leasingBuy for continuing demand
Consider a purchase for services expected to need IPv4 long term. Review capital, transfer eligibility and registry timing, as well as routing, record maintenance and ongoing operating duties.
Explore IPv4 purchase
Start with the details you know
A first conversation does not require a finished network plan. Share what is known; capacity estimates and technical details can be confirmed together before any change.
- Workload and capacity
- Describe the campus service, research project or partner dependency, the estimated address need and any existing space you can use.
- Timeline and funding
- Include the required start date, project or grant period, and a budget range if known. Note whether a recurring lease or a capital purchase fits your funding.
- Network and contact
- Share the country or region, origin ASN or upstream network if known, and a technical contact. Holder authority, route authorization, DNS and security dependencies are confirmed before changes.
Responsibilities
Agree on supply, routing and operations
i.lease helps source IPv4 capacity and coordinate agreed, authorized work. The institution keeps control of its network; registries, upstreams and external services make their own decisions.
- Confirm the range, quote, permitted use and supply scope. For a lease, agree on renewal, return and exit duties; for a purchase, confirm transfer eligibility and record ownership.
- Confirm holder authority, applicable RIR records, origin ASN, IRR and ROA requirements, and upstream acceptance. Registry processing, route propagation, reputation, geolocation and external access are not guaranteed.
- The institution owns workload and research requirements, security and abuse contacts, change windows, acceptance checks and rollback. IPv4 supply does not guarantee research outcomes.
What campus and research teams should confirm
Use these answers to define the first workload, capacity, authority, and deployment review.
How should a campus or research network estimate IPv4 capacity?
Inventory public services, lab systems, instruments, remote access, partner links, temporary projects, current utilization, forecast demand, assignment duration, IPv6 or translation options, reserve capacity, and accountable owners. Treat the estimate as planning evidence, not a guarantee that a specific range is available.
Which education or research workloads still need public IPv4?
Document the technical or partner dependency that requires public IPv4 for each workload. Private addressing, translation, or IPv6 may fit other workloads, but the institution must validate application, security, funding, and research requirements.
Should an institution retain, lease, or buy IPv4 capacity?
Retained institutional space can fit existing authorized capacity, leasing can fit a defined project or transition window, and purchase can fit durable demand when eligibility, capital, timing, and long-term operations support it. None of these paths guarantees availability, registry approval, price, routing, or external access.
What evidence should be ready before registry or routing changes?
Prepare holder authorization, applicable RIR and WHOIS records, origin ASN, IRR and ROA plans, upstream and partner prerequisites, DNS needs, security and abuse contacts, change windows, observable acceptance checks, monitoring, and rollback ownership. Registries, networks, and partners retain their own decisions.
Tell us what your campus or project needs
Start with the intended use, approximate capacity and target date. We can then discuss suitable supply options and the information needed for the next step.