Commercial or private VPN infrastructure with legitimate customer egress
VPN & controlled egress
IPv4 Leasing for VPN Services
Plan dedicated IPv4 address pools for legitimate VPN and controlled-egress infrastructure with routing, geolocation, rDNS, and abuse-response considerations.
What this page covers
VPN operators use public address pools to provide customer egress, separate locations, and keep network identity manageable. The important part is not simply obtaining more addresses—it is designing pools that can be routed, geolocated, monitored, and retired cleanly.
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.
Multi-location VPN deployments that need dedicated public pools
Teams that need rDNS, geolocation, RPKI/IRR, and LOA support around leased space
Plan the deployment
Size pools by location and failure domain
Instead of treating every address as one global bucket, model how many locations you operate, how many concurrent users each site supports, and how much headroom you want for maintenance or reputation isolation. A /24 can be a clean starting unit; larger deployments may group several /24s under a /22 or /20.
Route it deliberately
Routing location and database geolocation are different
Where a VPN endpoint physically routes traffic and what a geolocation database reports are related but separate. Decide both intentionally, then test the databases your applications and customers actually use.
Operate it well
Build abuse response into the service
VPN services can attract misuse if controls are weak. Keep subscriber attribution, timestamps, rate controls, complaint handling, and rapid suspension procedures in place. LogicWeb’s acceptable-use and IP leasing policies apply to leased address space.
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.
Can VPN traffic use leased IPv4 space?
Legitimate VPN and egress use can be considered under the applicable service and acceptable-use terms. Describe the intended use accurately when ordering.
Can I request a specific geolocation?
LogicWeb accepts city and country requests and submits supported updates, but third-party databases control their own update timing and final records.
What block size should a VPN provider start with?
It depends on users, locations, concurrency, and how you isolate pools. A /24 is often a practical operational unit; use the larger /22 or /20 options when your pool design clearly requires them.
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.