Is Outsystems down?

We have identified the cause of an issue affecting the Count parameter in advanced SQL queries. Customers may experience a runtime error (OS-BERT-60409 – Could not calculate the query count) and application crashes when using the Count parameter in advanced SQL queries. Additionally, we strongly recommend avoiding any redeployment or republishing of applications that use Advanced SQL in production until the issue is resolved, to prevent any potential unexpected behavior. Our team is actively working on a solution, and we will provide an update as soon as more details are available.

We have identified the cause of the issue affecting ODC and a fix is currently being deployed. Users may continue to experience symptoms while the update is being implemented. We are monitoring the progress closely and aim to have the issue fully resolved by 00:00 UTC on May 23rd.

We continue to deploy the fix for the issue affecting ODC and are seeing progress across the impacted services. Due to additional time required to complete the rollout safely and validate platform stability, the estimated resolution time has been updated to 07:00 UTC on May 23rd. Users may continue to experience intermittent symptoms while deployment activities are ongoing. We are closely monitoring the situation and will provide further updates as progress continues.

We continue to make progress on the deployment of the fix affecting ODC services. During the final stages of the rollout and validation process, additional time was required before pipelines could be safely unfrozen and normal operations resumed. The updated estimated resolution time is now 11:00 UTC on May 25th. Users may continue to experience intermittent symptoms while mitigation and validation activities remain in progress. We are actively monitoring the situation and will continue to provide updates as additional information becomes available.

A solution has been applied to resolve this issue. A republish of the application is required to fully apply the fix. We will continue monitoring this situation to ensure full recovery.

This incident has been fully resolved, and the Count parameter in advanced SQL queries is now operating as expected. To ensure you benefit from this fix, please make sure you republish the affected application and deploy it to the affected stage if necessary. Thank you for your patience and understanding while we worked to resolve this matter.

On May 22, 2026, we deployed an update intended to improve internal diagnostics. This update added automatic comments to generated SQL statements. In a specific edge case, where count-based queries were used inside nested SQL statements, these added comments disrupted the structure of the query and caused it to fail. Affected applications returned runtime errors and certain database queries could not complete successfully. After deploying a fix for this, services were restored and all affected queries are now functioning normally. We appreciate your patience while this was being resolved and remain committed to continuously improving the stability and reliability of the platform.

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.

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.

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.

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.

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.

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.

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.

We are experiencing some partial infrastructure outage which is causing connection issues with some of our online tools. We will update you as soon as we have the website up and running.

We are continuing to investigate this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are investigating an issue where users are unable to log into the ODC Portal. This issue is also impacting some functionality within ODC Studio. Affected users may encounter an error message stating they do not have the necessary permissions to see the content or that they cannot access the page. This incident is currently confirmed to be affecting all regions. We are working to identify the cause and will provide further updates as they become available.

The cause of this incident has been found. A new deployment of the Identity Services relied on a database schema that had not yet been updated, resulting in service unavailability and authentication failures, affecting all ODC regions. A solution has been applied by rolling back the deployment. The incident is now resolved, and services are operating as expected. We have confirmed that user applications were not affected during this time.

On April 13,2026 between 1:13 and 3:07 AM UTC, an incident occurred that prevented users from logging in to the ODC Portal across multiple regions. The issue was caused by a deployment of a Identity Service that required a database schema change that had not yet been applied, resulting in authentication failures. Service was restored after the team initiated a rollback to the previous stable version. Validation confirmed that login functionality was restored for all users. The incident is fully resolved, and all services are operating as expected.

We are experiencing some partial infrastructure outage which is causing connection issues with some of our online tools. We will update you as soon as we have the website up and running.

A fix has been implemented and we are monitoring the results.

The issues affecting our services have been resolved, and all systems are now operating normally. We apologize for any disruption this may have caused to your workflows.