OVHcloud Public Cloud Status
Current status
Legend
- Operational
- Degraded performance
- Partial Outage
- Major Outage
- Under maintenance
Monitoring - Service has been fully restored since 08/01/2026 15:00 UTC. Monitoring remains active to ensure long-term stability.
Here are some supplementary details :
Start time : 06/01/2026 18:30 UTC
Impacted Service(s) : Latency was observed on Qwen3-32B.
Customers Impact : Customers were temporarily experiencing latency on the AI & Machine Learning service with the Qwen3-32B model.
We apologize for any inconvenience caused and appreciate your understanding.
Jan 09, 2026 - 10:28 UTC
Here are some supplementary details :
Start time : 06/01/2026 18:30 UTC
Impacted Service(s) : Latency was observed on Qwen3-32B.
Customers Impact : Customers were temporarily experiencing latency on the AI & Machine Learning service with the Qwen3-32B model.
We apologize for any inconvenience caused and appreciate your understanding.
Jan 09, 2026 - 10:28 UTC
Identified - We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our AI & Machine Learning offer on the global region.
Here are some supplementary details :
Start time : 06/01/2026 18:30 UTC
Impacted Service(s) : Latency on Qwen3-32B.
Customers Impact : Customers may temporarily experience latency on the AI & Machine Learning service with the Qwen3-32B model.
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
Jan 07, 2026 - 15:50 UTC
Here are some supplementary details :
Start time : 06/01/2026 18:30 UTC
Impacted Service(s) : Latency on Qwen3-32B.
Customers Impact : Customers may temporarily experience latency on the AI & Machine Learning service with the Qwen3-32B model.
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
Jan 07, 2026 - 15:50 UTC
Investigating - We are currently investigating an incident affecting our AI & Machine Learning offering, which is causing temporary latency issue in the global region.
Here are some supplementary details :
Start time : 06/01/2026 18:30 UTC
Impacted Service(s) : Latency on Qwen3-32B.
Customers Impact : Customers may temporarily experience latency on the AI & Machine Learning service with the Qwen3-32B model.
Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
Jan 07, 2026 - 15:10 UTC
Here are some supplementary details :
Start time : 06/01/2026 18:30 UTC
Impacted Service(s) : Latency on Qwen3-32B.
Customers Impact : Customers may temporarily experience latency on the AI & Machine Learning service with the Qwen3-32B model.
Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
Jan 07, 2026 - 15:10 UTC
Update - Please find below an update on the situation:
Update : The completion rate has now returned to normal levels; however, a considerable amount of time will still be required to fully clear the backlog.
Ongoing Actions : Our teams are mobilised to restore service as quickly as possible.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
Jan 08, 2026 - 16:42 UTC
Update : The completion rate has now returned to normal levels; however, a considerable amount of time will still be required to fully clear the backlog.
Ongoing Actions : Our teams are mobilised to restore service as quickly as possible.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
Jan 08, 2026 - 16:42 UTC
Update - Please find below an update on the situation:
Update : We continue to see a backlog of archiving operations that began on 07 Nov 2025 10:00 UTC. The backlog is being processed, but the rate of completion remains below normal levels, resulting in extended latency for new archiving requests. No new tasks are being blocked, but they are progressing more slowly than expected.
Ongoing Actions : Our teams are mobilised to restore service as quickly as possible.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
Dec 29, 2025 - 16:17 UTC
Update : We continue to see a backlog of archiving operations that began on 07 Nov 2025 10:00 UTC. The backlog is being processed, but the rate of completion remains below normal levels, resulting in extended latency for new archiving requests. No new tasks are being blocked, but they are progressing more slowly than expected.
Ongoing Actions : Our teams are mobilised to restore service as quickly as possible.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
Dec 29, 2025 - 16:17 UTC
Update - Please find below an update on the situation:
Update : We are continuing our archiving efforts, though completion is taking longer than expected.
Ongoing Actions : Our teams are mobilised to restore service as quickly as possible.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
Dec 26, 2025 - 21:12 UTC
Update : We are continuing our archiving efforts, though completion is taking longer than expected.
Ongoing Actions : Our teams are mobilised to restore service as quickly as possible.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
Dec 26, 2025 - 21:12 UTC
Update - Please find below an update on the situation:
Update : We are still catching up on archiving, but it's slower than expected.
Ongoing Actions : Our teams are mobilised to restore service as quickly as possible.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
Dec 17, 2025 - 10:37 UTC
Update : We are still catching up on archiving, but it's slower than expected.
Ongoing Actions : Our teams are mobilised to restore service as quickly as possible.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
Dec 17, 2025 - 10:37 UTC
Update - We have new information regarding the incident that affected your service(s).
Please find below an update on the situation:
Update : Archiving tasks aren't stuck anymore but slowness is observed.
As soon as a customer request archiving, the data will be billed as if it were on tape even though it may take a while for the data to actually reach the tape.
Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
Dec 12, 2025 - 16:58 UTC
Please find below an update on the situation:
Update : Archiving tasks aren't stuck anymore but slowness is observed.
As soon as a customer request archiving, the data will be billed as if it were on tape even though it may take a while for the data to actually reach the tape.
Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
Dec 12, 2025 - 16:58 UTC
Update - We have new information regarding the incident that affected your service(s).
Please find below an update on the situation:
Update : We are currently catching up on archiving, but we do not have an estimated time frame to share with you at this time.
Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
Dec 01, 2025 - 14:21 UTC
Please find below an update on the situation:
Update : We are currently catching up on archiving, but we do not have an estimated time frame to share with you at this time.
Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
Dec 01, 2025 - 14:21 UTC
Identified - We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Cold archive offer on the specific region.
Here are some supplementary details :
Start time : 07/11/2025 10:00 UTC
Impacted Service(s) : Archiving tasks are temporarily stuck in "Archiving" state.
Customers Impact : Customers are temporarily unable to archive their data.
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.
We will keep you updated on the progress and resolution.
Nov 20, 2025 - 10:48 UTC
Here are some supplementary details :
Start time : 07/11/2025 10:00 UTC
Impacted Service(s) : Archiving tasks are temporarily stuck in "Archiving" state.
Customers Impact : Customers are temporarily unable to archive their data.
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.
We will keep you updated on the progress and resolution.
Nov 20, 2025 - 10:48 UTC
Update - We have new information regarding the incident that affected your service(s).
Please find below an update on the situation:
Update : We continue to work with our provider on the incident.
Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
Jan 07, 2026 - 19:22 UTC
Please find below an update on the situation:
Update : We continue to work with our provider on the incident.
Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
Jan 07, 2026 - 19:22 UTC
Update - We have new information regarding the incident that affected your service(s).
Please find below an update on the situation:
Update : The incident originated on 28/10/2025 12:00 UTC when attempts to upgrade Kafka from version 3.8 to the target x.y release began returning an error. The problem is limited to the upgrade path; existing Kafka clusters continue to operate normally, and no other functionality of the Data & Analytics platform is impacted.
Actions in progress :
Our teams are working closely with the provider to diagnose the root cause of the upgrade failure. We are monitoring the provider's remediation work in real time and have prepared a fallback path that allows customers to deploy alternative supported versions (e.g., 3.9 or 4.0) in parallel while the primary upgrade path is being restored.
Key guidance for customers :
No immediate action is required from customers. If you need a newer Kafka version before the official migration is available, you may provision a parallel cluster running version 3.9 or 4.0. We will continue to provide updates as the investigation progresses and will notify you when the upgrade path is fully restored.
Root Cause : This incident is caused by our provider.
Ongoing Actions : The incident has been identified and corrected. It is being closely monitored to ensure long-term stability.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding
Dec 26, 2025 - 12:58 UTC
Please find below an update on the situation:
Update : The incident originated on 28/10/2025 12:00 UTC when attempts to upgrade Kafka from version 3.8 to the target x.y release began returning an error. The problem is limited to the upgrade path; existing Kafka clusters continue to operate normally, and no other functionality of the Data & Analytics platform is impacted.
Actions in progress :
Our teams are working closely with the provider to diagnose the root cause of the upgrade failure. We are monitoring the provider's remediation work in real time and have prepared a fallback path that allows customers to deploy alternative supported versions (e.g., 3.9 or 4.0) in parallel while the primary upgrade path is being restored.
Key guidance for customers :
No immediate action is required from customers. If you need a newer Kafka version before the official migration is available, you may provision a parallel cluster running version 3.9 or 4.0. We will continue to provide updates as the investigation progresses and will notify you when the upgrade path is fully restored.
Root Cause : This incident is caused by our provider.
Ongoing Actions : The incident has been identified and corrected. It is being closely monitored to ensure long-term stability.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding
Dec 26, 2025 - 12:58 UTC
Monitoring - Monitoring remains active for this incident.
Update : Our provider is still working to restore the service as quickly as possible.
The migration from 3.8 to x.y version is expected to be available by the end of January 2026.
We apologize for any inconvenience caused and appreciate your understanding.
Dec 19, 2025 - 08:32 UTC
Update : Our provider is still working to restore the service as quickly as possible.
The migration from 3.8 to x.y version is expected to be available by the end of January 2026.
We apologize for any inconvenience caused and appreciate your understanding.
Dec 19, 2025 - 08:32 UTC
Update - We are continuing to work on a fix for this issue.
Dec 15, 2025 - 14:36 UTC
Dec 15, 2025 - 14:36 UTC
Update - We have new information regarding the incident that affected your service(s).
Please find below an update on the situation:
Update : Our provider has informed us that the migration from 3.8 to x.y version is more complex than initially anticipated, which is the reason why this feature is currently unavailable. However, customers can deploy Kafka version 3.9 or 4.0 in parallel if they need. Upgrade possibility is expected to be available by end January 2026.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
Nov 03, 2025 - 14:50 UTC
Please find below an update on the situation:
Update : Our provider has informed us that the migration from 3.8 to x.y version is more complex than initially anticipated, which is the reason why this feature is currently unavailable. However, customers can deploy Kafka version 3.9 or 4.0 in parallel if they need. Upgrade possibility is expected to be available by end January 2026.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
Nov 03, 2025 - 14:50 UTC
Identified - We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offer on Kafka services.
Here are some supplementary details :
Start time : 28/10/2025 12:00 UTC
Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y").
Customers Impact : Customers are temporarily unable to upgrade their Kafka version from 3.8 to x.y.
Root Cause : This incident is caused by our provider.
Ongoing Actions : The incident has been identified and our teams are working with our provider to restore service as quickly as possible.
We will keep you updated on the progress and resolution.
Oct 31, 2025 - 12:18 UTC
Here are some supplementary details :
Start time : 28/10/2025 12:00 UTC
Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y").
Customers Impact : Customers are temporarily unable to upgrade their Kafka version from 3.8 to x.y.
Root Cause : This incident is caused by our provider.
Ongoing Actions : The incident has been identified and our teams are working with our provider to restore service as quickly as possible.
We will keep you updated on the progress and resolution.
Oct 31, 2025 - 12:18 UTC
Investigating - We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.
Here are some supplementary details :
Start time : 28/10/2025 12:00 UTC
Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y").
Ongoing Actions : Our teams are investigating to determine the origin of the incident to fix it.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
Oct 30, 2025 - 16:15 UTC
Here are some supplementary details :
Start time : 28/10/2025 12:00 UTC
Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y").
Ongoing Actions : Our teams are investigating to determine the origin of the incident to fix it.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
Oct 30, 2025 - 16:15 UTC
About This Site
Welcome to the Public Cloud status page for real-time information on system performance and availability.
AI & Machine Learning || AI Dashboard
Operational
AI & Machine Learning || AI Deploy
Operational
BHS
Operational
GRA
Operational
AI & Machine Learning || AI Endpoint
Operational
AI & Machine Learning || AI Notebooks
Operational
BHS
Operational
GRA
Operational
AI & Machine Learning || AI Training
Operational
BHS
Operational
GRA
Operational
Compute - Instance || BHS
Operational
BHS1
Operational
BHS3
Operational
BHS5
Operational
Compute - Instance || ERI
Operational
UK1
Operational
Compute - Instance || EU-SOUTH-MIL
Operational
EU-SOUTH-MIL-A
Operational
EU-SOUTH-MIL-B
Operational
EU-SOUTH-MIL-C
Operational
Compute - Instance || EU-WEST-PAR
Operational
EU-WEST-PAR-A
Operational
EU-WEST-PAR-B
Operational
EU-WEST-PAR-C
Operational
Compute-Instance || AP-SOUTH-MUM
Operational
Compute - Instance || GRA
Operational
GRA1
Operational
GRA3
Operational
GRA5
Operational
GRA7
Operational
GRA9
Operational
GRA11
Operational
Compute - Instance || India
Operational
AP-SOUTH-MUM-1
Operational
Compute - Instance || LIM
Operational
DE1
Operational
Compute - Instance || RBX
Operational
RBX-A
Operational
Compute - Instance || SGP
Operational
SGP1
Operational
SGP2
Operational
Compute - Instance || SBG
Operational
SBG5
Operational
SBG7
Operational
Compute - Instance || SYD
Operational
SYD1
Operational
AP-SOUTHEAST-SYD-2
Operational
Compute - Instance || USA
Operational
US-EAST-VA-1
Operational
US-WEST-OR-1
Operational
Compute - Instance || WAW
Operational
WAW1
Operational
Containers & Orchestration || Load Balancer
Operational
AP-SOUTH-MUM-1
Operational
BHS5
Operational
DE1
Operational
GRA5
Operational
GRA7
Operational
GRA9
Operational
GRA11
Operational
SBG5
Operational
SGP1
Operational
SYD1
Operational
WAW1
Operational
UK1
Operational
US-EAST-VA-1
Operational
US-WEST-OR-1
Operational
Containers & Orchestration || Managed Kubernetes Service
Operational
BHS5
Operational
DE1
Operational
GRA5
Operational
GRA7
Operational
GRA9
Operational
GRA11
Operational
SBG5
Operational
SGP1
Operational
SYD1
Operational
WAW1
Operational
UK1
Operational
US-EAST-VA-1
Operational
US-WEST-OR-1
Operational
Containers & Orchestration || Managed Private Registry
Operational
GRA
Operational
DE
Operational
BHS
Operational
VA
Operational
Containers & Orchestration || Managed Rancher Service
Operational
Containers & Orchestration || Workflow Management
Operational
BHS1
Operational
BHS3
Operational
BHS5
Operational
DE1
Operational
GRA1
Operational
GRA3
Operational
GRA5
Operational
GRA7
Operational
GRA9
Operational
GRA11
Operational
RBX-A
Operational
SBG5
Operational
SBG7
Operational
SGP1
Operational
SGP2
Operational
SYD1
Operational
AP-SOUTHEAST-SYD-2
Operational
UK1
Operational
WAW1
Operational
WAW2
Operational
US-EAST-VA-1
Operational
US-WEST-OR-1
Operational
AP-SOUTH-MUM-1
Operational
Databases || Cassandra
Operational
BHS
Operational
DE
Operational
GRA
Operational
SBG
Operational
SGP
Operational
UK
Operational
WAW
Operational
Databases || MongoDB
Operational
BHS
Operational
DE
Operational
GRA
Operational
PAR
Operational
SBG
Operational
SGP
Operational
UK
Operational
WAW
Operational
Databases || MySQL
Operational
BHS
Operational
DE
Operational
GRA
Operational
PAR
Operational
SBG
Operational
SGP
Operational
UK
Operational
WAW
Operational
Databases || PostgreSQL
Operational
BHS
Operational
DE
Operational
GRA
Operational
PAR
Operational
SBG
Operational
SGP
Operational
SYD
Operational
UK
Operational
WAW
Operational
Databases || Valkey
Operational
BHS
Operational
DE
Operational
GRA
Operational
PAR
Operational
SBG
Operational
SGP
Operational
UK
Operational
WAW
Operational
Data & Analytics || Data Platform
Operational
Data & Analytics || Dashboards
Operational
BHS
Operational
DE
Operational
GRA
Operational
PAR
Operational
SBG
Operational
SGP
Operational
UK
Operational
WAW
Operational
Data & Analytics || Kafka
Degraded Performance
BHS
Degraded Performance
DE
Degraded Performance
GRA
Degraded Performance
PAR
Degraded Performance
SBG
Degraded Performance
SGP
Degraded Performance
UK
Degraded Performance
WAW
Degraded Performance
Data & Analytics || Kafka Connect
Degraded Performance
BHS
Degraded Performance
DE
Degraded Performance
GRA
Degraded Performance
PAR
Degraded Performance
SBG
Degraded Performance
SGP
Degraded Performance
UK
Degraded Performance
WAW
Degraded Performance
Data & Analytics || Kafka MirrorMaker
Degraded Performance
BHS
Degraded Performance
DE
Degraded Performance
GRA
Degraded Performance
PAR
Degraded Performance
SBG
Degraded Performance
SGP
Degraded Performance
UK
Degraded Performance
WAW
Degraded Performance
Data & Analytics || OpenSearch
Operational
BHS
Operational
DE
Operational
GRA
Operational
PAR
Operational
SBG
Operational
SGP
Operational
UK
Operational
WAW
Operational
Identity, Security & Operations || Authentication
Operational
Identity, Security & Operations || Barbican
Operational
AP-SOUTH-MUM-1
Operational
AP-SOUTHEAST-SYD-2
Operational
BHS5
Operational
DE1
Operational
EU-SOUTH-MIL
Operational
EU-WEST-PAR
Operational
GRA9
Operational
RBX-A
Operational
SBG7
Operational
SGP1
Operational
SYD1
Operational
UK1
Operational
US-WEST-OR-1
Operational
US-EAST-VA-1
Operational
WAW1
Operational
Identity, Security & Operations || Key Management Service
Operational
AP-SOUTHEAST-SGP
Operational
AP-SOUTHEAST-SYD
Operational
CA-EAST-TOR
Operational
CA-EAST-BHS
Operational
EU-CENTRAL-WAW
Operational
EU-SOUTH-MIL
Operational
EU-WEST-ERI
Operational
EU-WEST-GRA
Operational
EU-WEST-LIM
Operational
EU-WEST-PAR
Operational
EU-WEST-RBX
Operational
EU-WEST-SBG
Operational
Identity, Security & Operations || Logs Data Platform
Operational
BHS
Operational
GRA
Operational
LocalZones || AF-NORTH
Operational
AF-NORTH-LZ-RBA
Operational
LocalZones || EU-CENTRAL
Operational
EU-CENTRAL-LZ-BUH
Operational
EU-CENTRAL-LZ-PRG
Operational
EU-CENTRAL-LZ-SOF
Operational
LocalZones || EU-NORTH
Operational
EU-NORTH-LZ-CPH
Operational
EU-NORTH-LZ-HEL
Operational
EU-NORTH-LZ-OSL
Operational
EU-NORTH-LZ-STO
Operational
LocalZones || EU-SOUTH
Operational
EU-SOUTH-LZ-LIS
Operational
EU-SOUTH-LZ-MAD
Operational
EU-SOUTH-LZ-MIL
Operational
LocalZones || EU-WEST
Operational
EU-WEST-LZ-AMS
Operational
EU-WEST-LZ-BRU
Operational
EU-WEST-LZ-DLN
Operational
EU-WEST-LZ-LUX
Operational
EU-WEST-LZ-MNC
Operational
EU-WEST-LZ-MRS
Operational
EU-WEST-LZ-VIE
Operational
EU-WEST-LZ-ZRH
Operational
LocalZones || US-CENTRAL
Operational
US-CENTRAL-LZ-SLC
Operational
US-CENTRAL-LZ-STL
Operational
LocalZones || US-EAST
Operational
US-EAST-LZ-ATL
Operational
US-EAST-LZ-BOS
Operational
US-EAST-LZ-CHI
Operational
US-EAST-LZ-DAL
Operational
US-EAST-LZ-MIA
Operational
US-EAST-LZ-NYC
Operational
LocalZones || US-WEST
Operational
US-WEST-LZ-DEN
Operational
US-WEST-LZ-LAX
Operational
US-WEST-LZ-PAO
Operational
US-WEST-LZ-PHX
Operational
US-WEST-LZ-SEA
Operational
Management || Horizon
Operational
Network || Floating IP
Operational
BHS1
Operational
BHS3
Operational
BHS5
Operational
DE1
Operational
GRA1
Operational
GRA3
Operational
GRA5
Operational
GRA7
Operational
GRA9
Operational
GRA11
Operational
AP-SOUTH-MUM-1
Operational
RBX-A
Operational
SBG5
Operational
SBG7
Operational
SGP1
Operational
SYD1
Operational
AP-SOUTHEAST-SYD-2
Operational
UK1
Operational
WAW1
Operational
US-EAST-VA-1
Operational
US-WEST-OR-1
Operational
EU-WEST-PAR-A
Operational
EU-WEST-PAR-B
Operational
EU-WEST-PAR-C
Operational
EU-SOUTH-MIL-A
Operational
EU-SOUTH-MIL-B
Operational
EU-SOUTH-MIL-C
Operational
Network || Gateway
Operational
BHS1
Operational
BHS3
Operational
BHS5
Operational
DE1
Operational
GRA1
Operational
GRA3
Operational
GRA5
Operational
GRA7
Operational
GRA9
Operational
GRA11
Operational
SBG5
Operational
SBG7
Operational
SGP1
Operational
SYD1
Operational
AP-SOUTHEAST-SYD-2
Operational
UK1
Operational
WAW1
Operational
US-EAST-VA-1
Operational
US-WEST-OR-1
Operational
AP-SOUTH-MUM-1
Operational
EU-WEST-PAR-A
Operational
EU-WEST-PAR-B
Operational
EU-WEST-PAR-C
Operational
RBX-A
Operational
EU-SOUTH-MIL-A
Operational
EU-SOUTH-MIL-B
Operational
EU-SOUTH-MIL-C
Operational
Network || Load Balancer
Operational
BHS1
Operational
BHS3
Operational
BHS5
Operational
DE1
Operational
GRA1
Operational
GRA3
Operational
GRA5
Operational
GRA7
Operational
GRA9
Operational
GRA11
Operational
SBG5
Operational
SBG7
Operational
SGP1
Operational
SYD1
Operational
AP-SOUTHEAST-SYD-2
Operational
UK1
Operational
WAW1
Operational
US-EAST-VA-1
Operational
US-WEST-OR-1
Operational
EU-WEST-PAR-A
Operational
EU-WEST-PAR-B
Operational
EU-WEST-PAR-C
Operational
AP-SOUTH-MUM-1
Operational
RBX-A
Operational
EU-SOUTH-MIL-A
Operational
EU-SOUTH-MIL-B
Operational
EU-SOUTH-MIL-C
Operational
Network || Private network (vRack)
Operational
BHS1
Operational
BHS3
Operational
BHS5
Operational
DE1
Operational
GRA1
Operational
GRA3
Operational
GRA5
Operational
GRA7
Operational
GRA9
Operational
GRA11
Operational
RBX-A
Operational
SBG5
Operational
SBG7
Operational
SGP1
Operational
SGP2
Operational
SYD1
Operational
AP-SOUTHEAST-SYD-2
Operational
UK1
Operational
WAW1
Operational
US-EAST-VA-1
Operational
US-WEST-OR-1
Operational
EU-WEST-PAR-A
Operational
EU-WEST-PAR-B
Operational
EU-WEST-PAR-C
Operational
AP-SOUTH-MUM-1
Operational
RBX-A
Operational
EU-SOUTH-MIL-A
Operational
EU-SOUTH-MIL-B
Operational
EU-SOUTH-MIL-C
Operational
Network || Public network
Operational
BHS1
Operational
BHS3
Operational
BHS5
Operational
DE1
Operational
GRA1
Operational
GRA3
Operational
GRA5
Operational
GRA7
Operational
GRA9
Operational
GRA11
Operational
RBX-A
Operational
SBG1
Operational
SBG3
Operational
SBG5
Operational
SBG7
Operational
SGP1
Operational
SGP2
Operational
SYD1
Operational
AP-SOUTHEAST-SYD-2
Operational
UK1
Operational
WAW1
Operational
US-EAST-VA-1
Operational
US-WEST-OR-1
Operational
EU-WEST-PAR-A
Operational
EU-WEST-PAR-B
Operational
EU-WEST-PAR-C
Operational
AP-SOUTH-MUM-1
Operational
RBX-A
Operational
EU-SOUTH-MIL-A
Operational
EU-SOUTH-MIL-B
Operational
EU-SOUTH-MIL-C
Operational
Quantum || Emulators
Operational
BHS
Operational
GRA
Operational
Quantum || QPUs
Operational
BHS
Operational
GRA
Operational
Storage || Block storage
Operational
AP-SOUTHEAST-SYD-2
Operational
AP-SOUTH-MUM-1
Operational
BHS1
Operational
BHS3
Operational
BHS5
Operational
DE1
Operational
EU-SOUTH-MIL-A
Operational
EU-SOUTH-MIL-B
Operational
EU-SOUTH-MIL-C
Operational
EU-WEST-PAR-A
Operational
EU-WEST-PAR-B
Operational
EU-WEST-PAR-C
Operational
GRA1
Operational
GRA3
Operational
GRA5
Operational
GRA6
Operational
GRA7
Operational
GRA9
Operational
GRA11
Operational
RBX-A
Operational
SBG5
Operational
SBG7
Operational
SGP1
Operational
SYD1
Operational
UK1
Operational
US-EAST-VA-1
Operational
US-WEST-OR-1
Operational
WAW1
Operational
YNM1
Operational
Storage || Cloud Archive
Operational
DE
Operational
GRA
Operational
UK
Operational
WAW
Operational
BHS
Operational
SYD
Operational
SGP
Operational
US-EAST-VA
Operational
US-WEST-OR
Operational
Storage || Cold Archive
Degraded Performance
RBX-ARCHIVE
Degraded Performance
Storage || Instance Backup
Operational
BHS1
Operational
BHS3
Operational
BHS5
Operational
DE1
Operational
GRA1
Operational
GRA3
Operational
GRA5
Operational
GRA7
Operational
GRA9
Operational
GRA11
Operational
SBG5
Operational
SBG7
Operational
SGP1
Operational
SYD1
Operational
AP-SOUTHEAST-SYD-2
Operational
UK1
Operational
US-EAST-VA-1
Operational
US-WEST-OR-1
Operational
WAW1
Operational
AP-SOUTH-MUM-1
Operational
EU-WEST-PAR-A
Operational
EU-WEST-PAR-B
Operational
EU-WEST-PAR-C
Operational
RBX-A
Operational
Storage || Object storage
Operational
BHS
Operational
GRA
Operational
DE
Operational
RBX
Operational
SBG
Operational
SGP
Operational
SYD
Operational
UK
Operational
US-EAST-VA-1
Operational
US-WEST-OR-1
Operational
WAW
Operational
YYZ
Operational
LIM
Operational
AP-SOUTH-MUM-1
Operational
EU-WEST-PAR-A
Operational
EU-WEST-PAR-B
Operational
EU-WEST-PAR-C
Operational
YNM1
Operational
EU-SOUTH-MIL-B
Operational
EU-SOUTH-MIL-A
Operational
EU-SOUTH-MIL-C
Operational
Storage || Volume Backup
Operational
BHS1
Operational
BHS3
Operational
BHS5
Operational
DE1
Operational
GRA1
Operational
GRA3
Operational
GRA5
Operational
GRA7
Operational
GRA9
Operational
GRA11
Operational
SBG5
Operational
SBG7
Operational
SGP1
Operational
SYD1
Operational
AP-SOUTHEAST-SYD-2
Operational
UK1
Operational
US-EAST-VA-1
Operational
US-WEST-OR-1
Operational
WAW1
Operational
AP-SOUTH-MUM-1
Operational
RBX-A
Operational
EU-WEST-PAR-A
Operational
EU-WEST-PAR-B
Operational
EU-WEST-PAR-C
Operational
EU-SOUTH-MIL
Operational
Storage || Volume Snapshot (Ceph)
Operational
DE1
Operational
GRA1
Operational
GRA2
Operational
GRA3
Operational
GRA5
Operational
GRA6
Operational
GRA4
Operational
GRA7
Operational
GRA8
Operational
GRA9
Operational
GRA11
Operational
RBX-A
Operational
SBG5
Operational
SBG6
Operational
SBG7
Operational
SBG8
Operational
SGP1
Operational
SYD1
Operational
AP-SOUTHEAST-SYD-2
Operational
UK1
Operational
UK2
Operational
WAW1
Operational
WAW2
Operational
US-EAST-VA-1
Operational
US-WEST-OR-1
Operational
AP-SOUTH-MUM-1
Operational
EU-WEST-PAR-A
Operational
EU-WEST-PAR-B
Operational
EU-WEST-PAR-C
Operational
EU-SOUTH-MIL
Operational
RBX-A
Operational
BHS1
Operational
BHS3
Operational
BHS5
Operational
LocalZones || AP-SOUTH-MUM
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
[GRA7/GRA9/GRA11/DE1/BHS5/SBG5][Public Cloud] - MKS maintenance notification Jan 12, 2026 09:00 - Jan 14, 2026 17:00 UTC
As part of our continuous improvement plan, a maintenance is scheduled on our Managed Kubernetes Service offer .
Start time : 12/01/2026 09:00 UTC
End time : 14/01/2026 17:00 UTC
Service impact : During the maintenance, all cluster, by cell, with an ALWAYS_UPDATE policy can be temporarily put into a degraded mode.
Service improvement : As part of our continuous improvement policy, we will be doing a maintenance on our Managed Kubernetes Service in the regions GRA7/GRA9/GRA11/DE1/BHS5/SBG5.
Thank you for your understanding.
Posted on Jan 07, 2026 - 15:48 UTC
Start time : 12/01/2026 09:00 UTC
End time : 14/01/2026 17:00 UTC
Service impact : During the maintenance, all cluster, by cell, with an ALWAYS_UPDATE policy can be temporarily put into a degraded mode.
Service improvement : As part of our continuous improvement policy, we will be doing a maintenance on our Managed Kubernetes Service in the regions GRA7/GRA9/GRA11/DE1/BHS5/SBG5.
Thank you for your understanding.
Posted on Jan 07, 2026 - 15:48 UTC
[Global][Data & Analytics ] - Data Platform maintenance notification Jan 12, 2026 13:00-16:00 UTC
As part of our continuous improvement plan, a maintenance is scheduled on our Data Platform offer.
Here are the details of the maintenance:
Start time : 12/01/2026 13:00 UTC
End time : 12/01/2026 16:00 UTC
Service impact : None
Service improvement : As part of our continuous improvement policy, we will be doing a maintenance on our Data Platform infrastructure.
Thank you for your understanding.
Posted on Dec 19, 2025 - 09:49 UTC
Here are the details of the maintenance:
Start time : 12/01/2026 13:00 UTC
End time : 12/01/2026 16:00 UTC
Service impact : None
Service improvement : As part of our continuous improvement policy, we will be doing a maintenance on our Data Platform infrastructure.
Thank you for your understanding.
Posted on Dec 19, 2025 - 09:49 UTC
[EU-SOUTH-MIL][Public Cloud] Octavia maintenance notification Jan 13, 2026 23:30 - Jan 14, 2026 12:00 UTC
As part of our continuous improvement plan, a maintenance is scheduled on our Public Cloud infrastructure.
Here are the details of the maintenance:
Start time : 13/01/2026 23:30 UTC
End time : 14/01/2026 12:00 UTC
Service impact : LBaaS control plane will experience a short-term interruption in availability., Dataplane & LBs that are already spawned will keep on working
Service improvement : As part of our continuous improvement policy, we will be doing a maintenance on our Public Cloud infrastructure.
Thank you for your understanding.
Posted on Jan 07, 2026 - 23:22 UTC
Here are the details of the maintenance:
Start time : 13/01/2026 23:30 UTC
End time : 14/01/2026 12:00 UTC
Service impact : LBaaS control plane will experience a short-term interruption in availability., Dataplane & LBs that are already spawned will keep on working
Service improvement : As part of our continuous improvement policy, we will be doing a maintenance on our Public Cloud infrastructure.
Thank you for your understanding.
Posted on Jan 07, 2026 - 23:22 UTC
[GLOBAL][Data & Analytics] - Data Platform maintenance notification Jan 14, 2026 09:30-11:30 UTC
As part of our continuous improvement plan, maintenance is scheduled on our Data Platform offer.
Start time : 14/01/2026 09:30 UTC
End time : 14/01/2026 11:30 UTC
Service impact : Some tasks running during maintenance will encounter errors.
Service improvement : As part of our continuous improvement policy, we will be doing a upgrade on our Data Platform offer.
Thank you for your understanding.
Posted on Dec 23, 2025 - 18:06 UTC
Start time : 14/01/2026 09:30 UTC
End time : 14/01/2026 11:30 UTC
Service impact : Some tasks running during maintenance will encounter errors.
Service improvement : As part of our continuous improvement policy, we will be doing a upgrade on our Data Platform offer.
Thank you for your understanding.
Posted on Dec 23, 2025 - 18:06 UTC
[Global][Data & Analytics ] - Data Platform maintenance notification Jan 19, 2026 09:00-18:00 UTC
As part of our continuous improvement plan, a maintenance is scheduled on our Data Platform offer.
Here are the details of the maintenance:
Start time : 19/01/2026 09:00 UTC
End time : 19/01/2026 18:00 UTC
Service impact : None
Service improvement : As part of our continuous improvement policy, we will deploy a new open-source REST catalog service to prepare for future integrations within our Data Platform offer.
Thank you for your understanding.
Posted on Jan 09, 2026 - 17:42 UTC
Here are the details of the maintenance:
Start time : 19/01/2026 09:00 UTC
End time : 19/01/2026 18:00 UTC
Service impact : None
Service improvement : As part of our continuous improvement policy, we will deploy a new open-source REST catalog service to prepare for future integrations within our Data Platform offer.
Thank you for your understanding.
Posted on Jan 09, 2026 - 17:42 UTC
[RBX/SBG][Containers & Orchestration] - Managed Rancher Service maintenance notification Feb 17, 2026 08:30-17:00 UTC
As part of our continuous improvement plan, maintenance is scheduled on our Containers & Orchestration offer.
This may temporarily affect availability.
Start time : 17/02/2026 08:30 UTC
End time : 17/02/2026 17:00 UTC
Service impact : None
Service improvement : As part of our continuous improvement policy, we need to upgrade Ranchers in version 2.10 to version 2.11. You can already manage the upgrade by yourself through OVHcloud Control panel or API.
The Rancher compatibility matrix with downstream clusters will change, indeed K8S version 1.28 and 1.29 will no longer be officially supported.
For more information regarding Managed Rancher Service supported versions and lifecycle policy, you can visit this page: KB0064608
Thank you for your understanding.
Posted on Jan 06, 2026 - 15:42 UTC
This may temporarily affect availability.
Start time : 17/02/2026 08:30 UTC
End time : 17/02/2026 17:00 UTC
Service impact : None
Service improvement : As part of our continuous improvement policy, we need to upgrade Ranchers in version 2.10 to version 2.11. You can already manage the upgrade by yourself through OVHcloud Control panel or API.
The Rancher compatibility matrix with downstream clusters will change, indeed K8S version 1.28 and 1.29 will no longer be officially supported.
For more information regarding Managed Rancher Service supported versions and lifecycle policy, you can visit this page: KB0064608
Thank you for your understanding.
Posted on Jan 06, 2026 - 15:42 UTC