Public Cloud Status

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

Start time : 07/07/2026 11:45 UTC End time : 07/07/2026 11:56 UTC Root Cause : This incident was caused by a network equipment issue.

We apologize for any inconvenience caused and appreciate your understanding.

Monitoring: Service has been fully restored since 07/07/2026 11:56 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 07/07/2026 11:45 UTC Impacted Service(s) : Creation of AI payloads was temporarily unavailable in GRA region. Customers Impact : Customers were temporarily unable to create AI payloads.

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 : 13/07/2026 16:55 UTC End time : 13/07/2026 22:55 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 BHS1/BHS5 regions.

Here are some supplementary details :

Start time : 13/07/2026 16:55 UTC Impacted Service(s) : Some instances in the BHS1/BHS5 regions are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on the specified regions. 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 currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific BHS1/BHS5 regions.

Here are some supplementary details :

Start time : 13/07/2026 16:55 UTC Impacted Service(s) : Some instances in the BHS1/BHS5 regions are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on the specified regions. 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.

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

Start time : 13/07/2026 16:55 UTC End time : 13/07/2026 22:55 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 BHS1/BHS5 regions.

Here are some supplementary details :

Start time : 13/07/2026 16:55 UTC Impacted Service(s) : Some instances in the BHS1/BHS5 regions are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on the specified regions. 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 currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific BHS1/BHS5 regions.

Here are some supplementary details :

Start time : 13/07/2026 16:55 UTC Impacted Service(s) : Some instances in the BHS1/BHS5 regions are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on the specified regions. 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.

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

Start time : 06/07/2026 20:08 UTC End time : 07/07/2026 21:34 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 07/07/2026 21:34 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 06/07/2026 20:08 UTC Impacted Service(s) : Public network experienced availability and latency issues. Customers Impact : Customers experienced temporary service unavailability or increased latency when accessing their services. Root Cause : This incident was caused by a network equipment issue.

Monitoring: Ongoing Actions: At 20:30 UTC, we will perform an upgrade on the affected network equipment to prevent this issue from recurring.

No customer impact is expected during this maintenance.

Our teams will closely monitor service stability throughout the operation and will remain mobilized until the maintenance has been successfully completed.

We will keep you informed of the progress and notify you once the maintenance has been completed.

We apologize for any inconvenience caused and appreciate your understanding.

Monitoring: Please find the details of this incident below :

Start time : 06/07/2026 20:08 UTC Impacted Service(s) : Public network experienced availability and latency issues. Customers Impact : Customers experienced temporary service unavailability or increased latency when accessing their services. Root Cause : This incident was caused by a network equipment issue. Ongoing Actions : Our team isolated the affected network equipment to restore service. The service has been restored since 07/07/2026 01:25 UTC. Ongoing Actions : Our teams are continuing to investigate the root cause of the incident while closely monitoring system stability to ensure continued stability.

We will keep you updated on the progress of our investigation. We apologize for any inconvenience caused and appreciate your understanding.

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

Here are some supplementary details :

Start time : 06/07/2026 20:08 UTC Impacted Service(s) : Network perturbation was observed for some instances in the GRA1/3/4/5/7/9/11 regions. Customers Impact : Some customers were temporarily facing packet loss on their instances located in the specified regions. Root Cause : A service disruption occurred due to an unexpected underlying 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 offering has been resolved.

Start time : 06/07/2026 20:08 UTC End time : 07/07/2026 21:34 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 07/07/2026 21:34 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 06/07/2026 20:08 UTC Impacted Service(s) : Public network experienced availability and latency issues. Customers Impact : Customers experienced temporary service unavailability or increased latency when accessing their services. Root Cause : This incident was caused by a network equipment issue.

Monitoring: Ongoing Actions: At 20:30 UTC, we will perform an upgrade on the affected network equipment to prevent this issue from recurring.

No customer impact is expected during this maintenance.

Our teams will closely monitor service stability throughout the operation and will remain mobilized until the maintenance has been successfully completed.

We will keep you informed of the progress and notify you once the maintenance has been completed.

We apologize for any inconvenience caused and appreciate your understanding.

Monitoring: Please find the details of this incident below :

Start time : 06/07/2026 20:08 UTC Impacted Service(s) : Public network experienced availability and latency issues. Customers Impact : Customers experienced temporary service unavailability or increased latency when accessing their services. Root Cause : This incident was caused by a network equipment issue. Ongoing Actions : Our team isolated the affected network equipment to restore service. The service has been restored since 07/07/2026 01:25 UTC. Ongoing Actions : Our teams are continuing to investigate the root cause of the incident while closely monitoring system stability to ensure continued stability.

We will keep you updated on the progress of our investigation. We apologize for any inconvenience caused and appreciate your understanding.

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

Here are some supplementary details :

Start time : 06/07/2026 20:08 UTC Impacted Service(s) : Network perturbation was observed for some instances in the GRA1/3/4/5/7/9/11 regions. Customers Impact : Some customers were temporarily facing packet loss on their instances located in the specified regions. Root Cause : A service disruption occurred due to an unexpected underlying 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 offering has been resolved.

Start time : 06/07/2026 20:08 UTC End time : 07/07/2026 21:34 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 07/07/2026 21:34 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 06/07/2026 20:08 UTC Impacted Service(s) : Public network experienced availability and latency issues. Customers Impact : Customers experienced temporary service unavailability or increased latency when accessing their services. Root Cause : This incident was caused by a network equipment issue.

Monitoring: Ongoing Actions: At 20:30 UTC, we will perform an upgrade on the affected network equipment to prevent this issue from recurring.

No customer impact is expected during this maintenance.

Our teams will closely monitor service stability throughout the operation and will remain mobilized until the maintenance has been successfully completed.

We will keep you informed of the progress and notify you once the maintenance has been completed.

We apologize for any inconvenience caused and appreciate your understanding.

Monitoring: Please find the details of this incident below :

Start time : 06/07/2026 20:08 UTC Impacted Service(s) : Public network experienced availability and latency issues. Customers Impact : Customers experienced temporary service unavailability or increased latency when accessing their services. Root Cause : This incident was caused by a network equipment issue. Ongoing Actions : Our team isolated the affected network equipment to restore service. The service has been restored since 07/07/2026 01:25 UTC. Ongoing Actions : Our teams are continuing to investigate the root cause of the incident while closely monitoring system stability to ensure continued stability.

We will keep you updated on the progress of our investigation. We apologize for any inconvenience caused and appreciate your understanding.

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

Here are some supplementary details :

Start time : 06/07/2026 20:08 UTC Impacted Service(s) : Network perturbation was observed for some instances in the GRA1/3/4/5/7/9/11 regions. Customers Impact : Some customers were temporarily facing packet loss on their instances located in the specified regions. Root Cause : A service disruption occurred due to an unexpected underlying 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 offering has been resolved.

Start time : 06/07/2026 20:08 UTC End time : 07/07/2026 21:34 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 07/07/2026 21:34 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 06/07/2026 20:08 UTC Impacted Service(s) : Public network experienced availability and latency issues. Customers Impact : Customers experienced temporary service unavailability or increased latency when accessing their services. Root Cause : This incident was caused by a network equipment issue.

Monitoring: Ongoing Actions: At 20:30 UTC, we will perform an upgrade on the affected network equipment to prevent this issue from recurring.

No customer impact is expected during this maintenance.

Our teams will closely monitor service stability throughout the operation and will remain mobilized until the maintenance has been successfully completed.

We will keep you informed of the progress and notify you once the maintenance has been completed.

We apologize for any inconvenience caused and appreciate your understanding.

Monitoring: Please find the details of this incident below :

