Public Cloud Incident History

We are pleased to inform you that the incident affecting our Storage offering has been resolved. <b>Start time :</b> 23/07/2026 18:00 UTC <b>End time :</b> 23/07/2026 23:15 UTC <b>Root Cause :</b> A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.

We have new information regarding the incident that affected your service(s). Please find below an update on the situation: <b>Update : </b> The services are operational again since 23/07/2026 23:15 UTC. <b>Ongoing Actions :</b> Our team will monitor the situation. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

We are currently investigating an incident affecting our Storage offering, which is causing temporary issue in the EU-WEST-PAR region. Here are some supplementary details : <b>Start time :</b> 23/07/2026 18:00 UTC <b>Impacted Service(s) :</b> Intermittent HTTP 503 errors may affect object upload and download operations. <b>Customers Impact :</b> Customers may experience issues downloading or uploading their objects due to 503 errors. <b>Ongoing Actions :</b> 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.

We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. <b>Start time :</b> 23/07/2026 17:52 UTC <b>End time :</b> 23/07/2026 17:58 UTC <b>Root Cause :</b> A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.

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/11 regions. Here are some supplementary details : <b>Start time :</b> 23/07/2026 17:52 UTC <b>Impacted Service(s) :</b> Some instances in the GRA1/3/9/11 regions are unreachable. <b>Customers Impact :</b> Some customers are temporarily unable to access instances located on the specified regions. <b>Root Cause :</b> A service disruption occurred due to an unexpected underlying infrastructure malfunction. <b>Ongoing Actions :</b> 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.

We are pleased to inform you that the incident affecting our Databases offering has been resolved. <b>Start time :</b> 19/07/2026 18:00 UTC <b>End time :</b> 21/07/2026 08:00 UTC <b>Root Cause :</b> A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.

<b>Update:</b> Database access has been restored across all regions. Our teams are continuing to work on the remaining impacted databases in GRA11. Pending orders are being delivered, and new orders are no longer suspended. Monitoring remains in place to ensure long-term stability. We apologize for any inconvenience caused and appreciate your understanding and patience.

Please find an update of this incident below : <b>Update:</b> Database access is being progressively restored in all regions, with the exception of GRA11. Pending orders are now being progressively delivered. As a precaution, new orders remain temporarily suspended. <b>Ongoing Actions :</b> Our teams continue to restore the remaining impacted region and are closely monitoring the situation. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

We have new information regarding the incident that affected your service(s). Please find below an update on the situation: <b>Update : </b> Customers are temporarily unable to access and fork their databases. Please note that no data has been lost, and all data remains intact. <b>Ongoing Actions :</b> 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.

We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Databases offering Here are some supplementary details : <b>Start time :</b> 19/07/2026 18:00 UTC <b>Impacted Service(s) :</b> Some Database are temporarily unavailable. <b>Customers Impact :</b> Customers are temporarily unable to access their Database located on the specified region. <b>Root Cause :</b> A service disruption occurred due to an unexpected underlying infrastructure malfunction. <b>Ongoing Actions :</b> 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.

We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. <b>Start time :</b> 20/07/2026 15:02 UTC <b>End time :</b> 20/07/2026 15:10 UTC <b>Root Cause :</b> A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.

Service has been fully restored since 20/07/2026 15:10 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : <b>Start time :</b> 20/07/2026 15:02 UTC <b>Impacted Service(s) :</b> Some instances in the GRA5, GRA7, GRA9 and GRA11 regions were unreachable. <b>Customers Impact :</b> Some customers were temporarily unable to access instances located on the specified regions. We apologize for any inconvenience caused and appreciate your understanding.

We are pleased to inform you that the incident affecting our Compute - Instance offering in GRA11 has been resolved. <b>Start time :</b> 19/07/2026 16:50 UTC <b>End time :</b> 19/07/2026 19:14 UTC <b>Root Cause :</b> This incident was caused by our provider. We apologize for any inconvenience caused and appreciate your understanding.

We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific region GRA11. Here are some supplementary details : <b>Start time :</b> 19/07/2026 16:50 UTC <b>Impacted Service(s) :</b> Creation of Public Cloud instances in GRA11 region is temporarily unavailable. <b>Customers Impact :</b> Customers are temporarily unable to create new Public Cloud instances. Instances created during the incident will remain stuck in a "building"/"spawning" state and will not become operational. Once the incident is resolved, customers are advised to delete these instances and create new ones. <b>Root Cause :</b> This incident is caused by our provider. <b>Ongoing Actions :</b> 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.

We are pleased to inform you that the incident affecting our Compute - Instance offering in GRA11 has been resolved. <b>Start time :</b> 19/07/2026 08:00 UTC <b>End time :</b> 19/07/2026 15:32 UTC <b>Root Cause :</b> This incident was caused by our provider. We apologize for any inconvenience caused and appreciate your understanding.

