[LIM1][Compute - Instance] - Cloud Compute Incident Notification

Update timeline

1. identified May 02, 2026, 12:25 PM UTC

   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 : 02/05/2026 12:18 UTC Impacted Service(s) : Some instances in the LIM1 region are unreachable. Customers Impact : Customers are temporarily unable to access instances located on the specified regions. 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.

2. identified May 02, 2026, 04:24 PM UTC

   We are continuing to work on a fix for this issue.

3. identified May 02, 2026, 04:43 PM UTC

   We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : Most instances are now operational again. Ongoing Actions : Our team is working to fix the last remaining instances. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

4. identified May 03, 2026, 03:08 AM UTC

   We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : The remaining instances are still being worked on by our teams. 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.

5. resolved May 03, 2026, 08:13 PM UTC

   We are pleased to inform you that the incident affecting our Compute - Instance offering in LIM1 has been resolved. Start time : 02/05/2026 12:18 UTC End time : 03/05/2026 19:58 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.