IPv4 for VPN operators
IPv4 capacity for your VPN network
Lease IPv4 capacity for the VPN network your team operates. Compare dedicated and shared assignment, then confirm the regions, routing and term you need.
- Your IPv4 supply partner
- Explore our leasing options and marketplace listings, with coordination for your address requirements.
- Capacity for your VPN stack
- Source addresses for the VPN servers, tunnels and customer services your team operates.
- A plan for your network
- Discuss your regions, prefixes, routing and lease term with our team.
Address assignment
Compare dedicated and shared pools
Build your address plan around the tenants and services you serve. Choose dedicated pools for separation or shared pools for utilization, then discuss the capacity with us.
Dedicated tenant or service pools
Reserve capacity for a particular tenant or service when separate assignments and operating records matter. Plan unused reserves and growth alongside that separation.
Shared pools
Share capacity across tenants or services when utilization is the priority. Plan assignment records, usage controls and abuse response; activity shares the same address reputation.
Bring the details you know
Start with an estimate. Bring your regions, assignment model and growth plan; we will help you explore the address supply options.
- Capacity and assignment
- Share the regions, estimated addresses, peak concurrency, tenant model, assignment duration and reserve needs. Include existing prefixes your team is authorized to use.
- Routing and external checks
- Include the origin ASN, upstreams and holder authority if known. Confirm LOA, IRR and RPKI needs, and record the source and date of reputation or geolocation observations.
- First deployment and expansion
- Describe the initial deployment, growth needs, lease term and renewal or exit plan. Agree acceptance checks, change windows, rollback and abuse-response contacts.
Deployment support
Bring your next VPN deployment together
We help you explore available addresses and coordinate supply details around your network plan.
- Prepare holder authorization and the records needed for your intended deployment.
- Bring together routing requirements, upstream contacts and recent geolocation and reputation checks.
- Test representative connections and sessions, then agree the rollout window, monitoring and expansion plan.
Questions before choosing a pool
Explore the address model and supply details for your next deployment.
How should a VPN operator estimate IPv4 capacity?
Start with active users, peak sessions, service regions, tenant isolation, assignment duration, NAT design and reserve capacity. Share your current footprint and growth plans with us to explore a suitable lease.
Should a VPN network use dedicated or shared IPv4 pools?
Dedicated pools separate assignments and operating records by tenant or service. Shared pools make use of capacity across tenants. Choose around your customer needs, utilization targets and operating model, and discuss the supply requirement with us.
How should we assess a range for VPN use?
Review recent reputation and geolocation information, routing readiness and representative connections from your deployment locations. Share the criteria that matter to your service so our supply discussion starts with your priorities.
What evidence should be reviewed before VPN deployment?
Prepare holder authorization, applicable WHOIS and RIR records, origin ASN, IRR and ROA plans, upstream prerequisites, rDNS and geofeed needs, dated reputation and geolocation observations, abuse contacts, acceptance checks, monitoring, and rollback ownership.
Discuss your VPN IPv4 requirements
Tell us your regions, capacity, assignment model and term. Let’s find address supply for the next stage of your VPN network.