Public Cloud Status

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our AI & Machine Learning offer on the global region.

Here are some supplementary details :

Start time : 06/01/2026 18:30 UTC Impacted Service(s) : Latency on Qwen3-32B. Customers Impact : Customers may temporarily experience latency on the AI & Machine Learning service with the Qwen3-32B model. 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.

Investigating: We are currently investigating an incident affecting our AI & Machine Learning offering, which is causing temporary latency issue in the global region.

Here are some supplementary details :

Start time : 06/01/2026 18:30 UTC Impacted Service(s) : Latency on Qwen3-32B. Customers Impact : Customers may temporarily experience latency on the AI & Machine Learning service with the Qwen3-32B 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.

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

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

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

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.

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

Start time : 07/01/2026 22:31 UTC End time : 08/01/2026 08:45 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 08/01/2026 08:45 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 07/01/2026 22:31 UTC Impacted Service(s) : AI Endpoint was temporarily unavailable. Customers Impact : Customers were temporarily unable to use AI Endpoint.

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 on AI Endpoint .

Here are some supplementary details :

Start time : 07/01/2026 22:31 UTC Impacted Service(s) : AI Endpoint is temporarily unavailable. Customers Impact : Customers are temporarily unable to use AI Endpoint. 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 Identity, Security & Operations has been resolved.

Start time : 07/01/2026 15:00 UTC End time : 07/01/2026 18:00 UTC Root Cause : A service disruption occurred due to an unexpected infrastructure failure.

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 Identity, Security & Operations offer on the specific SYD region.

Here are some supplementary details :

Start time : 07/01/2026 15:00 UTC Impacted Service(s) : The KMS service is temporarily unavailable. Customers Impact : Customers are temporarily unable to access the Key Management Service located in SYD 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.

Investigating: We are currently experiencing an event affecting our Identity, Security & Operations offer.

Start time : 07/01/2026 15: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.

Investigating: We are currently experiencing an event affecting our Identity, Security & Operations.

Start time : 07/01/2026 15: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 would like to inform you that the incident on our Object Storage offer has now been resolved.

Here is detail for this incident : Start time : 05/01/2026 14:45 UTC End time : 05/01/2026 16:22 UTC Root Cause : A service disruption occurred due to an unexpected infrastructure failure.

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

Monitoring: Service has been fully restored since 05/01/2026 16:22 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 05/01/2026 14:45 UTC Impacted Service(s) : Object storage was temporarily unavailable in EU-WEST-PAR. Customers Impact : Customers were temporarily getting 503 errors when trying to access their object storage.

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 Object Storage offer in the EU-WEST-PAR region.

Here are some supplementary details :

Start time : 05/01/2026 14:45 UTC Impacted Service(s) : Object storage is temporarily unavailable in EU-WEST-PAR. Customers Impact : Customers are temporarily getting 503 errors when trying to access their object storage. 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 experiencing an event affecting our Object Storage offer in the EU-WEST-PAR region.

Start time : 05/01/2026 14:45 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 had an incident affecting our Compute - Instance offering, which has caused temporary latency issue in the AP-SOUTH-MUM-1.

Here are some supplementary details :

Start time : 04/01/2026 22:48 UTC End time : 04/01/2026 22:51 UTC Impacted Service(s) : The API in the AP-SOUTH-MUM-1 region was temporarily degraded. Customers Impact : Customers may had error on the API Root Cause : A service disruption occured due to an unexpected infrastructure malfunction.

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 : 02/01/2026 23:50 UTC End time : 02/01/2026 23:58 UTC Impacted Service(s) : Some instances in GRA5, GRA7, GRA9 and GRA11 regions were temporarily unreachable. Customers Impact : Some customers were temporarily unable to access and use their instances. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.