Regions
| Region ID | Name | Location | Status |
|---|---|---|---|
veloxa-us-east-1 | US East (Washington, DC) | Washington, DC area, USA | Live |
More regions are planned. We have not set dates for them, so we don't list them yet. If your users are far from the US East Coast, or you need servers in two places, another provider may serve you better today.
What runs in US East
In this region you can run:
- VPS servers as system containers that start in seconds, with full root access, SSH through your shared IPv4 port block, snapshots and backups.
- Firewalls on your servers' network interface; outbound mail on port 25 is blocked by default.
- S3-compatible object storage buckets.
Not available in this region yet:
- Full virtual machines (choose a container).
- Private networks between your servers.
- Floating IPs and load balancers.
- Public IPv6 addresses for servers.
Our uptime target is in the SLA, and current incidents and maintenance are on the status page.
Availability zones
Each region is made of availability zones. Each zone is its own group of servers, run separately from the others and possibly in another data center, so a fault in one zone does not stop the rest. US East has one zone today, veloxa-us-east-1-a, and we will add more there.
Once a region has more than one zone, you can pick the zone when you create a server. If you leave it on automatic, containers go to the region's default zone and virtual machines go to a zone that runs them. In the API, pass zone to POST /api/v2/servers. Each server reports its zone.
Choosing a region
The console has a region menu on the sign-up page and on the page where you create a server. It lists every open region, which today means everything you create runs in veloxa-us-east-1.
In the API, GET /api/v1/regions lists the open regions with their city and whether they run containers, virtual machines or both. Pass the region's slug as region when you create a server with POST /api/v1/instances. See the developer overview for authentication and examples.