Start time : 06/07/2026 20:08 UTC Impacted Service(s) : Public network experienced availability and latency issues. Customers Impact : Customers experienced temporary service unavailability or increased latency when accessing their services. Root Cause : This incident was caused by a network equipment issue. Ongoing Actions : Our team isolated the affected network equipment to restore service. The service has been restored since 07/07/2026 01:25 UTC. Ongoing Actions : Our teams are continuing to investigate the root cause of the incident while closely monitoring system stability to ensure continued stability.

We will keep you updated on the progress of our investigation. We apologize for any inconvenience caused and appreciate your understanding.

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

Here are some supplementary details :

Start time : 06/07/2026 20:08 UTC Impacted Service(s) : Network perturbation was observed for some instances in the GRA1/3/4/5/7/9/11 regions. Customers Impact : Some customers were temporarily facing packet loss on their instances located in the specified regions. Root Cause : A service disruption occurred due to an unexpected underlying 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 offering has been resolved.

Start time : 06/07/2026 20:08 UTC End time : 07/07/2026 21:34 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 07/07/2026 21:34 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 06/07/2026 20:08 UTC Impacted Service(s) : Public network experienced availability and latency issues. Customers Impact : Customers experienced temporary service unavailability or increased latency when accessing their services. Root Cause : This incident was caused by a network equipment issue.

Monitoring: Ongoing Actions: At 20:30 UTC, we will perform an upgrade on the affected network equipment to prevent this issue from recurring.

No customer impact is expected during this maintenance.

Our teams will closely monitor service stability throughout the operation and will remain mobilized until the maintenance has been successfully completed.

We will keep you informed of the progress and notify you once the maintenance has been completed.

We apologize for any inconvenience caused and appreciate your understanding.

Monitoring: Please find the details of this incident below :

Start time : 06/07/2026 20:08 UTC Impacted Service(s) : Public network experienced availability and latency issues. Customers Impact : Customers experienced temporary service unavailability or increased latency when accessing their services. Root Cause : This incident was caused by a network equipment issue. Ongoing Actions : Our team isolated the affected network equipment to restore service. The service has been restored since 07/07/2026 01:25 UTC. Ongoing Actions : Our teams are continuing to investigate the root cause of the incident while closely monitoring system stability to ensure continued stability.

We will keep you updated on the progress of our investigation. We apologize for any inconvenience caused and appreciate your understanding.

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

Here are some supplementary details :

Start time : 06/07/2026 20:08 UTC Impacted Service(s) : Network perturbation was observed for some instances in the GRA1/3/4/5/7/9/11 regions. Customers Impact : Some customers were temporarily facing packet loss on their instances located in the specified regions. Root Cause : A service disruption occurred due to an unexpected underlying 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 offering has been resolved.

Start time : 06/07/2026 20:08 UTC End time : 07/07/2026 21:34 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 07/07/2026 21:34 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 06/07/2026 20:08 UTC Impacted Service(s) : Public network experienced availability and latency issues. Customers Impact : Customers experienced temporary service unavailability or increased latency when accessing their services. Root Cause : This incident was caused by a network equipment issue.

Monitoring: Ongoing Actions: At 20:30 UTC, we will perform an upgrade on the affected network equipment to prevent this issue from recurring.

No customer impact is expected during this maintenance.

Our teams will closely monitor service stability throughout the operation and will remain mobilized until the maintenance has been successfully completed.

We will keep you informed of the progress and notify you once the maintenance has been completed.

We apologize for any inconvenience caused and appreciate your understanding.

Monitoring: Please find the details of this incident below :

Start time : 06/07/2026 20:08 UTC Impacted Service(s) : Public network experienced availability and latency issues. Customers Impact : Customers experienced temporary service unavailability or increased latency when accessing their services. Root Cause : This incident was caused by a network equipment issue. Ongoing Actions : Our team isolated the affected network equipment to restore service. The service has been restored since 07/07/2026 01:25 UTC. Ongoing Actions : Our teams are continuing to investigate the root cause of the incident while closely monitoring system stability to ensure continued stability.

