Public Cloud Status

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

Start time : 26/02/2026 12:00 UTC End time : 04/03/2026 16:36 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 03/03/2026 17:00 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 26/02/2026 12:00 UTC Impacted Service(s) : The mistral model is operational again. Customers Impact : Customers will no longer experience issues when using the Mistral model.

We apologize for any inconvenience caused and appreciate your understanding.

Identified: We are currently investigating an incident affecting our AI & Machine Learning offering, which is causing temporary availability issue in the mistral endpoint.

Here are some supplementary details :

Start time : 26/02/2026 12:00 UTC Impacted Service(s) : The mistral model may have slowness and unavailabilty. Customers Impact : Some customers may experience issues when using the Mistral model. 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.

Identified: We are currently investigating an incident affecting our AI & Machine Learning offering, which is causing temporary availability issue in the mistral endpoint.

Here are some supplementary details :

Start time : 26/02/2026 12:00 UTC Impacted Service(s) : The mistral model may have slowness and unavailabilty. 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: Service has been fully restored since 06/03/2026 10:00 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 06/03/2026 15:22 UTC Impacted Service(s) : LLama3.3-70B model is experiencing performance issues.

We apologize for any inconvenience caused and appreciate your understanding.

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

Please find below an update on the situation: Update : The issue has been identified and is related to an unusually high load on the LLama3.3-70B model. Our teams are monitoring the situation and working to mitigate the impact. 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 AI & Machine Learning offering, which is causing temporary latency issue in the LLama3.3-70B model.

Here are some supplementary details :

Start time : 04/03/2026 10:00 UTC Impacted Service(s) : LLama3.3-70B model is experiencing performance issues. Customers Impact : Latency and unavailability can be observed on the customer side. 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 offer has been resolved.

Start time : 08/03/2026 09:00 UTC End time : 08/03/2026 13:38 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 are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific region.

Here are some supplementary details :

Start time : 08/03/2026 09:00 UTC Impacted Service(s) : Some instances in the GRA1 region are unreachable. Customers Impact : Some customers are temporarily unable to acess and use their instances 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.

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

Start time : 03/03/2026 16:33 UTC End time : 03/03/2026 18:45 UTC Root Cause : A service disruption occurred 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 : Most of the instances are now operational again. Ongoing Actions : Our teams are mobilised to restore the remaining instances 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:

Start time : 03/03/2026 16:33 UTC Impacted Service(s) : Some instances in the Graveline region are unreachable. Customers Impact : Some customers are temporarily unable to access and use their instances in the specified region. Root Cause : A service disruption occurred 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.

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

Here are some supplementary details :

Start time : 03/03/2026 16:33 UTC Impacted Service(s) : Some instances in the Graveline region are unreachable. 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 has been resolved.

Start time : 05/03/2026 22:15 UTC End time : 05/03/2026 00: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.

Identified: We are currently investigating an incident affecting our offering, which is causing temporary issue in the SBG5 region.

Here are some supplementary details :

Start time : 04/03/2026 22:15 UTC Impacted Service(s) : The API in the SBG5 region was temporarily degraded. Customers Impact : For these regions, you might have issues to create, start, or manage your instances and create or attach new volumes. Your instances already running are not impacted. 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: We are currently experiencing an event affecting our Compute - Instance offer.

Start time : 04/03/2026 22:15 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 Containers & Orchestration has been resolved.

Start time : 05/03/2026 09:00 UTC End time : 05/03/2026 17:20 UTC Root Cause : A service disruption was currently occurring due to an unexpected infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.

Monitoring: Service has been restored since 05/03/2026 17:20 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 05/03/2026 09:00 UTC Impacted Service(s) : Nodepools may have been rolled out and reinstalled. Root Cause : A service disruption is currently occurring due to an unexpected infrastructure malfunction.

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 Containers & Orchestration offer in AP-SOUTH-MUM/EU-WEST-PAR/EU-SOUTH-MIL/RBX.

Here are some supplementary details :

Start time : 05/03/2026 09:00 UTC Impacted Service(s) : Nodepools may have been rolled out and reinstalled. Customers Impact : Some customers may still experience a partial impact during the nodepool updates. 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.

Investigating: We are currently experiencing an event affecting our Containers & Orchestration Managed Kubernetes Service offer.

Start time : 05/03/2026 09: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 Containers & Orchestration has been resolved.

Start time : 05/03/2026 09:00 UTC End time : 05/03/2026 17:20 UTC Root Cause : A service disruption was currently occurring due to an unexpected infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.

Monitoring: Service has been restored since 05/03/2026 17:20 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 05/03/2026 09:00 UTC Impacted Service(s) : Nodepools may have been rolled out and reinstalled. Root Cause : A service disruption is currently occurring due to an unexpected infrastructure malfunction.

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 Containers & Orchestration offer in AP-SOUTH-MUM/EU-WEST-PAR/EU-SOUTH-MIL/RBX.

Here are some supplementary details :

Start time : 05/03/2026 09:00 UTC Impacted Service(s) : Nodepools may have been rolled out and reinstalled. Customers Impact : Some customers may still experience a partial impact during the nodepool updates. 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.

Investigating: We are currently experiencing an event affecting our Containers & Orchestration Managed Kubernetes Service offer.

Start time : 05/03/2026 09: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 Containers & Orchestration has been resolved.

Start time : 05/03/2026 09:00 UTC End time : 05/03/2026 17:20 UTC Root Cause : A service disruption was currently occurring due to an unexpected infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.

Monitoring: Service has been restored since 05/03/2026 17:20 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 05/03/2026 09:00 UTC Impacted Service(s) : Nodepools may have been rolled out and reinstalled. Root Cause : A service disruption is currently occurring due to an unexpected infrastructure malfunction.

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 Containers & Orchestration offer in AP-SOUTH-MUM/EU-WEST-PAR/EU-SOUTH-MIL/RBX.

Here are some supplementary details :

Start time : 05/03/2026 09:00 UTC Impacted Service(s) : Nodepools may have been rolled out and reinstalled. Customers Impact : Some customers may still experience a partial impact during the nodepool updates. 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.

Investigating: We are currently experiencing an event affecting our Containers & Orchestration Managed Kubernetes Service offer.

Start time : 05/03/2026 09: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 Containers & Orchestration has been resolved.

Start time : 05/03/2026 09:00 UTC End time : 05/03/2026 17:20 UTC Root Cause : A service disruption was currently occurring due to an unexpected infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.

Monitoring: Service has been restored since 05/03/2026 17:20 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 05/03/2026 09:00 UTC Impacted Service(s) : Nodepools may have been rolled out and reinstalled. Root Cause : A service disruption is currently occurring due to an unexpected infrastructure malfunction.

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 Containers & Orchestration offer in AP-SOUTH-MUM/EU-WEST-PAR/EU-SOUTH-MIL/RBX.

Here are some supplementary details :

Start time : 05/03/2026 09:00 UTC Impacted Service(s) : Nodepools may have been rolled out and reinstalled. Customers Impact : Some customers may still experience a partial impact during the nodepool updates. 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.

Investigating: We are currently experiencing an event affecting our Containers & Orchestration Managed Kubernetes Service offer.

Start time : 05/03/2026 09: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.