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 June 21, 2026 [GRA1/3/11][Compute - Instance] - Some Instances Incident Notification 7m GRA1
Started Jun 21, 2026, 07:39 AM UTC· resolved Jun 21, 2026, 07:46 AM UTC
- investigating Jun 21, 2026, 07:39 AM UTC
We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary availability issue in GRA1 region Here are some supplementary details : Start time : 21/06/2026 07:28 UTC Impacted Service(s) : Some instances in the GRA1 region are unreachable. Customers Impact : Customers are temporarily unable to access some instances located on the 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.
- resolved Jun 21, 2026, 07:46 AM UTC
We are pleased to inform you that the incident affecting our Compute - Instance offering in GRA1 has been resolved. Start time : 21/06/2026 07:28 UTC End time : 21/06/2026 07:39 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 June 17, 2026 [EU-WEST-PAR][Public Cloud] - Network connectivity issues notification 1h 21m EU-WEST-PAR-A, EU-WEST-PAR-B, EU-WEST-PAR-A, EU-WEST-PAR-C and 2 more
Started Jun 17, 2026, 01:23 PM UTC· resolved Jun 17, 2026, 02:44 PM UTC
- identified Jun 17, 2026, 01:23 PM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Public Cloud offer on the specific EU-WEST-PAR region. Here are some supplementary details : Start time : 09/06/2026 07:00 UTC Impacted Service(s) : Nodes located in EU-WEST-PAR region may experience packets drop while communicating with their controlplanes and the Internet. Customers Impact : Customer are temporarily facing connectivity issues with their nodes located in the specified region. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Jun 17, 2026, 02:44 PM UTC
We are pleased to inform you that the incident affecting our Public Cloud offering has been resolved. Start time : 15/06/2026 23:00 UTC End time : 17/06/2026 14: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.
Notice June 17, 2026 [GRA7][Containers & Orchestration] - Managed Kubernetes Service incident notification – GRA7
Started Jun 17, 2026, 08:21 AM UTC· resolved Jun 17, 2026, 08:21 AM UTC
- resolved Jun 17, 2026, 08:21 AM UTC
We had an incident on Containers & Orchestration offer in GRA7 region which has now been resolved. Here are some supplementary details : Start time : 17/06/2026 07:40 UTC End time : 17/06/2026 08:10 UTC Impacted Service(s) : Managed Kubernetes Service's API was temporarily unavailable. Customers Impact : Customers were temporarily unable to use the API of Managed Kubernetes Service. Root Cause : This incident was caused by a software issue. We thank you for your understanding and patience throughout this incident.
Major June 11, 2026 [GRA][Data & Analytics] - Data Platform Incident Notification 3h 43m Data & Analytics || Data Platform
Started Jun 11, 2026, 12:32 PM UTC· resolved Jun 11, 2026, 04:16 PM UTC
- investigating Jun 11, 2026, 12:32 PM UTC
We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary availability issue in GLOBAL regions. Here are some supplementary details : Start time : 11/06/2026 09:00 UTC Impacted Service(s) : Some jobs cannot be executed on the Data Platform. Customers Impact : Some customers cannot run some jobs, causing delays in data processing and dependent workflows. 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 11, 2026, 04:16 PM UTC
We are pleased to inform you that the incident affecting our Data & Analytics offering has been resolved. Start time : 10/06/2026 12:00 UTC End time : 11/06/2026 13:00 UTC Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.
Minor June 10, 2026 [SBG5][Storage] - Block storage incident notification 7h 1m SBG5
Started Jun 10, 2026, 01:25 AM UTC· resolved Jun 10, 2026, 08:26 AM UTC
- identified Jun 10, 2026, 01:25 AM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Block storage offer in SBG5. Please find the details of this incident below : Start time : 10/06/2026 00:50 UTC Impacted Service(s) : Block storage service is experiencing degraded performance. Customers Impact : Customers may experience increased latency, slower response times, or intermittent errors when accessing or managing data stored on the affected Block Storage. 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.
- monitoring Jun 10, 2026, 01:30 AM UTC
Service has been fully restored since 10/06/2026 01:26 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 10/06/2026 00:50 UTC Impacted Service(s) : Block Storage service experienced degraded performance. Customers Impact : Customers may have experienced increased latency, slower response times, or intermittent errors when accessing or managing data stored on the affected Block Storage. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Jun 10, 2026, 08:26 AM UTC
We are pleased to inform you that the incident affecting our Block storage offering has been resolved. Start time : 10/06/2026 00:50 UTC End time : 10/06/2026 07:10 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 9, 2026 [GRA1/3/9][Compute - Instance] - Some instances incident notification 11h 14m GRA1, GRA3, GRA9
Started Jun 09, 2026, 01:50 PM UTC· resolved Jun 10, 2026, 01:05 AM UTC
- identified Jun 09, 2026, 01:50 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 : 09/06/2026 13:35 UTC Impacted Service(s) : All or some instances in the GRA1/3/9 regions are unreachable. Customers Impact : Some customers are temporarily unable to access and use their Public Cloud instances located 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 09, 2026, 04:51 PM UTC
We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : Some instances are no longer impacted by 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.
- identified Jun 09, 2026, 10:00 PM UTC
Ongoing Actions : 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 10, 2026, 01:05 AM UTC
We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 09/06/2026 13:35 UTC End time : 10/06/2026 00: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 6, 2026 [GRA5/GRA7/GRA11][Compute - Instance] - Some instances incident notification 2h 32m GRA5, GRA7, GRA11
Started Jun 06, 2026, 04:28 PM UTC· resolved Jun 06, 2026, 07:00 PM UTC
- identified Jun 06, 2026, 04:28 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 : 06/06/2026 15:06 UTC Impacted Service(s) : Some instances in the GRA5 - GRA7 - GRA11 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 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 06, 2026, 07:00 PM UTC
We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 06/06/2026 15:06 UTC End time : 06/06/2026 18:55 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 6, 2026 [DE][Containers & Orchestration] - Managed Private Registry incident notification 20h 42m DE
Started Jun 06, 2026, 11:23 AM UTC· resolved Jun 07, 2026, 08:05 AM UTC
- investigating Jun 06, 2026, 11:23 AM UTC
We are currently investigating an incident affecting our Managed Private Registry offering, which is causing temporary availability issue in DE region. Please find the details of this incident below : Start time : 06/06/2026 05:35 UTC Impacted Service(s) : Some Registries may be unavailable. Customers Impact : Customers may experience issues performing registry-related operations. 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 Jun 06, 2026, 04:23 PM UTC
We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : Some Registries in the LIM region are operational again. However, the performance of the some Registries may be temporarily degraded. 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 07, 2026, 08:05 AM UTC
We are pleased to inform you that the incident affecting our Managed Private Registry offering has been resolved. Start time : 06/06/2026 05:35 UTC End time : 07/06/2026 08:00 UTC Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.
Major June 5, 2026 [GRA1/3/7/9][Compute - Instance] - Some Instances Incident Notification 32m GRA1, GRA3, GRA7, GRA9
Started Jun 05, 2026, 08:28 PM UTC· resolved Jun 05, 2026, 09:00 PM UTC
- investigating Jun 05, 2026, 08:28 PM UTC
We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary availability issue in GRA1/3/7/9 regions. Here are some supplementary details : Start time : 05/06/2026 20:14 UTC Impacted Service(s) : Some instances in the GRA1/3/7/9 regions are unreachable. Customers Impact : Some 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.
- resolved Jun 05, 2026, 09:00 PM UTC
We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 05/06/2026 20:14 UTC End time : 05/06/2026 20:55 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 June 4, 2026 [Global][PCI-Databases] - MongoDB incident notification 20h 57m BHS, DE, GRA, EU-WEST-PAR and 9 more
Started Jun 04, 2026, 09:28 AM UTC· resolved Jun 05, 2026, 06:26 AM UTC
- investigating Jun 04, 2026, 09:28 AM UTC
We are currently investigating an incident affecting our PCI-Databases offering, which is causing temporary degraded issue in the Global region. Here are some supplementary details : Start time : 03/06/2026 12:00 UTC Impacted Service(s) : Some MongoDB databases that initially run with 3 nodes may temporarily run with 2 nodes. Customers Impact : Customers with 3 node MongoDB services may temporarily operate with only 2 nodes. No latency or data loss is observed. 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 Jun 04, 2026, 09:33 AM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our PCI-Databases offer on the specific global region. Here are some supplementary details : Start time : 03/06/2026 12:00 UTC Impacted Service(s) : Some MongoDB databases that initially run with 3 nodes may temporarily run with 2 nodes. Customers Impact : Customers with 3 node MongoDB services may temporarily operate with only 2 nodes. No latency or data loss is observed. 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.
- monitoring Jun 04, 2026, 12:07 PM UTC
Service has been fully restored since 04/06/2026 12:00 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 03/06/2026 12:00 UTC Impacted Service(s) : Some MongoDB databases that initially ran with 3 nodes temporarily ran with 2 nodes Customers Impact : Customers with 3-node MongoDB services temporarily operated with only 2 nodes. No latency or data loss was observed Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Jun 05, 2026, 06:26 AM UTC
We are pleased to inform you that the incident affecting our PCI-Databases offering has been resolved. Start time : 03/06/2026 12:00 UTC End time : 04/06/2026 12:00 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 4, 2026 [GLOBAL][AI & Machine Learning] - Qwen3.5-397B-A17B incident notification 4h 36m AI & Machine Learning || AI Endpoint
Started Jun 04, 2026, 07:46 AM UTC· resolved Jun 04, 2026, 12:22 PM UTC
- identified Jun 04, 2026, 07:46 AM UTC
We are currently investigating an incident affecting our AI & Machine Learning offering, which is causing temporary issue for the model Qwen3.5-397B-A17B. Here are some supplementary details : Start time : 03/06/2026 22:30 UTC Impacted Service(s) : The AI endpoint Qwen3.5-397B-A17B is not reachable. Customers Impact : Customers are temporarily unable to access their endpoint model. 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 04, 2026, 12:22 PM UTC
We are pleased to inform you that the incident affecting our AI & Machine Learning offering has been resolved. Start time : 03/06/2026 22:30 UTC End time : 04/06/2026 10:10 UTC Root Cause : A service disruption occurred due to an unexpected infrastructure failure. We apologize for any inconvenience caused and appreciate your understanding.
Minor June 3, 2026 PCI - EU-WEST-PAR - host1878809 1h 2m
Started Jun 03, 2026, 12:59 AM UTC· resolved Jun 03, 2026, 02:01 AM UTC
- investigating Jun 03, 2026, 12:59 AM UTC
Estimated time to recovery : 4 hour(s) Affected hosts host1878809 Affected instances The list of instances listed below are currently unavailable, due to hardware fault on the hypervisor(s) previously mentioned. We apologize for any inconvenience caused while we resolve this issue. 6366b462-028e-4155-bea5-060db8ae0be6
- resolved Jun 03, 2026, 02:01 AM UTC
This incident has been resolved.
Notice June 2, 2026 [GRA][Identity, Security & Operations] - Logs Data Platform incident notification – GRA
Started Jun 02, 2026, 08:18 AM UTC· resolved Jun 02, 2026, 08:18 AM UTC
- resolved Jun 02, 2026, 08:18 AM UTC
We had an incident on Logs Data Platform offer in GRA which has now been resolved. Here are some supplementary details : Start time : 02/06/2026 07:31 UTC End time : 02/06/2026 07:50 UTC Impacted Service(s) : The Logs Data Platform service were temporarily unavailable. Customers Impact : Customers were temporarily unable to use Logs Data Platform service. 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 May 30, 2026 [BHS7][Compute - Instance] - Compute Instance Incident Notification 4h 18m BHS1, BHS3, BHS5, BHS7
Started May 30, 2026, 07:47 AM UTC· resolved May 30, 2026, 12:06 PM UTC
- investigating May 30, 2026, 07:47 AM UTC
We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary availability issue in BHS regions. Here are some supplementary details : Start time : 30/05/2026 07:32 UTC Impacted Service(s) : Some instances in the BHS regions are unreachable. Customers Impact : Some 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 May 30, 2026, 08:04 AM UTC
We have determined the origin of the issue affecting our Compute - Instance offer in the specific BHS7 region. Here are some supplementary details : Start time : 30/05/2026 07:32 UTC Impacted Service(s) : Some instances in the BHS7 region are unreachable. Customers Impact : Some customers are temporarily unable to access instances located in the specified 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 May 30, 2026, 12:06 PM UTC
We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 30/05/2026 07:32 UTC End time : 30/05/2026 11:30 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 27, 2026 [BHS1/3][Compute - Instance] - Some instances incident notification – BHS1, BHS3
Started May 27, 2026, 05:57 PM UTC· resolved May 27, 2026, 05:57 PM UTC
- resolved May 27, 2026, 05:57 PM UTC
We had an incident on our Compute - Instance offer in BHS1 and BHS3 regions which has now been resolved. Here are some supplementary details : Start time : 27/05/2026 15:46 UTC End time : 27/05/2026 17:29 UTC Impacted Service(s) : Some instances in BHS1 and BHS3 regions were unreachable. Customers Impact : Some customers were temporarily unable to access and use their instances in the specified 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.
Major May 27, 2026 [AP-SOUTH-MUM/EU-SOUTH-MIL/EU-WEST-PAR/RBX][Containers & Orchestration] - Managed Kubernetes Service Incident Notification 22h 58m AP-SOUTH-MUM, EU-SOUTH-MIL, EU-WEST-PAR, RBX
Started May 27, 2026, 03:27 PM UTC· resolved May 28, 2026, 02:25 PM UTC
- investigating May 27, 2026, 03:27 PM UTC
We are currently experiencing an event affecting our Managed Kubernetes Service in AP-SOUTH-MUM / EU-SOUTH-MIL / EU-WEST-PAR / RBX regions. Start time : 27/05/2026 14:00 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 27, 2026, 04:02 PM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Containers & Orchestration - Managed Kubernetes Service in AP-SOUTH-MUM / EU-SOUTH-MIL / EU-WEST-PAR / RBX regions. Here are some supplementary details : Start time : 27/05/2026 14:00 UTC Impacted Service(s) : MKS cluster delivery and deletion is currently unavailable. Customers Impact : Customers are currently unable to create new MKS clusters and to add or edit nodepools. Root Cause : A service disruption is currently occurring due to an unexpected 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 May 28, 2026, 02:25 PM UTC
We are pleased to inform you that the incident affecting our Containers & Orchestration - Managed Kubernetes Service offering in AP-SOUTH-MUM / EU-SOUTH-MIL / EU-WEST-PAR / RBX regions has been resolved. Start time : 27/05/2026 14:00 UTC End time : 28/05/2026 13:56 UTC Root Cause : A service disruption is currently occurring due to an unexpected infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
Minor May 25, 2026 [GRA1][Storage] - Some CEPH volumes incident notification 8h 36m GRA1
Started May 25, 2026, 09:30 AM UTC· resolved May 25, 2026, 06:06 PM UTC
- investigating May 25, 2026, 09:30 AM UTC
We are currently investigating an incident affecting our Storage offering, which is causing temporary latency issue in the GRA1 region. Here are some supplementary details : Start time : 25/05/2026 07:30 UTC Impacted Service(s) : Some Ceph volumes may temporarily experience degraded performance. Customers Impact : Some customers may temporarily experience degraded performance on their Ceph 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.
- monitoring May 25, 2026, 02:02 PM UTC
Service has been fully restored since 25/05/2026 12:50 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 25/05/2026 07:30 UTC Impacted Service(s) : Some Ceph volumes may temporarily experience degraded performance. Customers Impact : Some customers may temporarily experience degraded performance on their Ceph volumes. We apologize for any inconvenience caused and appreciate your understanding.
- resolved May 25, 2026, 06:06 PM UTC
We are pleased to inform you that the incident affecting our Storage offering has been resolved. Start time : 25/05/2026 07:30 UTC End time : 25/05/2026 12:50 UTC Root Cause : This incident was caused by a network equipment issue. We apologize for any inconvenience caused and appreciate your understanding.
Minor May 22, 2026 [GRA/RBX/DE][Storage and Backups] - Object Storage Incident Notification 23d 22h GRA, DE, RBX
Started May 22, 2026, 03:04 PM UTC· resolved Jun 15, 2026, 01:48 PM UTC
- investigating May 22, 2026, 03:04 PM UTC
We are currently investigating an incident affecting our Storage and Backups offering, which is causing temporary functionality issue in GRA/RBX/DE regions Here are some supplementary details : Start time : 13/05/2026 00:00 UTC Impacted Service(s) : Delay in lifecycle rules execution for regions GRA, RBX and DE Customers Impact : Some customers might face delay in lifecycle rules execution in 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.
- investigating May 25, 2026, 08:58 AM UTC
We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : The incident is still under investigation by our technical teams, who are working to determine its cause and implement a fix. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- identified Jun 11, 2026, 10:05 AM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Storage and Backups offering in GRA/RBX/DE regions. Here are some supplementary details : Start time : 13/05/2026 00:00 UTC Impacted Service(s) : Delay in lifecycle rules execution for regions GRA, RBX and DE. Customers Impact : Some customers might face delay in lifecycle rules execution in specified regions. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. Ongoing Actions : Processing has been improved and most of the backlog has been cleared. Some workloads with a very high number of pending events may still experience delays while we continue optimizing processing. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Jun 15, 2026, 01:48 PM UTC
We are pleased to inform you that the incident affecting our Storage and Backups offering has been resolved. Start time : 13/05/2026 00:00 UTC End time : 15/06/2026 12:00 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 21, 2026 [BHS5][Compute - Instance] - Instances incident notification 14m BHS5
Started May 21, 2026, 11:07 PM UTC· resolved May 21, 2026, 11:22 PM UTC
- identified May 21, 2026, 11:07 PM UTC
We are currently experiencing an incident affecting our Compute - Instance offering in the BHS5 Region The root cause has been identified. Please find the details of this incident below : Start time : 21/05/2026 22:45 UTC Impacted Service(s) : Some instances in the BHS5 region are unreachable. Customers Impact : Customers are 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. Ongoing Actions : Our teams are actively working 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 21, 2026, 11:22 PM UTC
We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 21/05/2026 22:45 UTC End time : 21/05/2026 23:14 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 20, 2026 [SBG5][Compute - Instance] - Public Cloud Incident Notification 1h 15m GRA3, SBG5
Started May 20, 2026, 09:21 AM UTC· resolved May 20, 2026, 10:36 AM UTC
- identified May 20, 2026, 09:21 AM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer in GRA3 region. Here are some supplementary details : Start time : 20/05/2026 08:54 UTC Impacted Service(s) : Some instances in the GRA3 region are unreachable. Customers Impact : Some customers are temporarily unable to access instances located in the specified 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.
- identified May 20, 2026, 09:49 AM UTC
Please find below an update on the situation: Update : Some Instances are once again reachable. Our team remains committed to restoring the missing instances as quickly as possible. We apologize for any inconvenience caused and appreciate your understanding.
- resolved May 20, 2026, 10:36 AM UTC
We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 20/05/2026 08:54 UTC End time : 20/05/2026 10:16 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 19, 2026 [GRA5][Storage] - Block Storage incident notification 1h 7m GRA5
Started May 19, 2026, 05:01 AM UTC· resolved May 19, 2026, 06:09 AM UTC
- investigating May 19, 2026, 05:01 AM UTC
We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the region GRA5. Here are some supplementary details : Start time : 19/05/2026 04:46 UTC Impacted Service(s) : The block storage service is temporarily unavailable for some customers in GRA5 region. Customers Impact : Some customers are temporarily unable to access and use their block Storage located in GRA5 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.
- resolved May 19, 2026, 06:09 AM UTC
We are pleased to inform you that the incident affecting our Block Storage offering in GRA5 region has been resolved. Start time : 19/05/2026 04:46 UTC End time : 19/05/2026 05:55 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 18, 2026 [EU-SOUTH-MILA/B/C][Compute - Instance] - Instance creation incident notification 40m EU-SOUTH-MIL-A, EU-SOUTH-MIL-B, EU-SOUTH-MIL-C, EU-SOUTH-MIL-A and 5 more
Started May 18, 2026, 09:17 AM UTC· resolved May 18, 2026, 09:58 AM UTC
- investigating May 18, 2026, 09:17 AM UTC
We are currently experiencing an event affecting our Compute - Instance offer in EU-SOUTH-MIL. 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 18, 2026, 09: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 regions EU-SOUTH-MIL-A, EU-SOUTH-MIL-B and EU-SOUTH-MIL-C. Here are some supplementary details : Start time : 15/05/2026 12:10 UTC Impacted Service(s) : Creation of Public Cloud on vRack and LoadBalancer is temporarily unavailable in EU-SOUTH-MIL-C region. Since 18/05/2026 09:15 UTC, EU-SOUTH-MIL-A and EU-SOUTH-MIL-B regions are no longer impacted and creation of instances in these regions is available again. Customers Impact : Customers are temporarily unable to create new Public Cloud instances vRack and LoadBalancer in EU-SOUTH-MIL-C 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 May 18, 2026, 09:58 AM UTC
We are pleased to inform you that the incident affecting our Compute - Instance offering in regions EU-SOUTH-MIL-A, EU-SOUTH-MIL-B and EU-SOUTH-MIL-C has been resolved. Start time : 15/05/2026 12:10 UTC End time : 18/05/2026 09: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 May 13, 2026 [GRA][Compute - Instance] - Incident Notification 1h 59m GRA5, GRA7, GRA9, GRA11
Started May 13, 2026, 09:44 AM UTC· resolved May 13, 2026, 11:43 AM UTC
- investigating May 13, 2026, 09:44 AM UTC
We are currently experiencing an event affecting our Compute - Instance offer GRA regions Start time : 13/05/2026 09:03 UTC Our teams are fully committed to investigating this issue and working towards a resolution as soon as possible. As investigations are ongoing, we will share any new findings or updates with you as soon as possible. We apologize for any inconvenience caused and appreciate your understanding.
- resolved May 13, 2026, 11:43 AM UTC
We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 13/05/2026 09:03 UTC End time : 13/05/2026 09:35 UTC Root Cause : This incident was caused by a network equipment issue. We apologize for any inconvenience caused and appreciate your understanding.
Major May 11, 2026 [US-EAST-VA-1][Public Cloud] - Managed Kubernetes Service Incident Notification 3h 2m US-EAST-VA
Started May 11, 2026, 03:52 PM UTC· resolved May 11, 2026, 06:54 PM UTC
- investigating May 11, 2026, 03:52 PM UTC
We are currently investigating an incident affecting our Managed Kubernetes Service offering, which is causing temporary availability issue in the US-EAST-VA-1 region. Here are some supplementary details : Start time : 11/05/2026 15:37 UTC Impacted Service(s) : Some instances in the US-EAST-VA-1 region are unreachable. Customers Impact : Management and creation of new Managed Kubernetes Service clusters is temporarily unavailable. Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- resolved May 11, 2026, 06:54 PM UTC
We are pleased to inform you that the incident affecting our Managed Kubernetes Service offering has been resolved. Start time : 11/05/2026 15:37 UTC End time : 11/05/2026 18:41 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
Major May 11, 2026 [GRA2][Public Cloud] - Compute - Instance Incident Notification 5h 1m GRA1
Started May 11, 2026, 07:16 AM UTC· resolved May 11, 2026, 12:17 PM UTC
- identified May 11, 2026, 07:16 AM UTC
We have determined the origin of the issue affecting our Compute - Instance offer in GRA2 regions. Here are some supplementary details : Start time : 11/05/2026 07:05 UTC Impacted Service(s) : Some instances in GRA2 regions are unreachable. Customers Impact : Customers are temporarily unable to access instances in the specified regions. Root Cause : A service disruption occurred due to an unexpected infrastructure failure Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- resolved May 11, 2026, 12:17 PM UTC
We are pleased to inform you that the incident affecting our Compute - Instance offering in GRA2 has been resolved. Start time : 11/05/2026 07:05 UTC End time : 11/05/2026 11:45 UTC Root Cause : A service disruption occurred due to an unexpected infrastructure failure. We apologize for any inconvenience caused and appreciate your understanding.