Any leased prefix announced through BGP
Route authorization for leased prefixes
RPKI & ROA for Leased IPv4
Understand RPKI, ROA, IRR, origin ASN, and route authorization for leased IPv4 prefixes before announcing production traffic.
What this page covers
RPKI helps networks validate whether an ASN is authorized to originate a prefix. For leased IPv4, the ROA should reflect the real origin ASN and the intended prefix lengths, while IRR and registry data support the rest of the routing policy.
Best fit
When this option makes sense.
Size address space around the network you actually operate, then leave deliberate room for growth and operational separation.
Networks changing the origin ASN of an existing lease
Operators that want route authorization aligned with LOA and IRR records
Plan the deployment
A valid ROA protects the intended origin
A ROA states which ASN may originate a prefix and the maximum prefix length permitted. If the announcement matches, validators can mark it valid. If the ASN or prefix length conflicts, the route can become RPKI-invalid and may be filtered.
Route it deliberately
MaxLength deserves deliberate attention
If you intend to announce a /22 only as a /22, the ROA can be strict. If you also intend to announce /24 more-specifics, the authorization needs to permit that design. Do not use a broader maxLength automatically; authorize only the routes you intend to originate.
Operate it well
RPKI does not replace IRR, LOA, or monitoring
Different networks use different filters and operational checks. Keep the LOA, IRR route object, registry data, and RPKI authorization consistent, then monitor the live route after every origin or prefix change.
Lease operations
Infrastructure around the prefix matters too.
Exact support depends on address family, prefix, registry, and deployment. Confirm the final order details before routing production traffic.
Same-day LOA
Authorization is normally emailed during sales hours after payment and order checks.
WHOIS / SWIP
Company details and updates are included for eligible /24 and larger allocations.
Geolocation updates
Request a city and country when ordering or through a support ticket.
IRR & RPKI / ROA
Route objects and origin authorizations through ARIN or RIPE where supported by the block.
Reverse DNS
Delegate reverse DNS to your nameservers or request hosted PTR records. The published minimum is /24.
Optional rotation
The published option costs $25 per /24 per month. Confirm suitability and availability with sales.
Keep the use attributable and policy-compliant.Leased address space remains subject to LogicWeb’s IP Leasing Policy and Acceptable Use Policy. Larger pools increase the importance of customer attribution, complaint handling, and clean routing records.Read the IP Leasing Policy
Before you order
Common questions.
Does LogicWeb support RPKI for leased IPv4?
LogicWeb publishes RPKI/ROA support for its IPv4 lease options where supported by the block.
What happens if my ROA has the wrong ASN?
RPKI-validating networks can classify the announcement as invalid and may reject it. Correct the authorization before or during the routing change.
Is IRR still useful if I have RPKI?
Yes. Many operators still use IRR-based prefix filters and routing policy data. RPKI and IRR solve related but different operational problems.
From planning to production
Need address space for this workload?
LogicWeb publishes IPv4 /24 through /18 and IPv6 /48, /32, and /29 lease options with routing and registry support.