Region-specific constraints
Each datacenter region can have different technical or operational constraints. These constraints can affect ordering, deployment, network behavior, or what is allowed/available for a specific product.
Examples of constraints that may vary by region
Depending on location and product type, you may see differences in:
- Available products or configurations (certain plans/hardware not offered everywhere)
- Network characteristics (upstream providers, routing, latency patterns)
- Capacity limits (temporary restrictions on new deployments)
- IP availability (limited IPv4 stock in some regions)
- Maintenance windows (timing may depend on the facility)
- Local legal/jurisdiction considerations (data residency and regional regulations)
Note
Region constraints are not the same for OneCloud and Bare Metal.
OneCloud constraints are usually capacity/platform related.
Bare Metal constraints are commonly inventory/lead-time related.
OneCloud (Cloud Instances): common region constraints
- A region may be temporarily unavailable for new VM creation due to capacity
- Certain images/features may be limited to specific regions (depending on platform support)
- Scaling or creating additional instances may depend on current regional capacity
Bare Metal (Dedicated Servers): common region constraints
- Availability depends on hardware stock in that datacenter
- Certain upgrades/options may not be possible in all locations
- “On-demand” deployments may have lead times and are still subject to availability
How to confirm region constraints before ordering
- Check the available options in the order form for the product you want
- If you need a guaranteed region, specific hardware, or special requirements, contact Sales with:
- Desired location(s)
- Required specs (CPU/RAM/storage/bandwidth)
- Any special network/IP needs
- Expected deployment timeline