Shared NAT is common on cheap VPS offers. A dozen customers appear to share one public address, and your SSH, RDP, or outbound mail inherits whatever reputation that neighbour earned. Vpster does not sell that. Each instance gets its own public IPv4.
SSH, RDP, and outbound mail use that address. You see it in the console. That is the address we mean when we say dedicated.
- One public IPv4 per instance, not shared customer NAT
- The same address for inbound SSH or RDP and for outbound mail
- Stock is live at deploy; a funded wallet does not reserve it
If you only need a throwaway shared IP, this is the wrong product. The catalog is built for a dedicated address on every box.
Port and shield
The catalog port is 1000 Mbps behind a network shield. You keep the dedicated IPv4. Transfer is by plan — 1 to 16 TB depending on size — not an unmetered promise. Uptime target and the rest of the network copy live on the network page.
IPv6 may also be present on some images. Do not assume inbound IPv6 is the path you advertised to a peer or a registrar. The IPv4 in the console is the address we mean.
Why a stable address matters
Trading bots, RPC nodes, and Windows desktops often need an address that is not behind someone else's NAT. Mail from the box is less likely to share a blocklist with a neighbour you never chose. None of that requires a special “IP add-on.” It is on every monthly instance.
Cities and stock
IPv4 stock is live at deploy. A city can show out of stock even when the plan exists. Check Locations before you pick a region. Frankfurt, Amsterdam, London, New York, and Singapore are the usual public set for monthly cloud.
Stock changes. A funded wallet does not reserve an address. Do not bookmark a city as always available. If you need one region for peering, wait and check again rather than deploying a second box “just in case.”
See live stock on Locations, or start a deploy after you fund the wallet.
Comments