3-AZ Region - Public Cloud


New

Paris 3-AZ Region (EU-WEST-PAR)

Test the highest resilience standards.

Deploy highly-available apps across 3 independents, 30km-distant Availability Zones in the Paris Region.

Benefit from built-in redundancy, low-latency replication, and maximum uptime - without the premium costs from hyperscalers.

πŸ—“οΈ Beta ends: April 1, 2025
πŸ“ Paris Region (EU-WEST-PAR)
πŸ’Έ Free during Beta: Compute, Block Storage, and Network.

Available in: eu-west-par-a, eu-west-par-b, eu-west-par-c

paris-3az-hero

See how our SLAs compare to major hyperscalers:

Β 

OVHcloud 1-AZ

AWS Service-Level

OVHcloud 3-AZ

AWS Region-Level
Compute99.99%99.5%99.99%99.99%
Network99.9%99.9%99.99%99.99%
Object storage (S3 Compatible)99.9%-99.99%99.9%
Block storage (Classic)99.9%99.9%

99.99%

99.9%

With OVHcloud 3-AZ, critical services like Compute, Network, Object and Block storage achieve 99.99% availability, matching hyperscalers while offering more flexibility.

🌐 Paris Region, 3-AZ

Β 

Deploy Across 3 Isolated Zones. Maximize Uptime.

  • 3 Availability Zones: eu-west-par-a, eu-west-par-b, eu-west-par-c - each in its own secure data center.
  • Physical Redundancy: Independent power, cooling, and networking for fault containment.
  • Built for High Availability: Keep your apps online even if one zone fails.

Seamless Traffic Distribution. Instant Failover.

  • Regional IP Load Balancers: Auto-distribute traffic across all AZs.
  • Gateways: Manage private and public access with full control.
  • Failover Ready: If one AZ fails, traffic reroutes instantly to the remaining zones

Resilience Across Compute, Network, and Storage.

  • Compute: Zonal services, deployed across AZs for redundancy. SLA: 99.99%
  • Load Balancer: Regional IP LBs with auto-failover. Traffic is redirected instantly in case of AZ outages. SLA: 99.99%
  • Gateways: Distributed across AZs for full control and resilience. SLA: 99.99%

Tailor Your 3-AZ: Design your Infrastructure for resilience and raw performance

Maximum uptime & blazing-fast IOPS - Architecture in 3-AZ environments delivers both !

Compute Instance 2

Compute instances (Zonal)

⚑ Dedicated VM instances per AZ
πŸš€ Flexible deployments across multiple zones
πŸ’‘ Ideal for scalable web applications, microservices, and compute-heavy workloads.

Resilience: Regional Load Balancer auto-redirects traffic if an AZ fails.

Block Storage Small OVHcloud

Block Storage - Classic (Regional)

βœ… Auto replication across AZs
πŸ›‘οΈ Built-in fault tolerance
πŸ’‘ Best for resilient apps needing high durability.

Resilience : built-in erasure coding makes your Block Storage - classic resilient to an AZ outage

Block Storage Small OVHcloud

Block Storage - High Speed & High Speed Gen 2 (Zonal)

⚑ Ultra-low latency, high I/O throughput
πŸ”₯ Optimized for speed, flexible deployments across multiple zones
πŸ’‘ Ideal for databases, analytics & performance-critical workloads.

Floating IP Gateway Load Balancer

Networking – Load Balancer, Gateway & Floating IP (Regional)

βœ… Seamless public and private traffic distribution across AZs
βœ… Auto-recovery on AZ failure
βœ… Instant rerouting with Floating IP
πŸ’‘ Best for resilient web services, APIs, and external-facing apps.

Resilience: Use regional LB for auto-failover across zones.

3-AZ for Resilience - Zero Downtime During Outages

Outage? No Problem. Traffic rerouted instantly. Ideal For:

Managed Service Providers: Client workloads always on.

Telecoms: Continuous service without downtime.

Retail:Β Reliable, always-on shopping experiences.

Travel & Hospitality: Real-time booking and scheduling.

B2B Services:Β Consistent access to critical applications.

Key Benefits:

⏱️ Zero downtime during AZ outages

πŸ”„ Built-in redundancy (99.99% SLA)

πŸ’Ύ Regional storage for durable data

⚑ Auto-failover across 3 AZs

Β 

Reference Architecture 3AZ 2

FAQ

What is the difference between 1-AZ and 3-AZ regions ?

Learn about resilience of deployments mode in our dedicated guide

Can I migrate my 1-AZ workloads to 3-AZ?

Yes ! Migration is totally possible from 1-AZ region to 3-AZ region.

You an also connect 1-AZ regions to 3-AZ regions through private connectivity in order to optimize complexity and price of your infrastructure deployments.

Is the 3-AZ Beta suitable for production workloads?

The 3-AZ Beta is designed for testing and validation purposes. While it offers high availability and redundancy features, it comes without SLA guarantees during the Beta period. We recommend using it for pre-production environments, failover tests, or new deployments.

However, starting 1st of April, General availability will offer all SLA and infrastructure components to deploy production and mission critical workloads.

What is the SLA for each service in 3-AZ?

Service-level agreements (SLAs) are designed to maximize availability and match hyperscaler standards:

  • Network (LB): 99.99%
  • S3 (Object Storage): 99.99%
  • Compute Instances: 99.99% (zonal service, no change)
  • Block Storage – Classic (Regional): 99.99%
  • Block Storage – High-Speed Gen 2 (Zonal): 99.9%
  • DBaaS: 99.99%

SLAs will be effective starting GA (1st of april)

How does OVH 3-AZ compare to AWS/GCP in availability?

OVHcloud 3-AZ matches or exceeds hyperscaler SLAs while maintaining cost transparency:

  • Network (LB): 99.99% (par with AWS & GCP)
  • Compute: 99.99% (similar to AWS region-level and GCP multi-zone setups)
  • Block Storage (Regional): 99.99% (equivalent to AWS EBS Multi-AZ and GCP persistent disks)
  • Database: 99.99% (on par with AWS Aurora multi-AZ and GCP Cloud SQL with high availability)

How does failover work between Availability Zones?

OVHcloud 3-AZ ensures automatic failover across zones for high availability:

  • Compute: If a VM fails in one AZ, traffic is rerouted via the Regional Load Balancer to healthy instances already deployed in other AZs.
  • Block Storage (Classic Regional): Data remains available even if an AZ goes down, thanks to erasure coding across zones.
  • Network: Floating IPs and Gateways automatically reassign to healthy AZs without downtime.
  • DBaaS: In the event of a failure, standby nodes in other AZs take over with no data loss.

πŸ’‘ Result: Near-zero downtime and seamless user experience, even during an AZ outage.

What support is available during the Beta?

Beta users get access to standard support channels, including our documentation, GitHub issues, and the OVHcloud Discord community. Our product teams actively monitor feedback, and Beta testers can engage directly with them via dedicated Discord channels.

Is there a cost after the Beta?

During the Beta, Compute, Block Storage, and Network services are free until April 1, 2025.
Post-Beta, standard OVHcloud Public Cloud pricing will apply, with:

  • Transparent, no-surprise pricing.
  • Pricing details will be communicated before the end of the Beta.

You can find the 3-AZ GA pricing in our pricing webpage.

  • Alpha
  • Beta
  • General Availability