Public Cloud Outage History
Public Cloud is up right nowPingoru has recorded 205 incidents for Public Cloud: 205 in the last 12 months and 69 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 28 | 57 of 720 (8%) |
| May 2026 | 20 | 285 of 744 (38%) |
| June 2026 | 31 | 268 of 720 (37%) |
| July 2026 | 28 | 235 of 744 (32%) |
| August 2026 | 22 | 288 of 744 (39%) |
| September 2026 | 21 | 397 of 720 (55%) |
| October 2026 | 24 | 300 of 592 (51%) |
Incidents, newest first
Major May 11, 2026 [GRA1][Public Cloud] - Compute - Instance Incident Notification 5h 37m GRA1
Started May 11, 2026, 06:40 AM UTC· resolved May 11, 2026, 12:18 PM UTC
- identified May 11, 2026, 06:40 AM UTC
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.
- resolved May 11, 2026, 12:18 PM UTC
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.
Notice May 7, 2026 [WAW1][Compute - Instance] - Instance incident notification – WAW1
Started May 07, 2026, 07:55 AM UTC· resolved May 07, 2026, 07:55 AM UTC
- resolved May 07, 2026, 07:55 AM UTC
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.
Major May 4, 2026 [GRA1/GRA3/GRA5/GRA9][Public Cloud] - Compute - Instance Incident Notification 8h 17m GRA1, GRA3, GRA5, GRA9
Started May 04, 2026, 06:58 AM UTC· resolved May 04, 2026, 03:15 PM UTC
- investigating May 04, 2026, 06:58 AM UTC
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.
- identified May 04, 2026, 07:31 AM UTC
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.
- identified May 04, 2026, 07:32 AM UTC
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.
- identified May 04, 2026, 10:46 AM UTC
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.
- resolved May 04, 2026, 03:15 PM UTC
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.
Major May 2, 2026 [LIM1][Compute - Instance] - Cloud Compute Incident Notification 1d 7h DE1, GRA
Started May 02, 2026, 12:25 PM UTC· resolved May 03, 2026, 08:13 PM UTC
- identified May 02, 2026, 12:25 PM UTC
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. 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.
- identified May 02, 2026, 04:24 PM UTC
We are continuing to work on a fix for this issue.
- identified May 02, 2026, 04:43 PM UTC
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.
- identified May 03, 2026, 03:08 AM UTC
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 teams. 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.
- resolved May 03, 2026, 08:13 PM UTC
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.
Major May 1, 2026 [ERI1][Compute - Instance] - Cloud Compute Incident Notification 1h 5m UK1
Started May 01, 2026, 07:29 AM UTC· resolved May 01, 2026, 08:34 AM UTC
- identified May 01, 2026, 07:29 AM UTC
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 : 01/05/2026 07:19 UTC Impacted Service(s) : Some instances in the ERI1 region are unreachable. Customers Impact : Customers are temporarily unable to access instances located on 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.
- resolved May 01, 2026, 08:34 AM UTC
We are pleased to inform you that the incident affecting our Dedicated Servers has been resolved. Start time : 01/05/2026 07:19 UTC End time : 01/05/2026 08:20 UTC Root Cause : This incident was caused by a network equipment issue. We apologize for any inconvenience caused and appreciate your understanding.
Notice April 30, 2026 [GLOBAL][Containers & Orchestration] - Managed Kubernetes Service event notification – AP-SOUTH-MUM, BHS5, EU-WEST-LIM, EU-SOUTH-MIL and 13 more
Started Apr 30, 2026, 04:16 PM UTC· resolved Apr 30, 2026, 04:16 PM UTC
- identified Apr 30, 2026, 03:27 PM UTC
We are currently experiencing an ongoing security event affecting our Managed Kubernetes Service. The source of the issue has been identified. Start time : 22/04/2026 08:15 UTC Impacted service(s) : Managed Kubernetes Service (MKS) worker nodes. Customer impact : A recently disclosed security vulnerability may allow a user within a container to gain elevated access on the underlying node. This issue is limited to individual clusters and does not impact other customers or the managed control plane. Customers running shared or multi-tenant workloads within the same cluster should consider this issue with higher priority. Other OVHcloud managed services (MPR, MRS) are patched transparently by OVHcloud, no customer action required. Root Cause : This incident is caused by a software issue. Workaround : A temporary mitigation is available to reduce the risk while we prepare a permanent fix. Instructions are available in our dedicated blog post: https://blog.ovhcloud.com/copy-fail-cve-2026-31431-how-to-rapidly-protect-ovhcloud-mks-clusters-from-the-linux-kernel-zero-day Please note that applying this mitigation is optional and remains under your responsibility. If the vulnerability has already been exploited on your cluster, this mitigation will not remediate any pre-existing compromise Ongoing actions : Our teams are actively working on a permanent fix. Updated versions are expected to be available later today. We will share further details and update instructions as soon as they are ready. We will keep you informed of any progress. Thank you for your understanding.
- resolved Apr 30, 2026, 04:16 PM UTC
We are pleased to inform you that our teams released new versions to resolve the security event that affected our Managed Kubernetes Service. Start time : 22/04/2026 08:15 UTC End time : 30/04/2026 15:30 UTC Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.
Notice April 30, 2026 [EU][Network] - API Network incident notification – WAW1, GRA1, DE1, UK1 and 14 more
Started Apr 30, 2026, 03:36 PM UTC· resolved Apr 30, 2026, 03:36 PM UTC
- resolved Apr 30, 2026, 03:36 PM UTC
We had an incident on our Public Cloud Network API offer in EU which has now been resolved. Here are some supplementary details : Start time : 30/04/2026 14:42 UTC End time : 30/04/2026 14:57 UTC Impacted Service(s) : The API for Public Cloud was temporarily unavailable. Customers Impact : Customers were temporarily unable to create, start, manage their Public Cloud instances. Root Cause : This incident was caused by a software issue. We thank you for your understanding and patience throughout this incident.
Major April 30, 2026 [FR][Data & Analytics] - Data Platform Incident Notification 6h 18m Data & Analytics || Data Platform
Started Apr 30, 2026, 01:06 PM UTC· resolved Apr 30, 2026, 07:24 PM UTC
- identified Apr 30, 2026, 01:06 PM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offering, which is causing temporary functionality issue in the FR region. Here are some supplementary details : Start time : 30/04/2026 08:18 UTC Impacted Service(s) : Builds of APP or API are temporarily unavailable. Customers Impact : Customers are temporarily unable to build API/APP. 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.
- resolved Apr 30, 2026, 07:24 PM UTC
We are pleased to inform you that the incident affecting our Data & Analytics offer has been resolved. Start time : 30/04/2026 08:18 UTC End time : 30/04/2026 19:14 UTC Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.
Notice April 28, 2026 [GRA11][Data & Analytics] - Data Platform incident notification – Data & Analytics || Data Platform
Started Apr 28, 2026, 03:09 PM UTC· resolved Apr 28, 2026, 03:09 PM UTC
- resolved Apr 28, 2026, 03:09 PM UTC
We had an incident on Data & Analytics offer in GRA11 which has now been resolved. Here are some supplementary details : Start time : 28/04/2026 02:00 UTC End time : 28/04/2026 08:00 UTC Impacted Service(s) : Data Platform tools were temporarily unavailable. Customers Impact : Customers were temporarily unable to use Data Platform tools. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We thank you for your understanding and patience throughout this incident.
Major April 24, 2026 [RBX10][Compute - Instance] - Cloud Compute Incident Notification 2h 27m RBX-A
Started Apr 24, 2026, 02:51 PM UTC· resolved Apr 24, 2026, 05:19 PM UTC
- investigating Apr 24, 2026, 02:51 PM UTC
We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary availability issue in the RBX10 region. Here are some supplementary details : Start time : 24/04/2026 14:40 UTC Impacted Service(s) : Some instances in the RBX10 region are unreachable. Customers Impact : Customers are temporarily unable to access instances located on the specified 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.
- identified Apr 24, 2026, 03:25 PM UTC
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 : 24/04/2026 14:40 UTC Impacted Service(s) : Some instances in the RBX10 region are unreachable. Customers Impact : Customers are temporarily unable to access instances located on 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.
- resolved Apr 24, 2026, 05:19 PM UTC
We are pleased to inform you that the incident affecting our Compute - Instance has been resolved. Start time : 24/04/2026 14:40 UTC End time : 24/04/2026 16:42 UTC Root Cause : A service disruption occurred due to an unexpected infrastructure failure. We apologize for any inconvenience caused and appreciate your understanding.
Major April 22, 2026 [BHS][Storage] - Storage Incident Notification 45m BHS, BHS1, BHS
Started Apr 22, 2026, 01:57 PM UTC· resolved Apr 22, 2026, 02:42 PM UTC
- investigating Apr 22, 2026, 01:57 PM UTC
We are currently investigating an incident affecting our Storage offering, which is causing temporary functionality issue in BHS1. Here are some supplementary details : Start time : 22/04/2026 13:22 UTC Impacted Service(s) : Customers may experience difficulties accessing their services. Customers Impact : Customers may experience 503 errors in BHS1 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.
- investigating Apr 22, 2026, 02:00 PM UTC
We are continuing to investigate this issue.
- identified Apr 22, 2026, 02:21 PM UTC
We have determined the origin of the issue affecting our Storage offer in BHS region. Here are some supplementary details : Start time : 22/04/2026 13:22 UTC Impacted Service(s) : Customers may experience difficulties accessing their services. Customers Impact : Customers may experience 503 errors in BHS region. 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.
- resolved Apr 22, 2026, 02:42 PM UTC
We are pleased to inform you that the incident affecting our Storage has been resolved. Start time : 22/04/2026 13:22 UTC End time : 22/04/2026 14: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.
Major April 21, 2026 [BHS1/BHS3/BHS5][Compute - Instance] - Cloud Compute Incident Notification 2h 1m BHS1, BHS3, BHS5
Started Apr 21, 2026, 12:04 PM UTC· resolved Apr 21, 2026, 02:05 PM UTC
- investigating Apr 21, 2026, 12:04 PM UTC
We are currently investigating an incident affecting our Cloud Compute offering, which is causing temporary functionality issue in BHS1 region. Here are some supplementary details : Start time : 21/04/2026 11:45 UTC Impacted Service(s) : Some instances in the BHS1 region are unreachable. Customers Impact : Customers are temporarily unable to access instances located on the specified rigion. 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.
- investigating Apr 21, 2026, 12:12 PM UTC
We are continuing to investigate this issue.
- identified Apr 21, 2026, 12:31 PM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Cloud Compute offer on the specific regions BHS1, BHS3 and BHS5. Here are some supplementary details : Start time : 21/04/2026 11:45 UTC Impacted Service(s) : Some instances in the BHS1, BHS3 and BHS5 regions are unreachable. Customers Impact : 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
- resolved Apr 21, 2026, 02:05 PM UTC
We are pleased to inform you that the incident affecting our Compute - Instance offer in BHS1, BHS3 and BHS5 regions has been resolved. Start time : 21/04/2026 11:45 UTC End time : 21/04/2026 13:59 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
Major April 21, 2026 [DE][Containers & Orchestration] - Managed Private Registry incident notification 1h 20m DE
Started Apr 21, 2026, 08:19 AM UTC· resolved Apr 21, 2026, 09:40 AM UTC
- investigating Apr 21, 2026, 08:19 AM UTC
We are currently experiencing an incident affecting our Containers & Orchestration - Managed Private Registry offering, which is causing temporary functionality issues in the DE region. Here is detail for this incident : Start time : 21/04/2026 07:51 UTC Impacted Service(s) : Some Registries are unreachable in the De 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.
- resolved Apr 21, 2026, 09:40 AM UTC
We are pleased to inform you that the incident affecting our Containers & Orchestration has been resolved. Start time : 21/04/2026 07:51 UTC End time : 21/04/2026 09:40 UTC Root Cause : This incident was caused by this maintenance : https://network.status-ovhcloud.com/incidents/tpf453cj6rzj We apologize for any inconvenience caused and appreciate your understanding.
Notice April 20, 2026 [DE][Storage] - Object Storage S3 Standard Incident Notification – DE
Started Apr 20, 2026, 12:48 PM UTC· resolved Apr 20, 2026, 12:48 PM UTC
- resolved Apr 20, 2026, 12:48 PM UTC
We had an incident on Object Storage S3 Standard offer in DE region which has now been resolved. Here are some supplementary details : Start time : 20/04/2026 09:55 UTC End time : 20/04/2026 11:06 UTC Impacted Service(s) : Object storage service in DE region was temporarily unavailable for some customers. Customers Impact : Some customers were getting 503 error when trying to connect their object storage located in DE 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.
Notice April 20, 2026 [GRA5/7/9/11][Compute - Instance] - Instances incident notification 28m GRA5, GRA7, GRA9, GRA11
Started Apr 20, 2026, 12:39 PM UTC· resolved Apr 20, 2026, 01:07 PM UTC
- investigating Apr 20, 2026, 12:39 PM UTC
We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary availability issue in the Graveline region. Here are some supplementary details : Start time : 20/04/2026 11:27 UTC Impacted Service(s) : Some instances in the Graveline region are unreachable. 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.
- resolved Apr 20, 2026, 01:07 PM UTC
We are pleased to inform you that the incident affecting our Compute - Instance in GRA has been resolved. Start time : 20/04/2026 12:27 UTC End time : 20/04/2026 12: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.
Notice April 19, 2026 [AP-SOUTH-MUM-1][Storage] - Block Storage incident notification 5h 50m AP-SOUTH-MUM-1
Started Apr 19, 2026, 06:19 AM UTC· resolved Apr 19, 2026, 12:09 PM UTC
- monitoring Apr 19, 2026, 06:19 AM UTC
Service has been fully restored since 19/04/2026 05:27 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 18/04/2026 17:09 UTC Impacted Service(s) : The block storage service was temporarily unavailable for some customers. Customers Impact : Customers were temporarily unable to access their block storage located in AP-SOUTH-MUM-1 region. Root Cause : This incident is caused by another incident : https://network.status-ovhcloud.com/incidents/lycx4vgc89jk We apologize for any inconvenience caused and appreciate your understanding.
- resolved Apr 19, 2026, 12:09 PM UTC
We are pleased to inform you that the incident affecting our Block Storage in AP-SOUTH-MUM-1 region has been resolved. Start time : 18/04/2026 17:09 UTC End time : 19/04/2026 05:27 UTC Root Cause : This incident was caused by another incident : https://network.status-ovhcloud.com/incidents/lycx4vgc89jk We apologize for any inconvenience caused and appreciate your understanding.
Major April 18, 2026 [AP-SOUTH-MUM][Public Cloud] - LocalZone / CEPH / Compute Instance / Managed Kubernetes Service incident notification 14h 4m AP-SOUTH-MUM-1, AP-SOUTH-MUM, AP-SOUTH-MUM-1, AP-SOUTH-MUM
Started Apr 18, 2026, 10:06 PM UTC· resolved Apr 19, 2026, 12:11 PM UTC
- identified Apr 18, 2026, 10:06 PM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Public Cloud offering on the specific AP-SOUTH-MUM. Here are some supplementary details : Start time : 18/04/2026 17:06 UTC Impacted Service(s) : Some customers are temporarily unable to access or use their compute instances in the AP-SOUTH-MUM-1 region, while actions such as restarting instances in the AP-SOUTH-MUM local zone are currently unavailable, and some Ceph volumes in the region are also impacted. Customers Impact : Some customers are temporarily unable to access or use their compute instances in the AP-SOUTH-MUM-1 region, are unable to perform actions such as restarting instances in the AP-SOUTH-MUM Local Zones, and are also unable to use their Ceph storage services. Root Cause : This incident is linked to : https://network.status-ovhcloud.com/incidents/lycx4vgc89jk 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.
- identified Apr 18, 2026, 11:00 PM UTC
We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : Some customers using a Managed Kubernetes Service may also be impacted. The management service for instances, volumes, and the load balancer is temporarily unavailable. Customers are currently unable to perform certain actions such as starting, stopping, or restarting resources. Provisioning of these services in this region is also temporarily unavailable. We recommend that customers do not perform any actions on their currently running services. Ongoing Actions : The incident has been identified and our teams and 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.
- monitoring Apr 19, 2026, 06:33 AM UTC
Service has been fully restored since 19/04/2026 05:49 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 18/04/2026 17:06 UTC Impacted Service(s) : Some customers were temporarily unable to access or use their compute instances in the AP-SOUTH-MUM-1 region, while actions such as restarting instances in the AP-SOUTH-MUM local zone were unavailable, and some Ceph volumes in the region were also impacted. Also, some customers using a Managed Kubernetes Service were also impacted. The management service for instances, volumes, and the load balancer were temporarily unavailable. Customers Impact : Some customers were temporarily unable to access or use their compute instances in the AP-SOUTH-MUM-1 region, are unable to perform actions such as restarting instances in the AP-SOUTH-MUM Local Zones, and are also unable to use their Ceph storage services. Also customers using Managed Kubernetes Service were unable to perform certain actions such as starting, stopping, or restarting resources. Provisioning of these services in this region was also unavailable. Root Cause : This incident is caused by another incident : https://network.status-ovhcloud.com/incidents/lycx4vgc89jk We apologize for any inconvenience caused and appreciate your understanding.
- resolved Apr 19, 2026, 12:11 PM UTC
We are pleased to inform you that the incident affecting our Public Cloud offer in AP-SOUTH-MUM region has been resolved. Start time : 18/04/2026 17:06 UTC End time : 19/04/2026 05:49 UTC Root Cause : This incident was caused by another incident : https://network.status-ovhcloud.com/incidents/lycx4vgc89jk We apologize for any inconvenience caused and appreciate your understanding.
Major April 18, 2026 [AP-SOUTH-MUM][Containers & Orchestration] - Managed Private Registry incident notification 16h 1m AP-SOUTH-MUM
Started Apr 18, 2026, 08:11 PM UTC· resolved Apr 19, 2026, 12:13 PM UTC
- identified Apr 18, 2026, 08:11 PM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Containers & Orchestration offer on the specific AP-SOUTH-MUM. Here are some supplementary details : Start time : 18/04/2026 17:06 UTC Impacted Service(s) : Service degraded for Registry Product on this DC. Customers Impact : Some of customer may encounter a degraded service on their registries, images push/pull are not available and some UI may be unavailable. 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.
- identified Apr 18, 2026, 09:21 PM UTC
We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : This incident is linked to : https://network.status-ovhcloud.com/incidents/lycx4vgc89jk 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.
- monitoring Apr 19, 2026, 06:08 AM UTC
Service has been fully restored since 19/04/2026 04:44 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 18/04/2026 17:06 UTC Impacted Service(s) : Service were degraded for Registry Product on this DC. Customers Impact : Some of customer encountered a degraded service on their registries, images push/pull and some UI were unavailable. Root Cause : This incident is caused by another incident : https://network.status-ovhcloud.com/incidents/lycx4vgc89jk We apologize for any inconvenience caused and appreciate your understanding.
- resolved Apr 19, 2026, 12:13 PM UTC
We are pleased to inform you that the incident affecting our Containers & Orchestration offer in AP-SOUTH-MUM region has been resolved. Start time : 18/04/2026 17:06 UTC End time : 19/04/2026 04:44 UTC Root Cause : This incident was caused by another incident : https://network.status-ovhcloud.com/incidents/lycx4vgc89jk We apologize for any inconvenience caused and appreciate your understanding.
Major April 18, 2026 [AP-SOUTH-MUM][PCI-Databases] - Cloud databases incident notification 16h 44m AP-SOUTH-MUM, AP-SOUTH-MUM, AP-SOUTH-MUM, AP-SOUTH-MUM and 6 more
Started Apr 18, 2026, 07:31 PM UTC· resolved Apr 19, 2026, 12:16 PM UTC
- investigating Apr 18, 2026, 07:31 PM UTC
We are currently investigating an incident affecting our PCI-Databases offering, which is causing temporary availability issue in the AP-SOUTH-MUM. Here are some supplementary details : Start time : 18/04/2026 17:06 UTC Impacted Service(s) : Cloud databases services is unavailable on AP-SOUTH-MUM Customers Impact : Customers may find it difficult to access their services. Orders and service management are also affected. 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.
- investigating Apr 18, 2026, 08:58 PM UTC
We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : Customers in the AP-SOUTH-MUM region are temporarily unable to place orders or use management features on their cloud database services. 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.
- identified Apr 18, 2026, 09:20 PM UTC
We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : This incident is linked to : https://network.status-ovhcloud.com/incidents/lycx4vgc89jk 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.
- monitoring Apr 19, 2026, 07:05 AM UTC
Service has been fully restored since 19/04/2026 04:47 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 18/04/2026 17:06 UTC Impacted Service(s) : Cloud databases services were unavailable in AP-SOUTH-MUM region. Customers Impact : Customers faced difficulties to access their services. Orders and service management were also affected. Root Cause : This incident is caused by another incident : https://network.status-ovhcloud.com/incidents/lycx4vgc89jk We apologize for any inconvenience caused and appreciate your understanding.
- resolved Apr 19, 2026, 12:16 PM UTC
We are pleased to inform you that the incident affecting our PCI-Databases offer in AP-SOUTH-MUM region has been resolved. Start time : 18/04/2026 17:06 UTC End time : 19/04/2026 04:47 UTC Root Cause : This incident was caused by another incident : https://network.status-ovhcloud.com/incidents/lycx4vgc89jk We apologize for any inconvenience caused and appreciate your understanding.
Major April 18, 2026 [AP-SOUTH-MUM][Storage] - Object Storage S3 incident notification 18h 13m AP-SOUTH-MUM-1
Started Apr 18, 2026, 06:01 PM UTC· resolved Apr 19, 2026, 12:14 PM UTC
- investigating Apr 18, 2026, 06:01 PM UTC
We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the AP-SOUTH-MUM region . Here are some supplementary details : Start time : 18/04/2026 17:06 UTC Impacted Service(s) : Issues to access on S3 objects on this region Customers Impact : Customers may experience issues downloading or uploading their objects due to 500/503 errors. 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.
- identified Apr 18, 2026, 09:20 PM UTC
We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : This incident is linked to : https://network.status-ovhcloud.com/incidents/lycx4vgc89jk 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.
- monitoring Apr 19, 2026, 05:14 AM UTC
Service has been fully restored since 19/04/2026 04:44 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 18/04/2026 17:06 UTC Impacted Service(s) : Issues to access on S3 objects on this region were present. Customers Impact : Customers may have experienced issues downloading or uploading their objects due to 500/503 errors. Root Cause : This incident is caused by another incident : https://network.status-ovhcloud.com/incidents/lycx4vgc89jk We apologize for any inconvenience caused and appreciate your understanding.
- resolved Apr 19, 2026, 12:14 PM UTC
We are pleased to inform you that the incident affecting our Storage offer in AP-SOUTH-MUM region has been resolved. Start time : 18/04/2026 17:06 UTC End time : 19/04/2026 04:44 UTC Root Cause : This incident was caused by another incident : https://network.status-ovhcloud.com/incidents/lycx4vgc89jk We apologize for any inconvenience caused and appreciate your understanding.
Major April 16, 2026 [EU-WEST-PAR][Storage] - Object Storage Incident Notification 2h 12m EU-WEST-PAR-A, EU-WEST-PAR-B, EU-WEST-PAR-C
Started Apr 16, 2026, 12:56 PM UTC· resolved Apr 16, 2026, 03:08 PM UTC
- investigating Apr 16, 2026, 12:56 PM UTC
We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the PAR region. Here are some supplementary details : Start time : 16/04/2026 11:35 UTC Impacted Service(s) : The object storage service is temporarily unavailable. Customers Impact : Customers in the EU-WEST-PAR region may temporarily encounter 503 errors on their object storage. 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.
- resolved Apr 16, 2026, 03:08 PM UTC
We are pleased to inform you that the incident affecting our Storage offering has been resolved. Start time : 16/04/2026 11:35 UTC End time : 16/04/2026 14:48 UTC Root Cause : A service disruption occurred due to an unexpected infrastructure failure. We apologize for any inconvenience caused and appreciate your understanding.
Major April 15, 2026 [DE/GRA][Databases] - Databases MongoDB incident notification 14h 4m DE
Started Apr 15, 2026, 08:11 AM UTC· resolved Apr 15, 2026, 10:15 PM UTC
- investigating Apr 15, 2026, 08:07 AM UTC
We are currently experiencing an event affecting our PCI-Databases offer. Start time : 15/04/2026 04:10 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.
- identified Apr 15, 2026, 08:11 AM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Databases offer on the specific DE/GRA regions. Here are some supplementary details : Start time : 15/04/2026 07:10 UTC Impacted Service(s) : Some MongoDB databases are temporarily unavailable. Customers Impact : Some customers are temporarily unable to use their MongoDB databases. Root Cause : This incident is related by : https://public-cloud.status-ovhcloud.com/incidents/2v5b4kyjttxj 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.
- identified Apr 15, 2026, 03:08 PM UTC
We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : Some services are available again 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.
- resolved Apr 15, 2026, 10:15 PM UTC
We are pleased to inform you that the incident affecting our PCI-Databases has been resolved. Start time : 15/04/2026 04:10 UTC End time : 15/04/2026 22:10 UTC Root Cause : This incident is related by : https://public-cloud.status-ovhcloud.com/incidents/2v5b4kyjttxj We apologize for any inconvenience caused and appreciate your understanding.
Major April 15, 2026 [DE1][Compute - Instance] - Instance incident notification 1h 15m DE1
Started Apr 15, 2026, 07:46 AM UTC· resolved Apr 15, 2026, 09:01 AM UTC
- investigating Apr 15, 2026, 07:46 AM UTC
We are currently experiencing an event affecting our Compute - Instance offer. 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.
- identified Apr 15, 2026, 07:56 AM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific DE1 region. Here are some supplementary details : Start time : 15/04/2026 07:10 UTC Impacted Service(s) : Some instances in the DE1 region region are temporarily unreachable. Customers Impact : Some customers are temporarily unable to access and use their instances in the DE1 region. 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.
- resolved Apr 15, 2026, 09:01 AM UTC
We are pleased to inform you that the incident affecting our Compute - Instance has been resolved. Start time : 15/04/2026 04:10 UTC End time : 15/04/2026 08:10 UTC Root Cause : A service disruption occurred due to an unexpected infrastructure failure. We apologize for any inconvenience caused and appreciate your understanding.
Notice April 15, 2026 [ERI1][Storage] - Object Storage Incident Notification – UK
Started Apr 15, 2026, 07:38 AM UTC· resolved Apr 15, 2026, 07:38 AM UTC
- resolved Apr 15, 2026, 07:38 AM UTC
We had an incident on Storage offer which has now been resolved. Here are some supplementary details : Start time : 15/04/2026 05:00 UTC End time : 15/04/2026 07:16 UTC Impacted Service(s) : The block storage service was temporarily unavailable for some customers. Customers Impact : Some customers were temporarily unable to access their storage located in ERI1. Root Cause : A service disruption occurred due to an unexpected infrastructure failure. We thank you for your understanding and patience throughout this incident.
Notice April 13, 2026 [GRA][Data & Analytics] - Data Platform incident notification – Data & Analytics || Data Platform
Started Apr 13, 2026, 10:45 AM UTC· resolved Apr 13, 2026, 10:45 AM UTC
- resolved Apr 13, 2026, 10:45 AM UTC
We had an incident on Data & Analytics offer which has now been resolved. Here are some supplementary details : Start time : 13/04/2026 10:30 UTC End time : 13/04/2026 11:00 UTC Impacted Service(s) : Data Platform projects were temporarily unavailable. Customers Impact : For these regions, you might have faced issues with network connectivity or managing your private networks. Root Cause : This incident was caused by a software issue. We thank you for your understanding and patience throughout this incident.