One address is already included
The base monthly rate of every Tokyo dedicated server already includes one IPv4, tied to the default 250 Mbps unmetered path. Linux uses that address for SSH. Windows Server uses it for RDP. If you run one site, one reverse proxy, and one management entry, get the machine running first. Decide later whether you need more addresses. That is usually less work.
“One included” is specific: leave extra IPv4 at 0 when you order, and the spec panel still shows that public address after delivery. It is not a trial and not a shared egress. It is this machine’s own address. Do not treat “I must buy another one before I can sign in” as the default.
Extra IPv4 starts at 0. 0 means you use the included address only. 5 means you buy five more, for a total of six — it does not replace the included address with five.
Windows and Linux treat “the included one” the same way: it is the management face of the machine. The protocol is the only difference. Linux watches that address over SSH. Windows Server Standard or Datacenter lands RDP on it. Do not buy a second IP just to “split management from production.” Restricting source ranges on a firewall is usually more direct than another address.
How extra addresses are counted
Extra addresses are sold one by one, not packed as a /28 or /27. The configurator is a numeric stepper, not a subnet card. Extras run from 0 to 255. Add the included address and the per-server total is 256. Need a 257th? This product has no larger block to tick. Split onto another machine or change the design.
Add-ons fold into the monthly rate, then that total is prepaid for the same term as the server. Quarterly, semi-annual, and annual only multiply months. Buying many IPs at once does not unlock a discount. The address line in the monthly rate is “extra count × unit price.” The included address is not billed again.
Check the arithmetic once: the 128GB server is $449 / month. Five extra addresses are 5 × $2 = $10, so the monthly rate becomes $459. A quarter is $459 × 3 = $1,377 — not a separate “IP pack” price. The 256GB server follows the same formula with a $599 base. Bandwidth, extra disks, and Windows also ride that formula. Do not treat IPv4 as a second invoice.
What “no subnet packs” actually means
Selling by the address versus selling a block is not just a line on a price table. It changes how you plan routing. A subnet pack usually assumes you will run a gateway, DHCP, or hand a contiguous range to a hypervisor as an IP pool. This site does not sell that pack: each extra address is an independent IPv4. You write the NIC configuration yourself.
If the goal is “this site one exit, that customer another exit,” adding by the address is enough. If you need a contiguous range, to announce your own routes, or to hand a whole block to a virtualization platform as a pool, this product does not match. Do not treat sixteen scattered addresses as a /28.
| What you actually need | Better first move | Do not do this first |
|---|---|---|
| One site + SSH / RDP | Use the included address | Stockpile a batch of IPs |
| Several HTTPS sites on one box | Reverse proxy + host headers + certificates | Buy one IP per site up front |
| A customer or risk team wants a separate exit | Add by the address and write down the use | Buy a whole range in one go |
| Your own DHCP / contiguous range | Use a product that sells subnets | Treat scattered addresses as a /28 |
When extras are worth it
These three cases show up most often. If none of them apply, leave the stepper alone for now.
- Several sites or customers on the same machine need a separate exit. They should not share one address, and you want to drop one of them later without touching the others.
- Mail or risk controls treat “one IP per machine” as isolation. You need to split a sending source or a callback address.
- You already split sites with a reverse proxy and host headers, and a protocol or a partner still requires a distinct public address.
Write down who each address is for before you add it. The console lists a count. It will not keep a purpose ledger for you. Three months later, an address you cannot explain is usually the one you should not have added.
When to leave the stepper at zero
A handful of extra HTTPS sites should start with a reverse proxy, certificates, and host headers. A 32-core machine hosting a dozen sites is common, and they can all share the included IPv4. Buying addresses first and splitting sites later usually costs more in DNS changes.
Not enough bandwidth and not enough addresses are different problems. Default is 250 Mbps unmetered. When guest egress grows, move to 1G or 2G on the configurator. Do not buy more IPs hoping they will buy throughput. Addresses solve identity and isolation, not bandwidth.
You can add at most 255 extras. Before you approach the cap, confirm the OS can actually bind them. An unused address is still billed every month.
What to check after you add them
-
1
Read the console spec, not your memory
After payment, open the instance. The spec panel lists the extra IPv4 count. If it does not match the order, open a ticket first. Do not invent aliases in the OS.
-
2
Write the NIC yourself. The site does not configure it
On Linux, edit netplan or the distro equivalent. On Windows, add the address in the adapter’s advanced settings. The page will not run
ip addrfor you. -
3
Keep power actions and extra IPs on separate tickets
Power on, power off, and reboot go through tickets. Adding an address is not a power action. Do not write “reboot and add an IP while you are there” on one ticket.
After you bind an address, confirm it can leave the box with a local curl or an external probe. A count in the panel with no OS bind still presents the included address to the world.
Reverse DNS, mail authentication, and certificate SANs are not done for you on the order page. An address arriving only means you can configure it in the OS. Outbound mail, API callbacks, and third-party allowlists need the new address written into your own DNS and consoles. Skip a step and the outside world looks like you “bought it but never used it.”
What this means on the server you rent
If the site has to be Tokyo, and you want a dedicated server rather than an oversold VPS, the address rules on the configurator are the ones above. There is no region switch and no subnet pack.
The 128GB server is $449 / month. The 256GB server is $599 / month. Memory is DDR4-3200 ECC RDIMM and cannot be upgraded after order. Default disks are 2 × 1TB NVMe, each drive direct-attached. Address surcharge is extra count × $2 in the monthly rate, then multiplied by months for due. You can order without signing in. If you need to sign in, payment return still lands on the order page.
If this box will also be a Proxmox hypervisor, read the direct-attach disk note first. Address planning and disk planning are two jobs. Neither substitutes for the other.
Add or remove extra IPv4 on the configurator
One address is included. Need more? Use the stepper. Extras are 0–255. The datacenter is Tokyo, Japan. You can order without signing in.