Public Cloud Outage History

Started Mar 03, 2026, 04:45 PM UTC· resolved Mar 09, 2026, 03:50 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Dec 17, 2025, 10:37 AM UTC· resolved Mar 10, 2026, 01:10 PM UTC

1. identified Nov 20, 2025, 10:48 AM UTC

   We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Cold archive offer on the specific region. Here are some supplementary details : Start time : 07/11/2025 10:00 UTC Impacted Service(s) : Archiving tasks are temporarily stuck in "Archiving" state. Customers Impact : Customers are temporarily unable to archive their data. 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.

2. identified Dec 01, 2025, 02:21 PM UTC

   We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : We are currently catching up on archiving, but we do not have an estimated time frame to share with you at this time. 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.

3. identified Dec 12, 2025, 04:58 PM UTC

   We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : Archiving tasks aren't stuck anymore but slowness is observed. As soon as a customer request archiving, the data will be billed as if it were on tape even though it may take a while for the data to actually reach the tape. 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.

4. identified Dec 17, 2025, 10:37 AM UTC

   Please find below an update on the situation: Update : We are still catching up on archiving, but it's slower than expected. 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.

5. identified Dec 26, 2025, 09:12 PM UTC

   Please find below an update on the situation: Update : We are continuing our archiving efforts, though completion is taking longer than expected. 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.

6. identified Dec 29, 2025, 04:17 PM UTC

   Please find below an update on the situation: Update : We continue to see a backlog of archiving operations that began on  07 Nov 2025 10:00 UTC. The backlog is being processed, but the rate of completion remains below normal levels, resulting in extended latency for new archiving requests. No new tasks are being blocked, but they are progressing more slowly than expected. 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.

7. identified Jan 08, 2026, 04:42 PM UTC

   Please find below an update on the situation: Update : The completion rate has now returned to normal levels; however, a considerable amount of time will still be required to fully clear the backlog. 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.

8. identified Jan 27, 2026, 10:36 AM UTC

   Please find below an update on the situation: Update : Archive recovery is still underway. We would like to clarify the situation regarding restorations. In the meantime, if a customer needs to restore a bucket in "archiving" status, he must submit a support ticket (the criticality level is at the customer's discretion) so that we can perform the restoration. 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.

9. resolved Mar 10, 2026, 01:10 PM UTC

   We are pleased to inform you that the incident affecting our Cold Archive offer has been resolved. However, some time will be required to fully clear the backlog. Start time : 07/11/2025 10:00 UTC End time : 10/03/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.

Read the full incident report →

Started Oct 30, 2025, 04:15 PM UTC· resolved Apr 17, 2026, 09:42 AM UTC

1. investigating Oct 30, 2025, 04:15 PM UTC

   We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services. Here are some supplementary details : Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

2. identified Oct 31, 2025, 12:18 PM UTC

   We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offer on Kafka services. Here are some supplementary details : Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). Customers Impact : Customers are temporarily unable to upgrade their Kafka version from 3.8 to x.y. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and our teams are working with our provider to restore service as quickly as possible. We will keep you updated on the progress and resolution.

3. identified Nov 03, 2025, 02:50 PM UTC

   We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : Our provider has informed us that the migration from 3.8 to x.y version is more complex than initially anticipated, which is the reason why this feature is currently unavailable. However, customers can deploy Kafka version 3.9 or 4.0 in parallel if they need. Upgrade possibility is expected to be available by end January 2026. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

4. identified Dec 15, 2025, 02:36 PM UTC

   We are continuing to work on a fix for this issue.

5. monitoring Dec 19, 2025, 08:32 AM UTC

   Monitoring remains active for this incident. Update : Our provider is still working to restore the service as quickly as possible. The migration from 3.8 to x.y version is expected to be available by the end of January 2026. We apologize for any inconvenience caused and appreciate your understanding.

6. monitoring Dec 26, 2025, 12:58 PM UTC

   We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : The incident originated on 28/10/2025 12:00 UTC when attempts to upgrade Kafka from version 3.8 to the target x.y release began returning an error. The problem is limited to the upgrade path; existing Kafka clusters continue to operate normally, and no other functionality of the Data & Analytics platform is impacted. Actions in progress : Our teams are working closely with the provider to diagnose the root cause of the upgrade failure. We are monitoring the provider's remediation work in real time and have prepared a fallback path that allows customers to deploy alternative supported versions (e.g., 3.9 or 4.0) in parallel while the primary upgrade path is being restored. Key guidance for customers : No immediate action is required from customers. If you need a newer Kafka version before the official migration is available, you may provision a parallel cluster running version 3.9 or 4.0. We will continue to provide updates as the investigation progresses and will notify you when the upgrade path is fully restored. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and corrected. It is being closely monitored to ensure long-term stability. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding

7. monitoring Jan 07, 2026, 07:22 PM UTC

   We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : We continue to work with our provider 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.

8. monitoring Feb 18, 2026, 01:46 PM UTC

   We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : Our teams are still working closely with our provider to solve 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.

9. monitoring Feb 24, 2026, 01:41 PM UTC

   We have new information regarding the incident that affected your service(s). Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by early March. We will keep you informed as soon as possible. We apologize for any inconvenience caused and appreciate your understanding.

10. monitoring Apr 03, 2026, 02:06 PM UTC

    We have new information regarding the incident that affected your service(s). Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by mid April. We will keep you informed as soon as possible. We apologize for any inconvenience caused and appreciate your understanding.

11. resolved Apr 17, 2026, 09:42 AM UTC

    We are pleased to inform you that the incident affecting our Data & Analytics has been resolved. Start time : 28/10/2025 12:00 UTC End time : 17/04/2026 09:28 UTC Root Cause : This incident was caused by our provider. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →