Public Cloud Status

Monitoring: We would like to inform you that our service has been fully restored as of 03/11/2026 09:53 UTC. Monitoring is still in place to ensure long-term stability.

Please find the details of this incident below :

Start time : 27/10/2026 20:00 UTC Impacted Service(s) : Object Storage S3 experienced increased response times in the specified region. Customers Impact : Customers may have experienced slowness when uploading or retrieving their data located in the specified region. Root Cause : This incident was caused by a hardware issue.

We apologize for any inconvenience caused and appreciate your understanding.

Investigating: We are currently experiencing an incident affecting our Object Storage offering, which is causing temporary latency issues in the EU-WEST-PAR region.

Please find the details of this incident below :

Start time : 27/10/2026 20:00 UTC Impacted Service(s) : Object Storage S3 is experiencing increased response times in the specified region. Customers Impact : Customers may experience slowness when uploading or retrieving their data located in the specified region. 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 would like to inform you that the incident affecting our Network offering has now been resolved.

Please find the details of this incident below :

Start time : 03/11/2026 17:00 UTC End time : 03/11/2026 19:13 UTC Impacted Service(s) : The Load Balancer delivery service in the DE1 region was temporarily unavailable. Customers Impact : Customers were temporarily unable to have their Load Balancer services delivered in the DE1 region. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

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

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Network offer on the specific DE1.

Here are some supplementary details :

Start time : 03/11/2026 17:00 UTC Impacted Service(s) : The load balancer delivery service in the DE1 region is temporarily unavailable. Customers Impact : Customers are temporarily unable to have their load balancer services delivered in the DE1 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.

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

Start time : 03/11/2026 09:13 UTC End time : 03/11/2026 15:31 UTC Root Cause : This incident was caused by a software issue.

We apologize for any inconvenience caused and appreciate your understanding.

Investigating: Please find an update of this incident below :

Update : Managed Kubernetes Service in the GRA11 region is also impacted by this incident. Customers may experience API errors when creating, modifying or managing their Kubernetes clusters. 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.

Investigating: We are currently experiencing an incident affecting our Network offering, which is causing temporary availability issues in the GRA11 region.

Please find the details of this incident below :

Start time : 03/11/2026 09:13 UTC Impacted Service(s) : The Network API for public network and private network (vRack) is temporarily unstable in the specified region. Customers Impact : Customers may experience API errors when creating, modifying or managing their public and private network (vRack) configurations. 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 would like to inform you that the incident affecting our Network offering in the DE1 region has now been resolved.

Please find the details of this incident below :

Start time : 03/11/2026 08:10 UTC End time : 03/11/2026 12:53 UTC Impacted Service(s) : The Network API for public network and private network (vRack) was temporarily unstable in the specified region. Customers Impact : Customers may have experienced API errors when creating, modifying or managing their public and private network (vRack) configurations. Root Cause : This incident was caused by a software issue.

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

Investigating: Please find an update of this incident below :

Update : Managed Kubernetes Service in the DE1 region is also impacted by this incident. Customers may experience API errors when creating, modifying or managing their Kubernetes clusters. 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.

Investigating: We are currently experiencing an incident affecting our Network offering, which is causing temporary availability issues in the DE1 region.

Please find the details of this incident below :

Start time : 03/11/2026 08:10 UTC Impacted Service(s) : The Network API for public network and private network (vRack) is temporarily unstable in the specified region. Customers Impact : Customers may experience API errors when creating, modifying or managing their public and private network (vRack) configurations. 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 would like to inform you that an incident affected our AI & Machine Learning offering. This incident has since been resolved.

Please find the details of this incident below :

Start time : 31/10/2026 07:08 UTC End time : 31/10/2026 07:58 UTC Impacted Service(s) : AI Notebooks, AI Training and AI Deploy services were temporarily unavailable. Customers Impact : Customers were temporarily unable to create, manage or access their notebooks, training jobs and AI applications. Root Cause : This incident was caused by a software issue.

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

Resolved: We would like to inform you that the incident affecting our Public Cloud offering has now been resolved.

Please find the details of this incident below :

