Update - Scheduled maintenance is still in progress. We will provide updates as necessary.
Jul 10, 2026 - 13:55 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 10, 2026 - 09:05 UTC
Scheduled - Please be informed we will be performing a mandatory maintenance to upgrade our Public Cloud Infrastructure.
During this maintenance window, services will be impacted for approximately 30 minutes or less.
Start time : 10/07/2026 08:00 UTC
Important information : • If instances do not return by the end of the maintenance window, please try a simple reboot on your end first. If this does not work, please raise an incident to Support to address the issue.
Thank you for your understanding.
Jul 10, 202611:03-12:03 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 10, 2026 - 13:44 UTC
Scheduled - Please be informed we will be performing a mandatory maintenance to upgrade our Public Cloud Databases.
Start time : 10/07/2026 09:58 UTC Service impact : Single-node (non-HA) services will be temporarily unavailable during the operation, whereas redundant, high-availability multi-node services fail over automatically and remain available. Management operations (create, delete, update, and upgrade) may experience slower processing times during this period. We recommend our high-availability offerings for customers who require uninterrupted service continuity. Service improvement : This upgrade strengthens the reliability and performance of our Public Cloud databases.
Thank you for your understanding.
Jul 10, 202613:45-14:45 UTC
Identified - We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Network offer on the specific region.
Here are some supplementary details :
Start time : 09/07/2026 13:40 UTC Impacted Service(s) : Paquet loss is being observed for IPv6. Customers Impact : Customers are temporarily facing packet loss on IPv6 when using services located in GRA region. Root Cause : This incident is caused by another incident : https://network.status-ovhcloud.com/incidents/cfjg549ghh2y 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.
Jul 09, 2026 - 13:45 UTC
Monitoring - We have new information regarding the incident that affected your service(s).
Please find below an update on the situation: Update : PostGIS support for PostgreSQL 18 was introduced in a newer PostGIS version. However, an identified defect carries a risk of data corruption for geospatial data, so we have chosen not to enable it on our offer yet. We are waiting for a PostGIS release that fixes this issue before allowing PostGIS to be used on PostgreSQL 18. As a reminder, this only affects customers using the PostGIS extension. PostgreSQL instances that do not use PostGIS are not impacted. In the meantime, we still strongly recommend that PostGIS users postpone any upgrade to PostgreSQL 18 and remain on PostgreSQL 17, which is fully compatible with PostGIS. 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.
Jul 08, 2026 - 14:22 UTC
Update - We have new information regarding the incident that affected your service(s).
Please find below an update on the situation: Update : PostGIS support for PostgreSQL 18 was introduced in a newer PostGIS version. However, an identified defect carries a risk of data corruption for geospatial data, so we have chosen not to enable it on our offer yet. We are waiting for a PostGIS release that fixes this issue before allowing PostGIS to be used on PostgreSQL 18. As a reminder, this only affects customers using the PostGIS extension. PostgreSQL instances that do not use PostGIS are not impacted. In the meantime, we still strongly recommend that PostGIS users postpone any upgrade to PostgreSQL 18 and remain on PostgreSQL 17, which is fully compatible with PostGIS. Ongoing Actions : We are closely monitoring the situation while the PostGIS team works on a resolution.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
Jun 11, 2026 - 08:45 UTC
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 and have determined origin of the issue to PostGIS plugin, affecting our PostgreSQL offer when using this specific plugin in version 3.5 and PG18.
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 PostGIS extension current version 3.5. Ongoing Actions : The PostGIS team needs to fix this bug and release a new version of the extension (v3.6). In the meantime, our services remain fully functional without PostGIS.
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
Update -
We will be undergoing scheduled maintenance during this time.
Jul 09, 2026 - 07:17 UTC
Scheduled -
As part of our continuous improvement plan, a maintenance is scheduled on our Compute - Instance infrastructure.
Start time : 15/07/2026 06:00 UTC End time : 15/07/2026 08:00 UTC Service impact : Some instances located in GRA region will be temporarily unavailable during the maintenance. Service improvement : As part of our continuous improvement policy, we will be doing a maintenance on our infrastructure in the specified region.
Thank you for your understanding.
Jun 16, 2026 - 20:30 UTC
As part of our continuous improvement plan, a maintenance is scheduled on our Object Storage offer.
Start time : 15/07/2026 07:00 UTC End time : 22/07/2026 16:00 UTC Service impact : S3-compatible Object Storage endpoints will now support IPv6 in dual-stack mode (IPv4 and IPv6), while maintaining unchanged IPv4 connectivity. However, customers with misconfigured IPv6 networking may experience connectivity issues when accessing S3-compatible Object Storage. Below you can find the table regarding the endpoints and records being added:
As part of our continuous improvement plan, a maintenance is scheduled on our Data Platform offer.
Start time : 20/07/2026 12:00 UTC End time : 20/07/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
Jul 08, 2026 - 15:33 UTC
Start time : 15/08/2026 06:00 UTC End time : 15/08/2026 16:00 UTC Service impact : Public Cloud instances hosted in the AP-SOUTHEAST-SYD-2 region Service improvement : As part of the continuous evolution of our Public Cloud offering, OVHcloud will progressively phase out the AP-SOUTHEAST-SYD-2 region in Sydney and focus future developments on the SYD1 region. Services hosted in AP-SOUTHEAST-SYD-2 will enter maintenance mode before a definitive shutdown in the coming months. Affected customers must manually migrate their workloads and data to the SYD1 region to avoid service disruption.
Required customer actions Customers are required to: - Create new instances in the SYD1 region - Manually migrate applications, services, and data - Validate workloads on the new infrastructure - Stop and delete old instances once migration is completed
To compensate for the inconvenience, OVHcloud will automatically apply a credit corresponding to one month of the affected services usage. Posted on
May 28, 2026 - 09:48 UTC
As part of maintenance for the Logs Data Platform, we will replace the certificates for your Data-gathering tools on 16 September 2026, as the current intermediate certificate expires on 20 September 2026.
Start time : 16/09/2026 10:30 UTC End time : 16/09/2026 19:30 UTC Service impact : Customers who send their logs directly to the clusters are not affected by this maintenance and can disregard the rest of this message (Customer's log ingestion endpoint looks like gra1.logs.ovh.com:12202, no action is required). However, customers who use an endpoint such as gra1-65d66a0a68728d746bbebbab.gra1.logs.ovh.com:6514 are affected by this maintenance and we recommend them to follow the relevant action plan below.
Case 1 — The customer's log forwarder agent performs no certificate verification Customers who keep this behavior will not be impacted by the maintenance. No action is required.
Case 2 — The customer's log forwarder agent validates only the intermediate chain 1. Import the new certificate chain (as soon as possible). The new chain (self-signed, valid for 10 years) is already available in the OVHcloud Manager, on the home page of the customer's Logs Data Platform service. Customers should import it into their configuration before 16 September 2026. 2. Keep the old chain in place temporarily. Until 16 September 2026, customers should leave the old chain in their configuration so the agent accepts both chains (old + new) during the transition window, avoiding any surprise. 3. After 16 September 2026, once the maintenance is complete, customers should remove the old chain and keep only the new one (valid for 10 years).
Case 3 — The customer's log forwarder agent validates the intermediate + Data-gathering-tool certificate chain 1. Create a new Data-gathering tool in the Logs Data Platform project, replicating the exact configuration of the previous one. 2. Import the full certificate chain (intermediate + new self-signed certificate). Customers should go to the Data-gathering tools page, then open the "Useful information" section to obtain it. 3. Update the log forwarder agent configuration to push logs to this new Data-gathering tool. 4. Delete the old Data-gathering tool. Service improvement : This maintenance renews the certificate chain that secures your log ingestion, ensuring uninterrupted and secure log delivery. The new chain is self-signed and valid for 10 years.
Thank you for your understanding. Posted on
Jul 03, 2026 - 09:47 UTC
We apologize for any inconvenience caused and appreciate your understanding.
Jul 11, 00:18 UTC
Identified -
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Managed Private Registry service on the EU-WEST-PAR region.
Here are some supplementary details :
Start time : 10/07/2026 20:20 UTC Impacted Service(s) : Registries are temporarily unavailable. Customers Impact : Customers are temporarily facing issues when trying to use connect to Harbor UI, pull or push new images. Root Cause : This incident is caused by this maintenance : https://public-cloud.status-ovhcloud.com/incidents/m5qn00qgl9zh 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.
Jul 10, 21:30 UTC
Resolved -
We are pleased to inform you that the incident affecting our Load Balancer service has been resolved.
Start time : 09/07/2026 19:20 UTC End time : 10/07/2026 01:50 UTC Root Cause : This incident was caused by a software issue.
We apologize for any inconvenience caused and appreciate your understanding.
Jul 10, 01:55 UTC
Identified -
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Load Balancer service on the specific region.
Here are some supplementary details :
Start time : 09/07/2026 19:20 UTC Impacted Service(s) : Public Cloud API is temporarily facing perturbations. Creation or modification of any LoadBalancer can have issues. Customers Impact : Customers are temporarily facing issues when trying to use the API, create or modify their Loadbalancer. Root Cause : This incident is caused by a software issue. 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.
Jul 9, 20:19 UTC
Investigating -
We are currently investigating an incident affecting our Containers & Orchestration offering, which is causing temporary issue in the EU-WEST-PAR region.
Here are some supplementary details :
Start time : 09/07/2026 19:20 UTC Impacted Service(s) : Public Cloud API is temporarily facing perturbations. Creation or modification of any LoadBalancer can have issues. Customers Impact : Customers are temporarily facing issues when trying to use the API, create or modify their Loadbalancer. 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.
Jul 9, 20:07 UTC
Completed -
The scheduled maintenance has been completed.
Jul 9, 15:40 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 9, 08:00 UTC
Scheduled -
As part of the end-of-life of our Containers & Orchestration - Load Balancer (IOLB) offer, a maintenance is scheduled in BHS5 / DE1 / GRA5 / GRA7 / GRA9 / GRA11 / SBG5 / SGP1 / SYD1 / WAW1 / UK1 / US-EAST-VA / US-WEST-OR regions.
Start time : 09/07/2026 08:00 UTC End time : 09/07/2026 16:00 UTC Service impact : We're retiring the historical Load Balancer for Managed Kubernetes, now replaced by the Public Cloud Loadbalancer. As part of this change, resources will be deleted and no longer billed. Note: the migration to Public Cloud Loadbalancer is not automatic and must be performed on your side. (https://docs.ovhcloud.com/en/guides/public-cloud/containers-orchestration/managed-kubernetes/migrate-iolb-to-public-cloud-loadbalancer) Service improvement : As part of our continuous improvement policy, we will be doing a maintenance on our Containers & Orchestration - Load Balancer in the specified regions.
Thank you for your understanding.
Jun 4, 16:27 UTC
Completed -
The current maintenance has been canceled and it will be rescheduled later.
Jul 9, 13:54 UTC
Scheduled -
As part of our continuous improvement plan, maintenance is scheduled on our Identity, Security & Operations offer in APAC region.
Start time : 09/07/2026 14:00 UTC End time : 09/07/2026 15:00 UTC Service impact : None Service improvement : As part of our continuous improvement policy, we will be doing a maintenance on our Identity, Security & Operations infrastructure.
Thank you for your understanding.
Jul 2, 20:10 UTC
Resolved -
We had an incident on S3 Object Storage offer which has now been resolved.
Here are some supplementary details :
Start time : 09/07/2026 11:46 UTC End time : 09/07/2026 11:48 UTC Impacted Service(s) : Object storage service in SBG region was temporarily unavailable for some customers. Customers Impact : Some customers were getting 503 error when trying to connect to their object storage located in the specified region. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
We thank you for your understanding and patience throughout this incident.
Jul 9, 12:24 UTC
Resolved -
We are pleased to inform you that the incident affecting our Object Storage Swift offering has been resolved.
Start time : 06/07/2026 14:00 UTC End time : 06/07/2026 15:25 UTC Root Cause : This incident was caused by a software issue.
We apologize for any inconvenience caused and appreciate your understanding.
Jul 8, 12:43 UTC
Monitoring -
Service has been fully restored since 06/07/2026 15:25 UTC. Monitoring remains active to ensure long-term stability.
Here are some supplementary details :
Start time : 06/07/2026 14:00 UTC Impacted Service(s) : Slowness and 504 error in response time Customers Impact : Some customers might have faced slowness or 504 error in response time in specified region.
We apologize for any inconvenience caused and appreciate your understanding.
Jul 6, 15:31 UTC
Investigating -
We are currently investigating an incident affecting our Object Storage Swift offering, which is causing temporary functionality issue in GRA region.
Here are some supplementary details :
Start time : 06/07/2026 14:00 UTC Impacted Service(s) : Slowness and 504 error in response time Customers Impact : Some customers might face slowness or 504 error in response time in specified region. 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.
Jul 6, 14:22 UTC
Resolved -
We are pleased to inform you that the incident affecting our Containers & Orchestration offering has been resolved.
Start time : 06/07/2026 20:08 UTC End time : 07/07/2026 01:25 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
We apologize for any inconvenience caused and appreciate your understanding.
Jul 8, 09:34 UTC
Monitoring -
Service has been fully restored since 07/07/2026 01:25 UTC. Monitoring remains active to ensure long-term stability.
Here are some supplementary details :
Start time : 06/07/2026 20:08 UTC Impacted Service(s) : The Managed Kubernetes Service experienced delays in managed node provisioning. Customers Impact : Customers may have experienced network disruptions when using the load balancer and delays in managed node delivery. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
We apologize for any inconvenience caused and appreciate your understanding.
Jul 7, 01:43 UTC
Investigating -
We are currently investigating an incident affecting our Containers & Orchestration offering, which is causing temporary availability issue in the GRA5/7/9/11 regions.
Here are some supplementary details :
Start time : 06/07/2026 20:08 UTC Impacted Service(s) : The Managed Kubernetes Service is experiencing delays in managed node provisioning. Customers Impact : Customers may experience network disruptions when using the load balancer and delays in managed node delivery. 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.
Jul 6, 23:30 UTC
Resolved -
We are pleased to inform you that the incident affecting our Containers & Orchestration offering has been resolved.
Start time : 06/07/2026 20:08 UTC End time : 07/07/2026 01:25 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
We apologize for any inconvenience caused and appreciate your understanding.
Jul 8, 09:34 UTC
Monitoring -
Service has been fully restored since 07/07/2026 01:25 UTC. Monitoring remains active to ensure long-term stability.
Here are some supplementary details :
Start time : 06/07/2026 20:08 UTC Impacted Service(s) : The Managed Private Registry service experienced intermittent disruptions or temporary unavailability. Customers Impact : Customers may have experienced issues pushing, pulling, or deploying container images. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
We apologize for any inconvenience caused and appreciate your understanding.
Jul 7, 01:39 UTC
Investigating -
We are currently investigating an incident affecting our Containers & Orchestration offering, which is causing temporary availability issue in the GRA region.
Here are some supplementary details :
Start time : 06/07/2026 20:08 UTC Impacted Service(s) : The Managed Private Registry service may experience intermittent disruptions or temporary unavailability. Customers Impact : Customers may experience issues pushing, pulling, or deploying container images. 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.
Jul 6, 22:24 UTC
Resolved -
We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved.
Start time : 06/07/2026 20:08 UTC End time : 07/07/2026 21:34 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
We apologize for any inconvenience caused and appreciate your understanding.
Jul 8, 09:31 UTC
Update -
Service has been fully restored since 07/07/2026 21:34 UTC. Monitoring remains active to ensure long-term stability.
Here are some supplementary details :
Start time : 06/07/2026 20:08 UTC Impacted Service(s) : Public network experienced availability and latency issues. Customers Impact : Customers experienced temporary service unavailability or increased latency when accessing their services. Root Cause : This incident was caused by a network equipment issue.
Jul 7, 21:53 UTC
Update -
Ongoing Actions: At 20:30 UTC, we will perform an upgrade on the affected network equipment to prevent this issue from recurring.
No customer impact is expected during this maintenance.
Our teams will closely monitor service stability throughout the operation and will remain mobilized until the maintenance has been successfully completed.
We will keep you informed of the progress and notify you once the maintenance has been completed.
We apologize for any inconvenience caused and appreciate your understanding.
Jul 7, 18:33 UTC
Update -
Please find the details of this incident below :
Start time : 06/07/2026 20:08 UTC Impacted Service(s) : Public network experienced availability and latency issues. Customers Impact : Customers experienced temporary service unavailability or increased latency when accessing their services. Root Cause : This incident was caused by a network equipment issue. Ongoing Actions : Our team isolated the affected network equipment to restore service. The service has been restored since 07/07/2026 01:25 UTC. Ongoing Actions : Our teams are continuing to investigate the root cause of the incident while closely monitoring system stability to ensure continued stability.
We will keep you updated on the progress of our investigation. We apologize for any inconvenience caused and appreciate your understanding.
Jul 7, 14:17 UTC
Monitoring -
Service has been fully restored since 07/07/2026 01:25 UTC. Monitoring remains active to ensure long-term stability.
Here are some supplementary details :
Start time : 06/07/2026 20:08 UTC Impacted Service(s) : Network perturbation was observed for some instances in the GRA1/3/4/5/7/9/11 regions. Customers Impact : Some customers were temporarily facing packet loss on their instances located in the specified regions. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
We apologize for any inconvenience caused and appreciate your understanding.
Jul 7, 09:50 UTC
Resolved -
We are pleased to inform you that the incident affecting our AI payload offering has been resolved.
Start time : 07/07/2026 11:45 UTC End time : 07/07/2026 11:56 UTC Root Cause : This incident was caused by a network equipment issue.
We apologize for any inconvenience caused and appreciate your understanding.
Jul 7, 15:10 UTC
Monitoring -
Service has been fully restored since 07/07/2026 11:56 UTC. Monitoring remains active to ensure long-term stability.
Here are some supplementary details :
Start time : 07/07/2026 11:45 UTC Impacted Service(s) : Creation of AI payloads was temporarily unavailable in GRA region. Customers Impact : Customers were temporarily unable to create AI payloads.
We apologize for any inconvenience caused and appreciate your understanding.
Jul 7, 12:31 UTC
Completed -
All services are operational.
Jul 6, 17:23 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 6, 12:00 UTC
Scheduled -
As part of our continuous improvement plan, a maintenance is scheduled on our Data Platform offer.
Start time : 06/07/2026 12:00 UTC End time : 06/07/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.
Jun 23, 17:24 UTC
Resolved -
We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved.
Start time : 03/07/2026 12:55 UTC End time : 03/07/2026 18:20 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
We apologize for any inconvenience caused and appreciate your understanding.
Jul 3, 18:57 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 GRA1/3/9 regions.
Here are some supplementary details :
Start time : 03/07/2026 12:55 UTC Impacted Service(s) : Some instances in the GRA1/3/9 regions are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on the specified regions. 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.
Jul 3, 13:39 UTC
Resolved -
We had an incident on AI & Machine Learning offer which has now been resolved.
Here are some supplementary details :
Start time : 02/07/2026 15:00 UTC End time : 03/07/2026 08:15 UTC Impacted Service(s) : All models on AI Endpoints have experienced latency and some 503 errors. Customers Impact : Customers experienced increased latency and intermittent 503 errors across all models on AI Endpoints. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
We thank you for your understanding and patience throughout this incident.
Jul 3, 13:05 UTC
Resolved -
We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved.
Start time : 01/07/2026 17:32 UTC End time : 01/07/2026 18:54 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
We apologize for any inconvenience caused and appreciate your understanding.
Jul 1, 19:21 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 GRA Region.
Here are some supplementary details :
Start time : 01/07/2026 17:32 UTC Impacted Service(s) : Some instances in the GRA7 region are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on the specified regions. 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.
Jul 1, 17:54 UTC
We apologize for any inconvenience caused and appreciate your understanding.
Jul 1, 19:15 UTC
Identified -
We are currently experiencing an incident affecting our Containers & Orchestration - Managed Private Registry offering, which is causing temporary functionality issues in the GRA region.
Here is detail for this incident : Start time : 01/07/2026 17:32 UTC Impacted Service(s) : Some Registries are unreachable in the GRA region. Customers Impact : Some customers are temporarily unable to do management operations on their Registries in the specified region. 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.
Jul 1, 19:14 UTC
We apologize for any inconvenience caused and appreciate your understanding.
Jul 1, 18:55 UTC
Update -
We are continuing to work on a fix for this issue.
Jul 1, 18:50 UTC
Identified -
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Containers & Orchestration offer on the specific DE1 region.
Here are some supplementary details :
Start time : 01/07/2026 17:32 UTC Impacted Service(s) : Customer may have difficulties to do some cluster action Customers Impact : Customer may have difficulties to manage their cluster on DE1 region Root Cause :https://public-cloud.status-ovhcloud.com/incidents/x3cj8gldm5yx 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.
Jul 1, 18:32 UTC
Completed -
We would like to inform you that the maintenance on our Containers & Orchestration is now completed.
Thank you for your patience throughout this maintenance.
Jul 1, 17:29 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 1, 07:30 UTC
Scheduled -
As part of our continuous improvement plan, maintenance is scheduled on our Containers & Orchestration offer.
Start time : 01/07/2026 07:30 UTC End time : 01/07/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.
Apr 22, 17:38 UTC
Completed -
We would like to inform you that the maintenance on our Public Cloud infrastructure is now completed. All services are operational.
Thank you for your patience throughout this maintenance.
Jul 1, 13:15 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 1, 07:52 UTC
Scheduled -
As part of our continuous improvement plan, a maintenance is scheduled on our Public Cloud infrastructure.
Start time : 01/07/2026 07:30 UTC End time : 01/07/2026 14:00 UTC Service impact : None. Service improvement : As part of our continuous improvement policy, we will be doing a maintenance on our infrastructure in the GRA5/79/11 regions.
Thank you for your understanding.
Jul 1, 07:51 UTC
Resolved -
We are pleased to inform you that the incident affecting our Block Storage offering in BHS1 region has been resolved.
Start time : 29/06/2026 14:07 UTC End time : 29/06/2026 18:40 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
We apologize for any inconvenience caused and appreciate your understanding.
Jun 29, 18:47 UTC
Update -
We have new information regarding the incident that affected your service(s).
Please find below an update on the situation: Impacted Service(s) : The block storage service was again unavailable for some customers in BHS1 region between 29/06/2026 17:00 UTC and 29/06/2026 18:00 UTC. Ongoing Actions : Our teams are continuing to work on the remaining block storage hosts that were impacted by this incident. As this work is ongoing, customers may experience some temporary degradation in performance.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
Jun 29, 18:10 UTC
Update -
We have new information regarding the incident that affected your service(s).
Please find below an update on the situation: Update : Customers are now able to access their block storage and normal operations have largely resumed. Ongoing Actions : Our teams are continuing to work on the remaining block storage hosts that were impacted by this incident. As this work is ongoing, customers may experience some temporary degradation in performance.
We will keep you updated on the progress and full resolution.
We apologize for any inconvenience caused and appreciate your understanding.
Jun 29, 15:46 UTC
Update -
We have new information regarding the incident that affected your service(s).
Please find below an update on the situation: Update : The majority of the block storage hosts in BHS1 region are no longer impacted by this incident. Ongoing Actions : Our teams are currently working on the last impacted block storage hosts.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
Jun 29, 14:59 UTC
Identified -
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Block Storage offer on the specific region BHS1.
Here are some supplementary details :
Start time : 29/06/2026 14:07 UTC Impacted Service(s) : The block storage service is temporarily unavailable for some customers in BHS1 region. Customers Impact : Some customers are unable to access and use their block storage loacted in the specified region. 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.
Jun 29, 14:43 UTC
Resolved -
We are pleased to inform you that the incident affecting our Compute - Instance offering in GRA1 and GRA11 regions has been resolved.
Start time : 28/06/2026 18:45 UTC End time : 28/06/2026 20:17 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
We apologize for any inconvenience caused and appreciate your understanding.
Jun 28, 20:21 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 regions GRA1 and GRA11.
Here are some supplementary details :
Start time : 28/06/2026 18:45 UTC Impacted Service(s) : Some instances in GRA1 and GRA11 regions are unreachable. Customers Impact : Some customers are temporarily unable to access their instances located in GRA1 and GRA11 regions. 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.
Jun 28, 19:10 UTC
Resolved -
We are pleased to inform you that the incident affecting our Compute - Instance offering in BHS1, BHS3 and BHS5 regions has been resolved.
Start time : 28/06/2026 17:04 UTC End time : 28/06/2026 17:45 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
We apologize for any inconvenience caused and appreciate your understanding.
Jun 28, 17:53 UTC
Investigating -
We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary availability issue in the BHS1, BHS3 and BHS5 regions.
Here are some supplementary details :
Start time : 28/06/2026 17:04 UTC Impacted Service(s) : Some instances in the BHS1, BHS3 and BHS5 regions are unreachable. Customers Impact : Some customers are temporarily unable to access their instances located in BHS1, BHS3 and BHS5 regions. 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.
Jun 28, 17:15 UTC
Resolved -
We had an incident on Compute - Instance offer in DE1 region which has now been resolved.
Here are some supplementary details :
Start time : 28/06/2026 12:55 UTC End time : 28/06/2026 13:03 UTC Impacted Service(s) : Some instances in the DE1 region were unreachable. Customers Impact : Some customers were temporarily unable to access their instances located in DE1 region. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
We thank you for your understanding and patience throughout this incident.
Jun 28, 13:08 UTC