We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific region GRA11. Here are some supplementary details : <b>Start time :</b> 19/07/2026 08:00 UTC <b>Impacted Service(s) :</b> Creation of Public Cloud instances in GRA11 region is temporarily unavailable. <b>Customers Impact :</b> Customers are temporarily unable to create new Public Cloud instances. Instances created during the incident will remain stuck in a "building"/"spawning" state and will not become operational. Once the incident is resolved, customers are advised to delete these instances and create new ones. <b>Root Cause :</b> This incident is caused by our provider. <b>Ongoing Actions :</b> 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.

We are pleased to inform you that the incident affecting our AI & Machine Learning offering on AI Deploy, AI Training and AI Notebooks has been resolved. <b>Start time :</b> 19/07/2026 12:40 UTC <b>End time :</b> 19/07/2026 14:30 UTC <b>Root Cause :</b> This incident was caused by our provider. We apologize for any inconvenience caused and appreciate your understanding.

We are currently investigating an incident affecting our AI & Machine Learning offering, which is causing temporary issue in the GRA region. Here are some supplementary details : <b>Start time :</b> 19/07/2026 12:40 UTC <b>Impacted Service(s) :</b> AI Deploy, AI Training and AI Notebooks are temporarily unavailable. <b>Customers Impact :</b> Customers are temporarily unable to access and use models in the specified offers. <b>Ongoing Actions :</b> 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.

We are pleased to inform you that the incident affecting our Logs Data Platform service has been resolved. <b>Start time :</b> 15/07/2026 18:00 UTC <b>End time :</b> 16/07/2026 13:00 UTC <b>Root Cause :</b> This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.

We are currently experiencing an incident affecting our Logs Data Platform service, which is causing temporary availability issues. Please find the details of this incident below : <b>Start time :</b> 15/07/2026 18:00 UTC <b>Impacted Service(s) :</b> The WebSocket connection on Logs Data Platform is temporarily unavailable. <b>Customers Impact :</b> Customers are temporarily unable to use the Logs Data Platform WebSocket connection. <b>Ongoing Actions :</b> 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.

We are pleased to inform you that the incident affecting our Object Storage Swift offering has been resolved. <b>Start time :</b> 14/07/2026 07:49 UTC <b>End time :</b> 14/07/2026 08:15 UTC <b>Root Cause :</b> A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.

We have determined the origin of the issue affecting our Object Storage Swift offer in WAW. Here are some supplementary details : <b>Start time :</b> 14/07/2026 07:59 UTC <b>Impacted Service(s) :</b> Object Storage Swift is temporarily unavailable. <b>Customers Impact :</b> Customers may experience connection problems while trying to access Object Storage Swift in WAW. <b>Root Cause :</b> A service disruption occurred due to an unexpected underlying infrastructure malfunction. <b>Ongoing Actions :</b> 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.

We are currently investigating an incident affecting our Object Storage offering, which is causing temporary availability issue in the region WAW. Here are some supplementary details : <b>Start time :</b> 14/07/2026 07:49 UTC <b>Impacted Service(s) :</b> Object Storage Swift <b>Customers Impact :</b> Customers may experience connection problems while trying to access Object Storage Swift in WAW. <b>Ongoing Actions :</b> 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.

We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. <b>Start time :</b> 13/07/2026 16:55 UTC <b>End time :</b> 13/07/2026 22:55 UTC <b>Root Cause :</b> A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.

We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific BHS1/BHS5 regions. Here are some supplementary details : <b>Start time :</b> 13/07/2026 16:55 UTC <b>Impacted Service(s) :</b> Some instances in the BHS1/BHS5 regions are unreachable. <b>Customers Impact :</b> Some customers are temporarily unable to access instances located on the specified regions. <b>Root Cause :</b> A service disruption occurred due to an unexpected underlying infrastructure malfunction. <b>Ongoing Actions :</b> 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.

We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific BHS1/BHS5 regions. Here are some supplementary details : <b>Start time :</b> 13/07/2026 16:55 UTC <b>Impacted Service(s) :</b> Some instances in the BHS1/BHS5 regions are unreachable. <b>Customers Impact :</b> Some customers are temporarily unable to access instances located on the specified regions. <b>Root Cause :</b> A service disruption occurred due to an unexpected underlying infrastructure malfunction. <b>Ongoing Actions :</b> 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.

We are pleased to inform you that the incident affecting our Network offering has been resolved. <b>Start time :</b> 09/07/2026 13:40 UTC <b>End time :</b> 13/07/2026 11:10 UTC <b>Root Cause :</b> This incident is caused by another incident : https://network.status-ovhcloud.com/incidents/cfjg549ghh2y We apologize for any inconvenience caused and appreciate your understanding.

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 : <b>Start time :</b> 09/07/2026 13:40 UTC <b>Impacted Service(s) :</b> Paquet loss is being observed for IPv6. <b>Customers Impact :</b> Customers are temporarily facing packet loss on IPv6 when using services located in GRA region. <b>Root Cause :</b> This incident is caused by another incident : https://network.status-ovhcloud.com/incidents/cfjg549ghh2y <b>Ongoing Actions :</b> 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.