Public Cloud Status

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.

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

Here is detail for this incident : Start time : 05/11/2025 15:40 UTC Impacted Service(s) : Private image is temporarily unavailable for Public Cloud instances in the LocalZones. Customers Impact : Customers are temporarily unable to create images. 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: 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 Network has been resolved.

Start time : 20/11/2025 15:14 UTC End time : 20/11/2025 16:06 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 Network offering, which is causing temporary latency issue in the GRA3 region.

Here are some supplementary details :

Start time : 20/11/2025 15:14 UTC Impacted Service(s) : API may be slow or responding some errors 500. 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 Object Storage offer in the specific regions : GRA, SBG, UK, DE, WAW has been resolved.

Start time : 19/11/2025 02:00 UTC End time : 19/11/2025 05:30 UTC Root Cause : This incident was caused by a software issue.

We apologize for any inconvenience caused and appreciate your understanding.

Monitoring: Service has been fully restored since 19/11/2025 05:30 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 19/11/2025 02:00 UTC Impacted Service(s) : We were observing a slight increase of error rate or response time on some object storage endpoint Customers Impact : Customers were facing Http500 errors and low latencies.

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 Obect Storage offer in the specific regions : Gra, Sbg, Uk, De, Waw .

Here are some supplementary details :

Start time : 19/11/2025 02:00 UTC Impacted Service(s) : We are observing a slight increase of error rate or response time on some object storage endpoint Customers Impact : Customers are facing Http500 errors and low latencies. 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: Service has been fully restored since 19/11/2025 03:45 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 19/11/2025 02:00 UTC Impacted Service(s) : We were observing a slight increase of error rate or response time on some object storage endpoint Customers Impact : Customers were facing Http500 errors and low latencies.

We apologize for any inconvenience caused and appreciate your understanding.

Investigating: We are currently experiencing an event affecting our Object Storage offer in the specific regions : Gra, Sbg, Uk, De, Waw .

Start time : 19/11/2025 02: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.

Resolved: We are pleased to inform you that the incident affecting our AI & Machine Learning has been resolved.

Start time : 17/11/2025 13:55 UTC End time : 17/11/2025 14:15 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 AI & Machine Learning offering, which is causing temporary availability issue in the AI Endpoint.

Here are some supplementary details :

Start time : 17/11/2025 13:55 UTC Impacted Service(s) : The AI Endpoint service is temporarily unavailable. Customers Impact : Customers cannot temporarily use the AI Endpoint service. 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 Compute - Instance offering has been resolved.

Start time : 15/11/2025 05:22 UTC End time : 15/11/2025 23:22 UTC Root Cause : This incident is due to an unexpected infrastructure malfunction.

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 : Our technical specialists are still actively working to fix the 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.

Identified: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our technical team continues to work on resolving 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: We have determined the origin of the incident affecting our Compute - Instance offering in the region DE1.

Here is detail for this incident : Start time : 15/11/2025 5:22 UTC Impacted Service(s) : Some instances in the DE1 region are unreachable. Customers Impact : Some customers are temporarily unable to access and use their instances located in the specified region. Root Cause : This incident is 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.

Resolved: We are pleased to inform you that the incident affecting our Compute - Instance has been resolved.

Start time : 15/11/2025 08:47 UTC End time : 15/11/2025 10:35 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.

Identified: We have determined the origin of the incident affecting our Compute - Instance offering in the region BHS1.

Here is detail for this incident : Start time : 15/11/2025 8:47 UTC Impacted Service(s) : Some instances in the BHS1 region are unreachable. Customers Impact : Some customers are temporarily unable to access and use their instances located in the specified region. Root Cause : This incident is 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.