Availability Zones
Geographically isolated but interconnected infrastructure segments designed for fault tolerance, high availability, and low-latency cross-zone communication.
Overview
CloudNexus Availability Zones (AZs) are physically distinct data centers within a single geographic region. Each AZ operates independently with redundant power, cooling, and networking infrastructure, while remaining connected via ultra-low-latency private backbones.
Key Characteristics
- Physical Isolation: Separate power grids, cooling systems, and physical security per AZ.
- Logical Connectivity: Private 100 Gbps fiber links with <1ms latency between zones.
- Independent Failure Domains: Outages in one AZ do not impact others.
- Consistent APIs: Deploy workloads across zones using identical resource endpoints.
Architecture & Isolation
Each region contains at least 3 Availability Zones, distributed across separate facilities to mitigate site-wide failures. Traffic routes through regional load balancers before reaching the active zone.
Independent facilities interconnected via dedicated low-latency backbone
Cross-AZ traffic is encrypted in transit and routed through our regional network fabric. Synchronous replication is supported for stateful services, while asynchronous options are available for cost-optimized setups.
Global AZ Network
CloudNexus currently operates 18 Availability Zones across 6 major regions. All zones support compute, storage, networking, and managed database services.
| Region | AZ Identifiers | Status | Cross-AZ Latency | Pricing Tier |
|---|---|---|---|---|
| US East (Virginia) | us-east-1a, -1b, -1c | ● Operational | 0.8 ms | Standard |
| EU West (Frankfurt) | eu-west-1a, -1b | ● Operational | 0.9 ms | Standard |
| AP South (Singapore) | ap-south-1a, -1b | ● Operational | 1.1 ms | Regional |
| US West (Oregon) | us-west-1a, -1b, -1c | ● Maintenance | 0.7 ms | Standard |
| SA East (São Paulo) | sa-east-1a | ● Operational | N/A | Regional |
* Cross-AZ latency represents p99.9 measured over private backbone. Public internet routes incur standard geographic latency.
Management & API
Configure, monitor, and deploy across Availability Zones using the CloudNexus Console, CLI, or REST API. Terraform, Pulumi, and Kubernetes providers are fully supported.
API Example: Multi-AZ Instance Request
# Deploy a stateful set across 3 AZs with auto-failover
cloudnexus compute create --name web-cluster-prod \
--az us-east-1a,us-east-1b,us-east-1c \
--replicas 3 \
--strategy multi-az-failover \
--network-mode private-backboneTerraform Provider
resource "cloudnexus_instance" "web" {
count = 3
availability_zone = ["us-east-1a", "us-east-1b", "us-east-1c"][count.index]
instance_type = "cn.standard.4x"
cross_az_failover = true
}Best Practices
Optimize your architecture for resilience, cost, and performance when deploying across Availability Zones.
Distribute Read/Write Nodes
Place primary database instances in one AZ and read replicas in others to balance load and isolate failures.
Use Private Backbones
Keep cross-AZ traffic on the private network to reduce latency, avoid egress costs, and enhance security.
Test Failover Regularly
Run chaos engineering drills to verify automatic failover, DNS propagation, and data consistency.
Right-Size Cross-AZ Traffic
Minimize synchronous calls between zones. Use async messaging or cache layers for inter-service communication.