The locations catalog is the same list you see at deploy. A city can be out of IPv4 while the monthly plan still exists. That is not a pricing trick. Addresses are finite. When a city is out, that deploy does not start.
We do not fall back to shared NAT to “keep the sale.” If you wanted a dedicated address in Frankfurt and Frankfurt is empty, you pick another city or you wait. You do not inherit a neighbour's IP, and you do not get a private address dressed up as public.
A funded wallet does not reserve an address. Stock is checked when you deploy, not when the top-up confirms.
Cities on monthly cloud
The usual public set is Frankfurt, Amsterdam, London, New York, and Singapore. Tokyo is not offered on this catalog. Each instance in those cities gets a dedicated IPv4 on a 1 Gbps DDoS-protected port. Transfer is metered by plan, not advertised as unmetered.
Stock changes through the day. Do not bookmark a city as always available, and do not treat last week's screenshot as inventory. In stock and out of stock both show on the live list. That is the inventory, not a teaser.
What to do when a city is out
- Open Locations or the location step on Deploy.
- Pick a city that shows stock.
- Finish the monthly plan and image. Access is instant after the wallet debit.
If you already need one region for peering or latency, wait and check again. Opening a second instance in another city “as a spare” is a second bill, a second disk, and a second renewal. A funded wallet still does not hold an address while you think it over.
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.
See live stock on Locations after you fund the wallet.
Comments