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 590 (51%) |
Incidents, newest first
Major July 9, 2026 [GRA][Network] - Public network incident notification 3d 22h GRA1, GRA3, GRA5, GRA7 and 2 more
Started Jul 09, 2026, 01:45 PM UTC· resolved Jul 13, 2026, 12:05 PM UTC
- identified Jul 09, 2026, 01:45 PM UTC
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.
- resolved Jul 13, 2026, 12:05 PM UTC
We are pleased to inform you that the incident affecting our Network offering has been resolved. Start time : 09/07/2026 13:40 UTC End time : 13/07/2026 11:10 UTC Root Cause : This incident is caused by another incident : https://network.status-ovhcloud.com/incidents/cfjg549ghh2y We apologize for any inconvenience caused and appreciate your understanding.
Notice July 9, 2026 [SBG][Storage] - S3 Object Storage incident notification – SBG
Started Jul 09, 2026, 12:24 PM UTC· resolved Jul 09, 2026, 12:24 PM UTC
- resolved Jul 09, 2026, 12:24 PM UTC
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.
Major July 7, 2026 [GRA][AI & Machine Learning] - AI payload incident notification – AI & Machine Learning || AI Endpoint
Started Jul 07, 2026, 03:10 PM UTC· resolved Jul 07, 2026, 03:10 PM UTC
- monitoring Jul 07, 2026, 12:31 PM UTC
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.
- resolved Jul 07, 2026, 03:10 PM UTC
We are pleased to inform you that the incident affecting our 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.
Major July 7, 2026 [GRA1/3/4/5/7/9/11][Compute - Instance] - Some instances incident notification 23h 40m GRA1, GRA3, GRA5, GRA7 and 3 more
Started Jul 07, 2026, 09:50 AM UTC· resolved Jul 08, 2026, 09:31 AM UTC
- monitoring Jul 07, 2026, 09:50 AM UTC
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 : 07/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.
- monitoring Jul 07, 2026, 02:17 PM UTC
Please find the details of this incident below : Start time : 06/07/2026 20:08 UTC Impacted Service(s) : Public network was temporarily unavailable. Customers Impact : Customers were temporarily unable to access 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.
- monitoring Jul 07, 2026, 06:33 PM UTC
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.
- monitoring Jul 07, 2026, 09:53 PM UTC
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.
- resolved Jul 08, 2026, 09:31 AM UTC
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.
Major July 6, 2026 [GRA5/7/9/11][Containers & Orchestration] - Managed Kubernetes Service Incident Notification 1d 10h GRA5, GRA7, GRA9, GRA11
Started Jul 06, 2026, 11:30 PM UTC· resolved Jul 08, 2026, 09:34 AM UTC
- investigating Jul 06, 2026, 11:30 PM UTC
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.
- monitoring Jul 07, 2026, 01:43 AM UTC
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.
- resolved Jul 08, 2026, 09:34 AM UTC
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.
Major July 6, 2026 [GRA][Containers & Orchestration] - Managed Private Registry Incident Notification 1d 11h GRA
Started Jul 06, 2026, 10:24 PM UTC· resolved Jul 08, 2026, 09:34 AM UTC
- investigating Jul 06, 2026, 10:24 PM UTC
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.
- monitoring Jul 07, 2026, 01:39 AM UTC
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.
- resolved Jul 08, 2026, 09:34 AM UTC
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.
Minor July 6, 2026 [GRA][Object Storage] - Object Storage Swift Incident Notification 1d 22h GRA
Started Jul 06, 2026, 02:22 PM UTC· resolved Jul 08, 2026, 12:43 PM UTC
- investigating Jul 06, 2026, 02:22 PM UTC
We are currently investigating an incident affecting our Storage and Backups offering, which is causing temporary functionality issue in GRA2 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.
- monitoring Jul 06, 2026, 03:31 PM UTC
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.
- resolved Jul 08, 2026, 12:43 PM UTC
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.
Major July 3, 2026 [GRA1/3/9][Compute - Instance] - Some Instances Incident Notification 5h 18m GRA1, GRA3, GRA9
Started Jul 03, 2026, 01:39 PM UTC· resolved Jul 03, 2026, 06:57 PM UTC
- identified Jul 03, 2026, 01:39 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 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.
- resolved Jul 03, 2026, 06:57 PM UTC
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.
Notice July 1, 2026 [GRA][Containers & Orchestration] - Managed Private Registry incident notification 1m GRA
Started Jul 01, 2026, 07:14 PM UTC· resolved Jul 01, 2026, 07:15 PM UTC
- identified Jul 01, 2026, 07:14 PM UTC
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.
- resolved Jul 01, 2026, 07:15 PM UTC
We are pleased to inform you that the incident affecting our Containers & Orchestration offering has been resolved. Start time : 01/07/2026 17:32 UTC End time : 01/07/2026 18:54 UTC Root Cause : https://web-cloud.status-ovhcloud.com/incidents/0j01r7j5vsky We apologize for any inconvenience caused and appreciate your understanding.
Major July 1, 2026 [DE1][Containers & Orchestration] - Managed Kubernetes Service incident notification 22m DE, DE1
Started Jul 01, 2026, 06:32 PM UTC· resolved Jul 01, 2026, 06:55 PM UTC
- identified Jul 01, 2026, 06:32 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 DE1 region. Here are some supplementary details : Start time : 01/07/2026 17:32 UTC Impacted Service(s) : Some registries are unavailable Customers Impact : Registries are unavailable (Harbor UI, docker pull/push) 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.
- identified Jul 01, 2026, 06:50 PM UTC
We are continuing to work on a fix for this issue.
- resolved Jul 01, 2026, 06:55 PM UTC
We are pleased to inform you that the incident affecting our Containers & Orchestration offering has been resolved. Start time : 01/07/2026 17:32 UTC End time : 01/07/2026 18:54 UTC Root Cause : https://public-cloud.status-ovhcloud.com/incidents/x3cj8gldm5yx We apologize for any inconvenience caused and appreciate your understanding.
Major July 1, 2026 [GRA7][Compute - Instance] - Some instances incident notification 1h 27m GRA4
Started Jul 01, 2026, 05:54 PM UTC· resolved Jul 01, 2026, 07:21 PM UTC
- identified Jul 01, 2026, 05:54 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 GRA Region. Here are some supplementary details : Start time : 01/07/2026 17:32 UTC Impacted Service(s) : Some instances in the GRA4 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.
- resolved Jul 01, 2026, 07:21 PM UTC
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.
Major June 29, 2026 [BHS1][Storage] - Block Storage incident notification 4h 3m BHS1, BHS3, BHS5
Started Jun 29, 2026, 02:43 PM UTC· resolved Jun 29, 2026, 06:47 PM UTC
- identified Jun 29, 2026, 02:43 PM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Block Storage offer on the specific regions BHS1, BHS3 and BHS5. 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, BHS3 and BHS5 region. Customers Impact : Some customers are unable to access and use their block storage loacted in 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.
- identified Jun 29, 2026, 02:59 PM UTC
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.
- identified Jun 29, 2026, 03:46 PM UTC
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.
- identified Jun 29, 2026, 06:10 PM UTC
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 is currently unavailable for some customers in BHS1 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 Jun 29, 2026, 06:47 PM UTC
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.
Major June 28, 2026 [GRA1/11][Compute - Instance] - Some instances incident notification 1h 11m GRA1, GRA11
Started Jun 28, 2026, 07:10 PM UTC· resolved Jun 28, 2026, 08:21 PM UTC
- identified Jun 28, 2026, 07:10 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 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.
- resolved Jun 28, 2026, 08:21 PM UTC
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.
Major June 28, 2026 [BHS1/3/5][Compute - Instance] - Some instances incident notification 38m BHS1, BHS3, BHS5
Started Jun 28, 2026, 05:15 PM UTC· resolved Jun 28, 2026, 05:53 PM UTC
- investigating Jun 28, 2026, 05:15 PM UTC
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.
- resolved Jun 28, 2026, 05:53 PM UTC
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.
Notice June 28, 2026 [DE1][Compute - Instance] - Some instances incident notification – DE1
Started Jun 28, 2026, 01:08 PM UTC· resolved Jun 28, 2026, 01:08 PM UTC
- resolved Jun 28, 2026, 01:08 PM UTC
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.
Major June 26, 2026 [GRA9][File storage] - File storage incident notification 8h 43m GRA9
Started Jun 26, 2026, 10:21 AM UTC· resolved Jun 26, 2026, 07:05 PM UTC
- identified Jun 26, 2026, 10:21 AM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our File storage offer on the specific GRA9 region. Here are some supplementary details : Start time : 26/06/2026 09:07 UTC Impacted Service(s) : Some File storage are temporarily unavailable. Customers Impact :Some customers are temporarily unable to access their File storage. 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 Jun 26, 2026, 07:05 PM UTC
We are pleased to inform you that the incident affecting our File storage offering has been resolved. Start time : 26/06/2026 09:07 UTC End time : 26/06/2026 19:00 UTC Root Cause : A service disruption occurred due to an unexpected infrastructure failure. We apologize for any inconvenience caused and appreciate your understanding.
Major June 25, 2026 [UK1][Containers & Orchestration] - Managed Kubernetes Service Incident Notification 11h 53m UK1
Started Jun 25, 2026, 07:25 PM UTC· resolved Jun 26, 2026, 07:18 AM UTC
- identified Jun 25, 2026, 07:25 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 UK1 regions. Here are some supplementary details : Start time : 25/06/2026 18:49 UTC Impacted Service(s) : Some instances in the UK1 region are unreachable. Customers Impact : Management and creation of new Managed Kubernetes Service clusters is temporarily unavailable. 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.
- resolved Jun 26, 2026, 07:18 AM UTC
We are pleased to inform you that the incident affecting our Containers & Orchestration offering has been resolved. Start time : 25/06/2026 18:49 UTC End time : 26/06/2026 06: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.
Major June 25, 2026 [GRA1][Compute - Instance] - Some Instances Incident Notification 33m GRA1
Started Jun 25, 2026, 06:15 PM UTC· resolved Jun 25, 2026, 06:48 PM UTC
- identified Jun 25, 2026, 06:15 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 GRA1 region. Here are some supplementary details : Start time : 25/06/2026 18:05 UTC Impacted Service(s) : Some instances in the GRA1 region are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on 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.
- resolved Jun 25, 2026, 06:48 PM UTC
We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 25/06/2026 18:05 UTC End time : 25/06/2026 18:30 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 June 24, 2026 [GRA][Compute - Instance] - Some Instances Incident Notification 19m GRA1
Started Jun 24, 2026, 09:03 PM UTC· resolved Jun 24, 2026, 09:23 PM UTC
- identified Jun 24, 2026, 09:03 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 GRA1 region. Here are some supplementary details : Start time : 24/06/2026 20:52 UTC Impacted Service(s) : Some instances in the GRA1 region are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on 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.
- resolved Jun 24, 2026, 09:23 PM UTC
We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 24/06/2026 20:52 UTC End time : 24/06/2026 21:22 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 June 24, 2026 [GRA7/GRA9/GRA11][Compute - Instance] - Compute Instance Incident Notification 3h 4m GRA7, GRA9, GRA11
Started Jun 24, 2026, 06:25 AM UTC· resolved Jun 24, 2026, 09:30 AM UTC
- identified Jun 24, 2026, 06:25 AM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer in GRA regions. Here are some supplementary details : Start time : 24/06/2026 06:01 UTC Impacted Service(s) : Some instances in the GRA regions are unreachable. Customers Impact : Customers are temporarily unable to access some 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. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Jun 24, 2026, 09:30 AM UTC
We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 24/06/2026 06:01 UTC End time : 24/06/2026 06:20 UTC Root Cause : A service disruption occurred due to an unexpected infrastructure failure. We apologize for any inconvenience caused and appreciate your understanding.
Major June 23, 2026 [GRA3][Compute - Instance] - Some Instances Incident Notification 7h 50m GRA3
Started Jun 23, 2026, 04:45 PM UTC· resolved Jun 24, 2026, 12:35 AM UTC
- identified Jun 23, 2026, 04:45 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 GRA3 region. Here are some supplementary details : Start time : 23/06/2026 13:00 UTC Impacted Service(s) : Some instances in the GRA3 region are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on 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.
- resolved Jun 24, 2026, 12:35 AM UTC
We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 23/06/2026 13:00 UTC End time : 24/06/2026 00: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.
Major June 23, 2026 [GLOBAL][AI & Machine Learning] - AI Endpoint Qwen2.5-VL-72B-Instruct model Incident Notification 44m AI & Machine Learning || AI Endpoint
Started Jun 23, 2026, 02:18 PM UTC· resolved Jun 23, 2026, 03:03 PM UTC
- investigating Jun 23, 2026, 02:18 PM UTC
We are currently investigating an incident affecting our AI & Machine Learning offering, which is causing temporary availability issue in GLOBAL region. Here are some supplementary details : Start time : 23/06/2026 10:00 UTC Impacted Service(s) : The Qwen2.5-VL-72B-Instruct model is currently unavailable on AI Endpoints. Customers Impact : Customers calling the Qwen2.5-VL-72B-Instruct model endpoint are experiencing HTTP 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.
- resolved Jun 23, 2026, 03:03 PM UTC
We are pleased to inform you that the incident affecting our AI & Machine Learning offering has been resolved. Start time : 23/06/2026 10:00 UTC End time : 23/06/2026 13:35 UTC Root Cause : A service disruption occurred due to an unexpected underlying software malfunction. We apologize for any inconvenience caused and appreciate your understanding.
Minor June 22, 2026 [UK1][Public Cloud] - API Incident Notification 3d 16h UK, UK, UK1, UK1 and 1 more
Started Jun 22, 2026, 02:45 PM UTC· resolved Jun 26, 2026, 06:54 AM UTC
- investigating Jun 22, 2026, 02:45 PM UTC
We are currently investigating an incident affecting our offering, which is causing temporary issue in the UK1 region. Here are some supplementary details : Start time : 22/06/2026 14:25 UTC Impacted Service(s) : The API in the UK1 region is temporarily degraded. Customers Impact : For these regions, you might have issues to create, start, or manage your instances and create or attach new volumes. 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 Jun 22, 2026, 03:09 PM UTC
We are pleased to inform you that the incident affecting our Public Cloud offering has been resolved. Start time : 22/06/2026 14:25 UTC End time : 22/06/2026 15:04 UTC Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.
- investigating Jun 26, 2026, 06:52 AM UTC
We are pleased to inform you that the incident affecting our Public Cloud offering has been resolved. Start time : 22/06/2026 14:25 UTC End time : 22/06/2026 15:04 UTC Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Jun 26, 2026, 06:54 AM UTC
This incident has been resolved.
Minor June 22, 2026 [GLOBAL][AI & Machine Learning] - AI Endpoint incident notification 2h 45m AI & Machine Learning || AI Endpoint
Started Jun 22, 2026, 12:18 PM UTC· resolved Jun 22, 2026, 03:04 PM UTC
- investigating Jun 22, 2026, 12:18 PM UTC
We are currently investigating an incident affecting our AI & Machine Learning offering, which is causing temporary availability issue on AI Endpoint . Here are some supplementary details : Start time : 22/06/2026 08:30 UTC Impacted Service(s) : AI Endpoints may have some performance issue. Customers Impact : Customers may have error 500 message on AI Endpoints. 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 Jun 22, 2026, 03:04 PM UTC
We are pleased to inform you that the incident affecting our AI & Machine Learning offering has been resolved. Start time : 22/06/2026 08:30 UTC End time : 22/06/2026 14:15 UTC Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.
Notice June 21, 2026 [GRA5/7/9/11][Compute - Instance] - Some Instances Incident Notification – GRA5, GRA7, GRA9, GRA11
Started Jun 21, 2026, 09:08 AM UTC· resolved Jun 21, 2026, 09:08 AM UTC
- resolved Jun 21, 2026, 09:08 AM UTC
We had an incident on Compute - Instance offer in the GRA5/7/9/11 regions which has now been resolved. Here are some supplementary details : Start time : 21/06/2026 08:38 UTC End time : 21/06/2026 08:47 UTC Impacted Service(s) : Some instances in the GRA5/7/9/11 regions were temporarily unreachable. Customers Impact : Customers were temporarily unable to access and use their instances in the GRA5/7/9/11 regions. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We thank you for your understanding and patience throughout this incident.