Public Cloud Status

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Monitoring: 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.

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

Identified: 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.

Identified: 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.

Investigating: 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.

Resolved: We are pleased to inform you that the incident affecting our Volume Snapshot (Ceph) in BHS3 and BHS5 has been resolved.

Start time : 19/12/2025 15:11 UTC End time : 19/12/2025 15:31 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.

Monitoring: Service has been fully restored since 19/12/2025 15:31 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 19/12/2025 15:11 UTC Impacted Service(s) : Latency was observed for some volume snapshot in BHS3 and BHS5. Customers Impact : Some customers faced temporarily latency for a couple of seconds while trying to access to their Volume Snapshot (Ceph). Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.

Resolved: This incident has been resolved.

Investigating: We are currently experiencing an event affecting our Load Balancer offer.

Start time : 18/12/2025 10:30 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: We would like to inform you that the incident on our Public Cloud offering has now been resolved.

Here is detail for this incident : Start time : 18/12/2025 08:50 UTC End time : 18/12/2025 09:48 UTC Root Cause : This incident is caused by a software issue.

We thank you for your understanding and patience throughout this incident.

Identified: We have determined the origin of the incident affecting our Public Cloud offering on the BHS1 Region.

Here is detail for this incident : Start time : 18/12/2025 08:50 UTC Impacted Service(s) : RabbitMQ service is temporarily unavailable. 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: We are pleased to inform you that the incident affecting our Compute - Instance offering, which was causing temporary availability issue in the GRA9 region has been resolved.

Start time : 15/12/2025 11:06 UTC End time : 15/12/2025 15:37 UTC Root Cause : A service disruption occurred due to an unexpected infrastructure failure

We apologize for any inconvenience caused and appreciate your understanding.

Monitoring: Service has been fully restored since 15/12/2025 15:37 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 15/12/2025 11:06 UTC Impacted Service(s) : Creation/Modification/Deletion of network components may not have worked as expected. Customers Impact : Customers may have faced difficulties to create, modificate and delete some network components.

We apologize for any inconvenience caused and appreciate your understanding.

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offering, which is causing temporary availability issue in the GRA9 region.

Here are some supplementary details :

Start time : 15/12/2025 11:06 UTC Impacted Service(s) : Creation/Modification/Deletion of network components may not work as expected. Customers Impact : Customers may face difficulties to create, modificate and delete some network components. 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.

Investigating: We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary availability issue in the GRA9 region.

Here are some supplementary details :

Start time : 15/12/2025 11:06 UTC Impacted Service(s) : Creation/Modification/Deletion of network components may not work as expected. 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: We are pleased to inform you that the incident affecting our Storage and Compute has been resolved.

Start time : 15/12/2025 07:52 UTC End time : 15/12/2025 08:59 UTC Root Cause : A service disruption occurred due to an unexpected infrastructure failure.

We apologize for any inconvenience caused and appreciate your understanding.

Investigating: We are currently investigating an incident affecting our Storage and Compute offering, which is causing temporary latency issue in the GRA5 region.

Here are some supplementary details :

Start time : 15/12/2025 07:52 UTC Impacted Service(s) : Block storage/Compute experiences latency for some customers. 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.