Getting started / Regions and zones
Regions and zones
Where your resources run, and why the two kinds of virtual machine sit in different zones.
One region
Pantech runs one region, in Africa. Every virtual machine, disk, snapshot and network you create lives there, on our own hardware, so nothing you store leaves the region. The region is shown on your organization's page and cannot be changed.
Zones
A region is split into zones, and the kind of virtual machine decides which zone it lands in:
- Standard VPSes run in one zone.
- VMs in a VPC, and the VPCs themselves, run in another.
You do not pick a zone directly; choosing the kind on the create form does it. The zone shows on a machine's Networking tab and on each volume, written like af-abj-1.
Zones matter in two places:
- Volumes attach only within their zone. A volume made for a standard VPS cannot be attached to a VM in a VPC.
- Some images are offered in only one zone. The create form lists only the images that run where your machine is going.
Public addresses are limited
Public IPv4 addresses are scarce, and each zone has a fixed pool. Every standard VPS takes one, each VPC takes one for its outbound traffic, and each static IP takes another. If a zone runs out, the create form marks that kind as unavailable and says why. Sharing one address between VMs with port forwarding helps when machines only need a port or two.