3-AZ Region - Databases & Analytics
Databases & Analytics in Paris 3-AZ Region (EU-WEST-PAR)
Test the highest resilience standards.
Deploy highly-available Databases (PostgreSQL, MySQL, MongoDB, Valkey) and Analytics (Kafka, OpenSearch, Grafana) services 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: July 21, 2025
📍 Paris Region (EU-WEST-PAR)
💸 Free during Beta: All Cloud Databases within Region
Available in: eu-west-par-a, eu-west-par-b, eu-west-par-c
Discover our Tiers & SLAs
Tier | 1-AZ | 3-AZ | Recommended for |
|---|---|---|---|
Essential or Discovery | - | - | Affordable solution for first steps, testing and pre-production. |
Business or Production | 99.90% | 99.95% | Additional features and security needs for production and rapidly scaling environments. |
Enterprise or Advanced | 99.95% | 99.99% | Very large volumes and mission critical data. |
With OVHcloud 3-AZ, Databases and Analytics services achieve 99.99% availability, matching hyperscalers while offering more flexibility.
🌐 Paris Region, 3-AZ
Built for High Availability
- 1-AZ Regions use a single availability zone with one or multiple data centers. While it offers protection against server and driver failures, it may be vulnerable to data center outages, potentially impacting access if the hosting data center fails.
- In comparison, 3-AZ Regions consist of 3 independent availability zones, each isolated in terms of power, cooling, and network systems,providing true fault isolation. This architecture ensures service availability even if an entire availability zone experiences an outage.
- Peace mind of mind with 99.99% availability SLAs.
Deployed Across 3 Isolated Zones
- 3 Availability Zones: eu-west-par-a, eu-west-par-b, eu-west-par-c. Each in its own secure data center. Database nodes are distributed across several nodes in different AZs.
- In the event of an AZ failure, databases and stored data will remain available. The Business/Production and Enterprise/Advanced offerings include at least two nodes, ensuring no service interruption.
- Backups are automatically managed by our services and stored off-site.
The answer to mission-critical data and apps
- Server-level fault tolerance: Uninterrupted service despite individual server failures.
- Data remains available for R/W operations, even in the event of a zone failure.
- 3-AZ Database instances will run exclusively on the latest generation of compute, offering more performance.
Cloud Databases & Analytics (Regional)
💡 At least 2 nodes, ensuring no service interruption
💾 Backups automatically managed and stored off-site.
⚡ Ultra-low latency, high I/P throughput
Resilience: Regional Load Balancer auto-redirects if an AZ fails.
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
FAQ
What is the difference between 1-AZ and 3-AZ regions?
Learn about resilience of deployments mode in our dedicated guide.
In the specific case of Databases & Analytics, 3-AZ instances will run exclusively on the latest generation of compute, with more performance, while 1-AZ will continue offering the previous generation.
Can I migrate my 1-AZ workloads to 3-AZ?
Yes ! Migration is totally possible from 1-AZ region to 3-AZ region.
You can 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, 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?
SLAs will be effective starting GA:
- 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%
- Databases & Analytics: 99.99%
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.
How does failover work between Availability Zones?
OVHcloud 3-AZ ensures automatic failover across zones for high availability. In the event of a Database or Analytics 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.
Is there a cost after the Beta?
Testing during Beta is completely free. Final pricing details will be communicated before the end of the Beta and the launch of General Availability.
-
Alpha
-
Beta
-
General Availability