CubePath runs on its own network, so you can deploy compute close to your users and route traffic across our footprint. This page shows where you can run servers and where we operate network-only points of presence.
Where you can deploy servers
VPS and dedicated servers are available in three regions:
| Region | Code | Servers | Network | Notes |
|---|---|---|---|---|
| Barcelona, Spain | eu-bcn-1 | Yes | Yes | European region |
| Houston, Texas | us-hou-1 | Yes | Yes | US Central |
| Miami, Florida | us-mia-1 | Yes | Yes | US East / LatAm gateway |
Network-only locations
In these locations we operate network only — transit, IP transport and connectivity. You can't deploy servers here:
| Location | Code | Servers | Network | Notes |
|---|---|---|---|---|
| Amsterdam, Netherlands | ams | No | Yes | Network only, no compute |
| Virginia, United States | us-va-1 | No | Yes | Network only, no compute |
Choosing a region
Pick the region nearest your users. Latency is the one thing no amount of hardware fixes: a request that has to cross an ocean loses more time to distance than a bigger plan can ever give back.
ImportantA resource's region is set at deploy time and can't be changed afterwards. Moving to another region means deploying there and migrating — so it's worth being right the first time.
Resources in different regions are independent of each other, and several things are strictly regional:
- A private network lives in one location; servers elsewhere can't join it.
- A floating IP only attaches to machines in the location where it was acquired.
- An availability group spreads machines across hosts within a single location.
- A Kubernetes cluster and its workers live in one location.
Serving more than one region
Since resources don't span regions, multi-region setups are built by running the same stack in each one and routing between them:
- GeoDNS answers each visitor with the nearest region's address, and health checks pull a dead region out of rotation automatically.
- A CDN zone puts static content near everyone without duplicating your servers at all — often the cheaper answer when only assets are slow.
TipBefore building in a second region, check whether latency is actually your problem. A CDN in front of a single-region app fixes most of what people expect multi-region to fix, at a fraction of the operational cost.
Our network
We operate our own infrastructure and network end to end, which keeps latency low and connectivity reliable across every region. See more on our datacenter page.