We will keep you updated on the progress of our investigation. We apologize for any inconvenience caused and appreciate your understanding.

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

Here are some supplementary details :

Start time : 06/07/2026 20:08 UTC Impacted Service(s) : Network perturbation was observed for some instances in the GRA1/3/4/5/7/9/11 regions. Customers Impact : Some customers were temporarily facing packet loss on their instances located in the specified regions. Root Cause : A service disruption occurred due to an unexpected underlying 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 offering has been resolved.

Start time : 06/07/2026 20:08 UTC End time : 07/07/2026 21:34 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 07/07/2026 21:34 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 06/07/2026 20:08 UTC Impacted Service(s) : Public network experienced availability and latency issues. Customers Impact : Customers experienced temporary service unavailability or increased latency when accessing their services. Root Cause : This incident was caused by a network equipment issue.

Monitoring: Ongoing Actions: At 20:30 UTC, we will perform an upgrade on the affected network equipment to prevent this issue from recurring.

No customer impact is expected during this maintenance.

Our teams will closely monitor service stability throughout the operation and will remain mobilized until the maintenance has been successfully completed.

We will keep you informed of the progress and notify you once the maintenance has been completed.

We apologize for any inconvenience caused and appreciate your understanding.

Monitoring: Please find the details of this incident below :

Start time : 06/07/2026 20:08 UTC Impacted Service(s) : Public network experienced availability and latency issues. Customers Impact : Customers experienced temporary service unavailability or increased latency when accessing their services. Root Cause : This incident was caused by a network equipment issue. Ongoing Actions : Our team isolated the affected network equipment to restore service. The service has been restored since 07/07/2026 01:25 UTC. Ongoing Actions : Our teams are continuing to investigate the root cause of the incident while closely monitoring system stability to ensure continued stability.

We will keep you updated on the progress of our investigation. We apologize for any inconvenience caused and appreciate your understanding.

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

Here are some supplementary details :

Start time : 06/07/2026 20:08 UTC Impacted Service(s) : Network perturbation was observed for some instances in the GRA1/3/4/5/7/9/11 regions. Customers Impact : Some customers were temporarily facing packet loss on their instances located in the specified regions. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.

Resolved: We are pleased to inform you that the incident affecting our Load Balancer service has been resolved.

Start time : 09/07/2026 19:20 UTC End time : 10/07/2026 01:50 UTC Root Cause : This incident was caused by a software issue.

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 Load Balancer service on the specific region.

Here are some supplementary details :

Start time : 09/07/2026 19:20 UTC Impacted Service(s) : Public Cloud API is temporarily facing perturbations. Creation or modification of any LoadBalancer can have issues. Customers Impact : Customers are temporarily facing issues when trying to use the API, create or modify their Loadbalancer. 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.

Investigating: We are currently investigating an incident affecting our Containers & Orchestration offering, which is causing temporary issue in the EU-WEST-PAR region.

Here are some supplementary details :

Start time : 09/07/2026 19:20 UTC Impacted Service(s) : Public Cloud API is temporarily facing perturbations. Creation or modification of any LoadBalancer can have issues. Customers Impact : Customers are temporarily facing issues when trying to use the API, create or modify their Loadbalancer. 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 Containers & Orchestration offering has been resolved.

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

Here are some supplementary details :

Start time : 06/07/2026 20:08 UTC Impacted Service(s) : The Managed Kubernetes Service experienced delays in managed node provisioning. Customers Impact : Customers may have experienced network disruptions when using the load balancer and delays in managed node delivery. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.

Investigating: We are currently investigating an incident affecting our Containers & Orchestration offering, which is causing temporary availability issue in the GRA5/7/9/11 regions.

Here are some supplementary details :

