Ideal for
- VPN or firewall rules that need a dedicated public IP
- Temporary migrations and service cutovers
- Running a second endpoint on the same VPS
- Simple separation between services or clients
Add one more public IPv4 when your VPS needs an extra endpoint for VPN, firewalling, migration work or service separation.
An active Tinyservers VPS is required. Commercial checks may be required, and abuse-sensitive use cases such as spam, public proxies and bulk mailing are not accepted.
An active Tinyservers VPS is required. After payment and any required commercial checks, technical allocation runs automatically once an eligible VPS is selected. If there is exactly one eligible VPS, it is selected automatically; otherwise choose the target in My Subnets in your client area.
Allocation depends on availability and successful technical checks, so instant delivery is not guaranteed. Support can assist if allocation is blocked. rDNS is available on request.
This monthly add-on is the smallest and fastest way to expand an existing Tinyservers VPS when you need one more public endpoint for routing, separation or migration work.
Yes. It is configured as a recurring monthly product using the same subscription logic as the VPS plans.
No. This product is intended only for customers who already have an active Tinyservers VPS.
If you already know one extra IPv4 is not enough, move directly to the /29 subnet product.
You might also like