Update - Our provider is still working on resolving the issue affecting our PostgreSQL offering. To avoid issues with geospatial features, we still strongly recommend postponing any upgrade to PostgreSQL version 18 and continuing to use PostgreSQL version 17, which remains compatible with PostGIS.
For any questions, please contact your usual point of contact or reach out to our support team.
We will keep you updated on the progress and resolution.
Apr 09, 2026 - 14:08 UTC
Identified - We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our PostgreSQL offer.
Here are some supplementary details : Start time : 16/03/2026 08:00 UTC Impacted Service(s) : Customers may experience issues when upgrading to PostgreSQL version 18, as the PostGIS extension is currently not functional on this version, potentially preventing the use of geospatial features. As a precaution, we strongly recommend postponing any upgrade to PostgreSQL version 18 and continuing to use PostgreSQL version 17, which remains compatible with PostGIS. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.
If you have any questions, please contact your usual point of contact or reach out to our support team.
We will keep you updated on the progress and resolution.
Mar 30, 2026 - 12:36 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 : 18/05/2026 12:00 UTC End time : 18/05/2026 15: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
May 05, 2026 - 21:41 UTC
As part of our continuous improvement plan, a maintenance is scheduled on our Data Platform offer.
Start time : 20/05/2026 08:30 UTC End time : 20/05/2026 16:00 UTC Service impact : None Service improvement : We are currently performing an infrastructure maintenance and upgrade operation to ensure continued reliability and long-term platform support.The changes are being deployed progressively and are expected to be completed without service interruption.
Thank you for your understanding. Posted on
May 13, 2026 - 14:59 UTC
As part of our continuous improvement plan, we will be carrying out a maintenance on our electrical infrastructure in GRA9/GRA11 regions.
Start time : 25/05/2026 07:00 UTC End time : 25/05/2026 11:00 UTC Service impact : Instances will be unavailable during the maintenance. The only flavor impacted is A10. Service improvement : As part of our continuous improvement policy, we will be doing a maintenance on our electrical infrastructure.
Thank you for your understanding. Posted on
May 11, 2026 - 15:36 UTC
Update -
We are sorry to inform you that this maintenance is postponed.
As part of our continuous improvement plan, maintenance is scheduled on our Managed Kubernetes Service.
Start time : 26/05/2026 07:00 UTC End time : 28/05/2026 16:00 UTC Service impact : Customers have to anticipate this maintenance in order to adapt to the new Kubernetes version. Service improvement : As part of our continuous improvement policy, customers using Kubernetes version 1.30 will be migrated to version 1.31.
Thank you for your understanding.
Apr 15, 2026 - 14:18 UTC
Scheduled -
As part of our continuous improvement plan, maintenance is scheduled on our Managed Kubernetes Service.
Start time : 26/05/2026 07:00 UTC End time : 28/05/2026 16:00 UTC Service impact : Customers have to anticipate this maintenance in order to adapt to the new Kubernetes version. Service improvement : As part of our continuous improvement policy, customers using Kubernetes version 1.30 will be migrated to version 1.31.
Thank you for your understanding.
Mar 18, 2026 - 21:56 UTC
As part of our continuous improvement plan, maintenance is scheduled on our Containers & Orchestration offer.
This may temporarily affect availability.
Start time : 08/06/2026 07:30 UTC End time : 08/06/2026 16:00 UTC Service impact : None Service improvement : As part of our continuous improvement policy, we need to upgrade Ranchers in version 2.11 to version 2.12. 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.30 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
Apr 22, 2026 - 17:38 UTC
Resolved -
We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved.
Start time : 13/05/2026 09:03 UTC End time : 13/05/2026 09:35 UTC Root Cause :A service disruption occurred due to an unexpected underlying infrastructure malfunction.
We apologize for any inconvenience caused and appreciate your understanding.
May 13, 11:43 UTC
Investigating -
We are currently experiencing an event affecting our Compute - Instance offer GRA regions
Start time : 13/05/2026 09:03 UTC
Our teams are fully committed to investigating this issue and working towards a resolution as soon as possible. As investigations are ongoing, we will share any new findings or updates with you as soon as possible.
We apologize for any inconvenience caused and appreciate your understanding.
May 13, 09:44 UTC
Resolved -
We are pleased to inform you that the incident affecting our Managed Kubernetes Service offering has been resolved.
Start time : 11/05/2026 15:37 UTC End time : 11/05/2026 18:41 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
We apologize for any inconvenience caused and appreciate your understanding.
May 11, 18:54 UTC
Investigating -
We are currently investigating an incident affecting our Managed Kubernetes Service offering, which is causing temporary availability issue in the US-EAST-VA-1 region.
Here are some supplementary details :
Start time : 11/05/2026 15:37 UTC Impacted Service(s) : Some instances in the US-EAST-VA-1 region are unreachable. Customers Impact : Management and creation of new Managed Kubernetes Service clusters is temporarily unavailable. 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.
May 11, 15:52 UTC
Completed -
The scheduled maintenance has been completed.
May 11, 15:26 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 11, 09:00 UTC
Update -
We will be undergoing scheduled maintenance during this time.
May 11, 08:48 UTC
Scheduled -
As part of our continuous improvement plan, maintenance is scheduled on our Managed Kubernetes Service offer.
Start time : 11/05/2026 09:00 UTC End time : 11/05/2026 15:30 UTC Service impact : None Service improvement : Following our continuous improvement policy, we are rolling out an update to all cluster in a supported versions (1.34, 1.35) with an update policy of ALWAYS_UPDATE to the latest patch version.
Thank you for your understanding.
May 11, 08:41 UTC
Resolved -
We are pleased to inform you that the incident affecting our Compute - Instance offering in GRA1 region has been resolved.
Start time : 11/05/2026 06:26 UTC End time : 11/05/2026 11:45 UTC Root Cause : A service disruption occurred due to an unexpected infrastructure failure.
We apologize for any inconvenience caused and appreciate your understanding.
May 11, 12:18 UTC
Identified -
We have determined the origin of the issue affecting our Compute - Instance offer in GRA1 regions.
Here are some supplementary details :
Start time : 11/05/2026 06:26 UTC Impacted Service(s) : Some instances in GRA1 regions are unreachable. Customers Impact : Customers are temporarily unable to access instances in the specified regions. Root Cause : A service disruption occurred due to an unexpected infrastructure failure 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.
May 11, 06:40 UTC
Resolved -
We are pleased to inform you that the incident affecting our Compute - Instance offering in GRA2 has been resolved.
Start time : 11/05/2026 07:05 UTC End time : 11/05/2026 11:45 UTC Root Cause : A service disruption occurred due to an unexpected infrastructure failure.
We apologize for any inconvenience caused and appreciate your understanding.
May 11, 12:17 UTC
Identified -
We have determined the origin of the issue affecting our Compute - Instance offer in GRA2 regions.
Here are some supplementary details :
Start time : 11/05/2026 07:05 UTC Impacted Service(s) : Some instances in GRA2 regions are unreachable. Customers Impact : Customers are temporarily unable to access instances in the specified regions. Root Cause : A service disruption occurred due to an unexpected infrastructure failure 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.
May 11, 07:16 UTC
Completed -
The scheduled maintenance has been completed.
May 7, 09:31 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 5, 06:00 UTC
Scheduled -
As part of our continuous improvement plan, maintenance is scheduled on our Managed Kubernetes Service offer.
Start time : 05/05/2026 06:00 UTC End time : 07/05/2026 10:00 UTC Service impact : None Service improvement : Following our continuous improvement policy, we are rolling out an update to all cluster in a supported versions (1.33, 1.34, 1.35) with an update policy of ALWAYS_UPDATE to the latest patch version.
Thank you for your understanding.
May 4, 20:28 UTC
Resolved -
We would like to inform you that an incident occurred on our Compute - Instance offering in WAW1. This incident has now been resolved.
Please find the details of this incident below :
Start time : 07/05/2026 07:42 UTC End time : 07/05/2026 07:50 UTC Impacted Service(s) : Some instances in the WAW1 region were unreachable. Customers Impact : Customers were temporarily unable to access and use their instances located on the specified region. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
We apologize for any inconvenience caused and appreciate your understanding.
May 7, 07:55 UTC
Completed -
The scheduled maintenance has been completed.
May 6, 17:13 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 4, 09:00 UTC
Scheduled -
As part of our continuous improvement plan, maintenance is scheduled on our Block Storage offer in the RBX-A/GRA3/GRA5/GRA7/GRA9/GRA11/SBG5 regions.
Start time : 04/05/2026 09:00 UTC End time : 06/05/2026 17:00 UTC Service impact : During the maintenance window, customers may experience a temporary performance degradation. Service improvement : As part of our continuous improvement policy and to improve service quality, we will be doing a software upgrade on our Block Storage servers.
Thank you for your understanding.
Apr 30, 20:49 UTC
Completed -
The scheduled maintenance has been completed.
May 5, 12:37 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 5, 12:00 UTC
Scheduled -
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 : 05/05/2026 12:00 UTC End time : 05/05/2026 14: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.
Apr 30, 12:39 UTC
Resolved -
We are pleased to inform you that the incident affecting our Public Cloud offering has been resolved.
Start time : 04/05/2026 06:31 UTC End time : 04/05/2026 15:13 UTC Root Cause : A service disruption occurred due to an unexpected infrastructure failure.
We apologize for any inconvenience caused and appreciate your understanding.
May 4, 15:15 UTC
Update -
We have new information regarding the incident that affected your service(s).
Please find below an update on the situation: Update : Our technical team continues to work 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.
May 4, 10:46 UTC
Update -
We have determined the origin of the issue affecting our Compute - Instance offer in GRA1/GRA3/GRA5/GRA9 regions.
Here are some supplementary details :
Start time : 04/05/2026 06:31 UTC Impacted Service(s) : Some instances in GRA1/GRA3/GRA5/GRA9 regions are unreachable. Customers Impact : Customers are temporarily unable to access instances in the specified regions. Root Cause : A service disruption occurred due to an unexpected infrastructure failure 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.
May 4, 07:32 UTC
Identified -
We have determined the origin of the issue affecting our Compute - Instance offer in GRA1/GRA3/GRA5/GRA9 regions.
Here are some supplementary details :
Start time : 04/05/2026 06:31 UTC Impacted Service(s) : Some instances in GRA1/GRA3/GRA5/GRA9 regions are unreachable. Customers Impact : Customers are temporarily unable to access instances in the specified regions. Root Cause : A service disruption occurred due to an unexpected infrastructure failure 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.
May 4, 07:31 UTC
Investigating -
We are currently experiencing an event affecting our Compute - Instance offer.
Start time : 04/05/2026 06:31 UTC
Our teams are fully committed to investigating this issue and working towards a resolution as soon as possible. As investigations are ongoing, we will share any new findings or updates with you as soon as possible.
We apologize for any inconvenience caused and appreciate your understanding.
May 4, 06:58 UTC
Resolved -
We are pleased to inform you that the incident affecting our Compute - Instance offering in LIM1 has been resolved.
Start time : 02/05/2026 12:18 UTC End time : 03/05/2026 19:58 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
We apologize for any inconvenience caused and appreciate your understanding.
May 3, 20:13 UTC
Update -
We have new information regarding the incident that affected your service(s).
Please find below an update on the situation: Update : The remaining instances are still being worked on by our team. 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.
May 3, 03:08 UTC
Update -
We have new information regarding the incident that affected your service(s).
Please find below an update on the situation: Update : Most instances are now operational again. Ongoing Actions : Our team is working to fix the last remaining instances.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
May 2, 16:43 UTC
Update -
We are continuing to work on a fix for this issue.
May 2, 16:24 UTC
Identified -
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific region.
Here are some supplementary details :
Start time : 02/05/2026 12:18 UTC Impacted Service(s) : Some instances in the LIM1 region are unreachable. Customers Impact : Customers are temporarily unable to access instances located on the specified regions and Redis Database. Root Cause : A service disruption occurred due to an unexpected infrastructure failure 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.
May 2, 12:25 UTC