Incident affecting Personal Environments for O11 and ODC

Incident Report for OutSystems

Postmortem

On May 8, 2026, at 12:03 AM UTC, ODC and O11 Personal Environments in the N. Virginia region experienced a service disruption caused by an AWS infrastructure event affecting a single Availability Zone. The disruption was related to an external power and cooling issue that impacted the availability of underlying AWS services.
Customers experienced service unavailability, including issues with logging in and publishing applications.The impact was limited to O11 Personal Environments and a small subset of users, while impact on ODC remained contained.
As AWS services recovered, many OutSystems environments resumed normal operation automatically. Some environments required additional recovery actions to fully restore service availability.
For ODC, the incident was fully resolved on May 9, 2026, at 3:30 AM UTC. Recovery efforts for O11 Personal Environments continued afterward due to the additional complexity of restoring affected environments.
All services are now operating as expected, and no user action is required.

Posted May 13, 2026 - 16:11 UTC

Resolved

This incident has been fully resolved, and Personal Environments in the N. Virginia region for O11 and ODC are now operating as expected. Thank you for your patience.

Posted May 11, 2026 - 16:12 UTC

Update

Based on official feedback from AWS as of May 8th, the core issue impacting ODC is mitigated and the service is now operating normally.

For O11 Personal Environments, while the primary issue is resolved, some customers might still face 504 errors or access issues. A small number of instances remain impaired and AWS continues to work to recover all affected remaining resources. We will continue to closely monitor the situation and we will provide further updates when available.

Posted May 11, 2026 - 07:29 UTC

Update

We have now confirmation from AWS that access is now being restored on the affected environments. We suggest that customers can start testing on their end. Some customers might still face 504 errors or access issues. We continue to closely monitor the situation and we will provide further updates when available.

Posted May 09, 2026 - 12:23 UTC

Update

We have identified the root cause of the issue as a hardware failure within the AWS US East (N. Virginia) datacenter. We are actively deploying mitigations and closely monitoring AWS's recovery progress, which is expected to take several hours. Users may continue to experience symptoms while these fixes are being fully implemented.

Posted May 08, 2026 - 23:19 UTC

Monitoring

We can now confirm that impact should only be perceived on O11 Personal Environments. AWS was able to identify that the issue was caused by a thermal event. Recovery might take several hours. We will continue to investigate this issue and closely monitoring the developments on the AWS investigations.

Posted May 08, 2026 - 16:30 UTC

Identified

We are currently investigating an issue affecting O11 Personal Environments and ODC in the N. Virginia region. Customers may experience a variety of symptoms, most notably service unavailability for O11 and login/publishing issues for ODC. The cause has been identified to an issue in the AWS datacenter. We will provide an update as soon as more details are available.

Posted May 08, 2026 - 11:56 UTC

This incident affected: OutSystems Personal Edition (Customer Apps & Data, Platform and Portal).