Start time : 02/11/2026 09:22 UTC End time : 02/11/2026 18:32 UTC Impacted Service(s) : Some network administrative tasks may have been temporarily slowed down. This did not affect instances. Customers Impact : Customers may have experienced errors or delays when creating or modifying the network configuration of their instances. Root Cause : This incident was caused by a software issue.

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

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 is actively working on the incident. We currently have an ETA of 02/11/2026 19:00 UTC. We will update this page if we receive any further information before then. 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 incident affecting our Public Cloud offering in the DE1 region. The root cause has been identified.

Please find the details of this incident below :

Start time : 02/11/2026 09:22 UTC Impacted Service(s) : Some network administrative tasks may be temporarily slowed down. This does not affect instances. Customers Impact : Customers may experience errors or delays when creating or modifying the network configuration of their instances. Root Cause : This incident is caused by a software issue. Ongoing Actions : Our teams are actively working 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 : 01/11/2026 17:55 UTC End time : 01/11/2026 19:30 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 affects your service(s).

Please find below an update on the situation :

Update :

Some instances in the SBG7 region are temporarily unreachable as well.

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 offering in the specific SBG5 region.

Here are some supplementary details :

Start time : 01/11/2026 17:55 UTC Impacted Service(s) : Some instances in the SBG5 region are temporarily unreachable. Customers Impact : Some customers are temporarily unable to access instances located 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.

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 : 29/10/2026 10:00 UTC End time : 29/10/2026 16:18 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 investigating an incident affecting our Containers & Orchestration offering, which is causing temporary functionality issue in the EU-WEST-PAR region.

Here are some supplementary details :

Start time : 29/10/2026 10:00 UTC Impacted Service(s) : New MKS cluster delivery is currently unavailable on the specific region. Customers Impact : Customers are currently unable to create new MKS clusters. 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 : 29/10/2026 15:43 UTC End time : 29/10/2026 16: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 experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific RBX region].

Here are some supplementary details :

Start time : 29/10/2026 15:43 UTC Impacted Service(s) : Some instances in the RBX region are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on 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.

Resolved: We are pleased to inform you that the incident affecting our Network offering has been resolved. All vRack tasks are running correctly.

Start time : 29/10/2026 05:15 UTC End time : 29/10/2026 12:20 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 Network offering, which is causing temporary latency issue in the EU region.

Here are some supplementary details :

Start time : 29/10/2026 05:15 UTC Impacted Service(s) : vRack issue on EU region Customers Impact : Customers may experienced some issue to create instance with vRack port, management tasks carried out via vRack may be affected. 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 Network offer.

Start time : 29/10/2026 10: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 Public Cloud Volume (Ceph) offering has been resolved.

Start time : 27/10/2026 00:00 UTC End time : 27/10/2026 16:30 UTC Root Cause : This incident was caused by a software issue.

We apologize for any inconvenience caused and appreciate your understanding.

Monitoring: We would like to inform you that our service has been fully restored as of 27/10/2026 16:16 UTC. Monitoring is still in place to ensure long-term stability.

Please find the details of this incident below :

Start time : 27/10/2026 00:00 UTC Impacted Service(s) : Some volumes experienced degraded performance in the EU-WEST-PAR-A zone. Customers Impact : Customers may have experienced high latency on their volumes. Volumes remained available throughout the incident. 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 incident affecting our Public Cloud Volume (Ceph) offering in the EU-WEST-PAR-A zone. The root cause has been identified.

Please find the details of this incident below :

Start time : 27/10/2026 00:00 UTC Impacted Service(s) : Some volumes are experiencing degraded performance in the specified zone. Customers Impact : Customers may experience high latency on their volumes. Volumes remain available. Root Cause : This incident is caused by a software issue. Ongoing Actions : Our teams are actively working 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 Storage offering, which is causing temporary latency issue in our Public Cloud Volume (Ceph) offering in the EU-WEST-PAR-A zone.

Here are some supplementary details :

Start time : 27/10/2026 00:00 UTC Impacted Service(s) : Some Volumes experience degraded performance in the specified zone. Customers Impact : Customers may have latencies and degradation on their Volumes. Ongoing Actions : Customers may experience high latency on their volumes. Volumes remained available throughout

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.