Start time : 06/07/2026 20:08 UTC Impacted Service(s) : The Managed Kubernetes Service is experiencing delays in managed node provisioning. Customers Impact : Customers may experience network disruptions when using the load balancer and delays in managed node delivery. 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 Containers & Orchestration offering has been resolved.

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

Here are some supplementary details :

Start time : 06/07/2026 20:08 UTC Impacted Service(s) : The Managed Kubernetes Service experienced delays in managed node provisioning. Customers Impact : Customers may have experienced network disruptions when using the load balancer and delays in managed node delivery. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.

Investigating: We are currently investigating an incident affecting our Containers & Orchestration offering, which is causing temporary availability issue in the GRA5/7/9/11 regions.

Here are some supplementary details :

Start time : 06/07/2026 20:08 UTC Impacted Service(s) : The Managed Kubernetes Service is experiencing delays in managed node provisioning. Customers Impact : Customers may experience network disruptions when using the load balancer and delays in managed node delivery. 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 Containers & Orchestration offering has been resolved.

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

Here are some supplementary details :

Start time : 06/07/2026 20:08 UTC Impacted Service(s) : The Managed Kubernetes Service experienced delays in managed node provisioning. Customers Impact : Customers may have experienced network disruptions when using the load balancer and delays in managed node delivery. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.

Investigating: We are currently investigating an incident affecting our Containers & Orchestration offering, which is causing temporary availability issue in the GRA5/7/9/11 regions.

Here are some supplementary details :

Start time : 06/07/2026 20:08 UTC Impacted Service(s) : The Managed Kubernetes Service is experiencing delays in managed node provisioning. Customers Impact : Customers may experience network disruptions when using the load balancer and delays in managed node delivery. 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 Containers & Orchestration offering has been resolved.

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

Here are some supplementary details :

Start time : 06/07/2026 20:08 UTC Impacted Service(s) : The Managed Kubernetes Service experienced delays in managed node provisioning. Customers Impact : Customers may have experienced network disruptions when using the load balancer and delays in managed node delivery. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.

Investigating: We are currently investigating an incident affecting our Containers & Orchestration offering, which is causing temporary availability issue in the GRA5/7/9/11 regions.

Here are some supplementary details :

Start time : 06/07/2026 20:08 UTC Impacted Service(s) : The Managed Kubernetes Service is experiencing delays in managed node provisioning. Customers Impact : Customers may experience network disruptions when using the load balancer and delays in managed node delivery. 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 Managed Private Registry service has been resolved.

Start time : 10/07/2026 20:20 UTC End time : 11/07/2026 00:10 UTC Root Cause : This incident was caused by this maintenance : https://public-cloud.status-ovhcloud.com/incidents/m5qn00qgl9zh

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 Managed Private Registry service on the EU-WEST-PAR region.

Here are some supplementary details :

Start time : 10/07/2026 20:20 UTC Impacted Service(s) : Registries are temporarily unavailable. Customers Impact : Customers are temporarily facing issues when trying to use connect to Harbor UI, pull or push new images. Root Cause : This incident is caused by this maintenance : https://public-cloud.status-ovhcloud.com/incidents/m5qn00qgl9zh 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 Containers & Orchestration offering has been resolved.

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

Here are some supplementary details :

Start time : 06/07/2026 20:08 UTC Impacted Service(s) : The Managed Private Registry service experienced intermittent disruptions or temporary unavailability. Customers Impact : Customers may have experienced issues pushing, pulling, or deploying container images. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.

Investigating: We are currently investigating an incident affecting our Containers & Orchestration offering, which is causing temporary availability issue in the GRA region.

Here are some supplementary details :

Start time : 06/07/2026 20:08 UTC Impacted Service(s) : The Managed Private Registry service may experience intermittent disruptions or temporary unavailability. Customers Impact : Customers may experience issues pushing, pulling, or deploying container images. 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.