Ideal for
- Validated multi-tenant or routed network layouts
- Projects that have already outgrown /28 sizing
- Customers who need a noticeably larger public IPv4 pool
- Teams ready for manual review and additional validation
Choose the /27 when the use case is already established and you need a larger routed pool than the /28 can provide.
An active Tinyservers VPS is required. Additional validation may be requested, and /26 or larger requests should stay on manual quote.
A /27 is a block of 32 consecutive IPv4 addresses (subnet mask 255.255.255.224). Two addresses are reserved for network and broadcast, leaving 30 usable IPs. Because the whole block is routed to your existing VPS, you do not lose a third address to a gateway — you simply add the IPs as aliases on your network interface.
| Block | Subnet mask | Total IPs | Usable on your VPS | Price |
|---|---|---|---|---|
| /29 | 255.255.255.248 | 8 | 6 | €8.90/mo |
| /28 | 255.255.255.240 | 16 | 14 | €14.90/mo |
| /27 | 255.255.255.224 | 32 | 30 | €26.90/mo |
Full guide on the blog: Routed IPv4 subnets for VPS — when you need /29, /28 or /27.
The routed /27 is the largest public IPv4 add-on currently exposed in the catalog. It is meant for customers who have already validated their workload and need more room than the smaller subnet tiers provide.
Yes. Larger routed blocks should stay on manual quote and approval.
Possibly. The larger the routed pool, the more likely manual validation becomes part of provisioning.
Use the contact path so the request can be reviewed outside the standard catalog flow.
You might also like