Outsystems Outage History

Started May 22, 2026, 02:58 PM UTC· resolved May 25, 2026, 01:37 PM UTC

1. identified May 22, 2026, 02:58 PM UTC

   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.

2. identified May 22, 2026, 06:58 PM UTC

   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.

3. identified May 22, 2026, 11:31 PM UTC

   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.

4. identified May 23, 2026, 08:07 AM UTC

   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.

5. monitoring May 25, 2026, 08:28 AM UTC

   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.

6. resolved May 25, 2026, 01:37 PM UTC

   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.

7. postmortem May 26, 2026, 04:18 PM UTC

   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.

Read the full incident report →

Started May 08, 2026, 11:56 AM UTC· resolved May 11, 2026, 04:12 PM UTC

1. identified May 08, 2026, 11:56 AM UTC

   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.

2. monitoring May 08, 2026, 04:30 PM UTC

   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.

3. monitoring May 08, 2026, 11:19 PM UTC

   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.

4. monitoring May 09, 2026, 12:23 PM UTC

   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.

5. monitoring May 11, 2026, 07:29 AM UTC

   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.

6. resolved May 11, 2026, 04:12 PM UTC

   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.

7. postmortem May 13, 2026, 04:08 PM UTC

   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.

Read the full incident report →

Started Apr 13, 2026, 02:24 AM UTC· resolved Apr 13, 2026, 03:30 AM UTC

1. investigating Apr 13, 2026, 02:24 AM UTC

   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.

2. resolved Apr 13, 2026, 03:30 AM UTC

   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.

3. postmortem Apr 13, 2026, 07:17 AM UTC

   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.

Read the full incident report →

Started Mar 19, 2026, 09:35 AM UTC· resolved Mar 19, 2026, 11:32 AM UTC

1. investigating Mar 19, 2026, 09:35 AM UTC

   We are currently investigating an issue affecting ODC. Users may experience errors when attempting to log into the ODC Portal and ODC Studio if they use External Identity Provider. Affected users are encountering the error message: "Email verification not supported / Email verification is not supported in the current Identity Provider. (OS-ID-BIZ-40302)". The current workaround is to reactivate the built-in identity provider. Please contact Support if you want to implement this option. Our team is actively working to identify the cause and restore full functionality.

2. investigating Mar 19, 2026, 09:46 AM UTC

   We are continuing to investigate this issue.

3. investigating Mar 19, 2026, 11:09 AM UTC

   A solution has been applied by rolling back a recent deployment of Identity Services, and our logs indicate that the errors have ceased. We are still investigating the root cause of this issue.

4. resolved Mar 19, 2026, 11:32 AM UTC

   The incident is now resolved and login to ODC Portal and ODC Studio is operating as expected. The issue, which prevented a subset of users from logging in, was caused by a change intended to strengthen the email verification process. We have resolved the situation by rolling back to a previous version of the services and will perform a root cause analysis to prevent a recurrence in future releases.

5. postmortem Mar 23, 2026, 01:46 PM UTC

   On March 19th, 2026, at approximately 06:43 UTC, an issue was identified affecting ODC, where some users were unable to complete the login process for the ODC Portal and ODC Studio when using external Identity Providers. Affected users encountered an error message stating "Email verification not supported" or were blocked from accessing their accounts because the system could not verify their email addresses via the external provider's claims. The incident was caused by a configuration change intended to strictly enforce email verification from external providers. This change inadvertently bypassed a native fallback verification process that certain users relied upon when their external providers did not share specific verification data. The issue was resolved by 11:00 UTC on March 19th following a rollback to the previous service versions. To prevent recurrence, future updates to this functionality will be implemented via a gradual rollout plan, including additional validation steps to ensure all identity provider configurations are fully supported.

Read the full incident report →

Started Mar 04, 2026, 09:09 AM UTC· resolved Mar 04, 2026, 10:41 AM UTC

1. investigating Mar 04, 2026, 09:09 AM UTC

   We are investigating an issue where users are experiencing errors when attempting to view application details within the ODC Portal. Specifically, users may encounter error code OS-CFGM-40060 during this process. Due to this behavior, users are unable to view or modify application configurations, which may prevent necessary updates or fixes to their applications. Our team is working to identify the cause and will provide further updates as they become available.

2. identified Mar 04, 2026, 09:39 AM UTC

   We have identified the cause of the issue affecting the viewing of application details. A recent configuration update created a validation mismatch between the ODC Portal and the underlying service. We are now working to revert this change to restore normal functionality. While we apply this fix, users may still encounter error OS-CFGM-40060 when accessing the View App detail page. We will provide further updates as the resolution progresses.

3. resolved Mar 04, 2026, 10:41 AM UTC

   This incident has been fully resolved and application access in ODC Portal is now operating as expected. Thank you for your patience.

4. postmortem Mar 10, 2026, 11:01 AM UTC

   On March 4th, 2026, between 2:39 am and 10:29 am UTC, ODC experienced an incident that prevented users from accessing the App Detail screen and performing app configurations across all stages. The runtime of existing applications was not affected by this issue. The root cause was a subscription validation misalignment between internal APIs and ODC Portal, which resulted in errors for customers without the ODC Sentry add-on. To prevent future occurrences, we are updating ODC Portal to verify subscription status in alignment with these APIs and improving UI error handling to ensure failures like this do not obstruct the overall page experience.

Read the full incident report →

Started Mar 01, 2026, 04:33 PM UTC· resolved Jul 03, 2026, 02:41 PM UTC

1. investigating Mar 01, 2026, 04:33 PM UTC

   We are currently experiencing service degradation in the Middle East (UAE) region due to connectivity and power issues within a major cloud provider (AWS). We are actively monitoring the situation and following updates from the official AWS status page. Our team is closely tracking recovery progress. We will provide further updates as more information becomes available.

2. identified Mar 01, 2026, 06:43 PM UTC

   AWS Team has identified the cause of the disruption affecting one availability zone in the Middle East (UAE) region. Power was temporarily shut down at the facility as a safety precaution. Restoration of power and connectivity may take several hours. Other availability zones in the region remain operational. We will provide further updates as more information becomes available.

3. identified Mar 01, 2026, 08:32 PM UTC

   We are continuing to monitor the official AWS status page. At this time, AWS has informed customers that some may experience errors when performing certain network-related actions. AWS is actively implementing mitigation measures, and recovery is expected within the next few hours.

4. monitoring Mar 01, 2026, 09:43 PM UTC

   Our services have been fully restored, and the issue affecting our OutSystems customers has been mitigated. While the ongoing disruption reported by AWS continues, it is not expected to impact our customers at this time. We will continue to closely monitor the situation. If you experience any issues, please contact our Support team. For updates directly from AWS, please visit: https://health.aws.amazon.com/health/status

5. investigating Mar 02, 2026, 08:59 AM UTC

   We are currently investigating this issue.

6. investigating Mar 02, 2026, 09:31 AM UTC

   We are investigating an issue affecting Outsystems Products in the Middle East (UAE) region. This disruption is related to the ongoing AWS service incident reported on March 1st. Users in this region are currently experiencing a total service outage in ODC, and all services are unavailable. We are monitoring the situation closely and will provide updates as more information becomes available.

7. investigating Mar 02, 2026, 03:12 PM UTC

   We continue to follow closely the investigation in partnership with AWS, towards the recovery of the Middle East (UAE) Region. At this point, we are expecting recovery to take at least a day given the significant efforts required. Until then, ODC and other services in this region will continue experiencing a total service outage. We continue to monitor the situation closely and will provide updates as more information becomes available.

8. investigating Mar 03, 2026, 08:50 AM UTC

   We are still continuing to monitor the investigation with AWS, as the recovery towards the impaired AWS Middle East (UAE) Region is still ongoing. While there have been significant improvements made so far, the estimated recovery time will take at least another day before power and connectivity can be restored.

9. identified Mar 03, 2026, 05:10 PM UTC

   The cause has been identified as a widespread infrastructure failure in the Middle East (UAE) affecting foundational AWS services. While recovery efforts are underway, ODC and other services in this region will remain unavailable until the underlying infrastructure is fully restored. We are closely monitoring the situation as it recovers and will provide further information once it becomes available.

10. identified Mar 04, 2026, 07:08 AM UTC

    Recovery efforts are still being prioritized by AWS for this region, focusing on restoration of the impacted AWS Services. We are closely monitoring the situation and will provide further updates once they become available.

11. monitoring Mar 04, 2026, 04:03 PM UTC

    Update - We are continuing to monitor the progress of recovery efforts in the affected region. We will provide further information as soon as more details become available.

12. identified Mar 04, 2026, 05:48 PM UTC

    Update - We are continuing to monitor the progress of recovery efforts in the affected region. We will provide further information as soon as more details become available.

13. identified Mar 06, 2026, 01:14 PM UTC

    We are continuing to monitor the recovery of ODC services in the Middle East (UAE) as the underlying infrastructure issues are being addressed. We will provide further updates as soon as more information becomes available.

14. identified Mar 09, 2026, 11:34 AM UTC

    Recovery efforts are still underway for the Middle East (UAE) as cloud services work to restore one of the affected areas. We are continuing to track the progress and will provide further updates as more information becomes available.

15. identified Mar 10, 2026, 02:36 PM UTC

    Recovery efforts for the Middle East (UAE) region remain ongoing as cloud infrastructure providers work to restore impacted services. We continue to track the recovery progress and will provide further updates as more information becomes available.

16. identified Mar 11, 2026, 05:11 PM UTC

    Recovery efforts for the Middle East (UAE) remain ongoing as cloud infrastructure providers work to restore impacted services. ODC organizations remain unavailable while these restoration efforts continue. We are closely tracking the progress and will provide further updates as more information becomes available.

17. identified Mar 13, 2026, 05:00 PM UTC

    Recovery efforts for the Middle East (UAE) remain ongoing as cloud infrastructure providers work to restore impacted services. ODC organizations remain unavailable while these restoration efforts continue. We are continuing tracking the recovery process of this incident to ensure a complete recovery. Going forward, updates will be delivered directly to affected users through their individual support tickets. Users who require further assistance with this event are encouraged to contact OutSystems Support by raising a new ticket or following their existing cases through the Support Portal.

18. identified Mar 24, 2026, 08:20 AM UTC

    We are investigating reports of service disruption affecting O11 Cloud customer in the Middle East (Bahrain) region. We are currently reaching out to impacted customers directly and will provide further updates as more information becomes available.

19. identified Apr 06, 2026, 11:51 AM UTC

    Most affected O11 Cloud customers in the Middle East (Bahrain) region have been mitigated, and overall stability has improved. The AWS outage remains ongoing. We are continuing to actively monitor AWS updates to ensure full service recovery. Further updates will be provided directly to affected users via their individual support tickets. Customers requiring additional assistance are encouraged to contact OutSystems Support by raising a new ticket or following their existing cases through the Support Portal.

20. resolved Jul 03, 2026, 02:41 PM UTC

    All customers impacted by this incident have been contacted and supported individually. While the Middle East region continues to be affected by the ongoing geopolitical situation and AWS continues to report the region as impacted, OutSystems has completed its direct response to every affected organization. The affected services remain flagged as a major outage while these conditions persist. Customers who need further assistance can contact OutSystems Support by raising a new ticket or continuing their existing case through Support Services.

Read the full incident report →

Started Jan 29, 2026, 08:00 PM UTC· resolved Jan 30, 2026, 12:43 PM UTC

1. investigating Jan 29, 2026, 08:00 PM UTC

   We are investigating an issue in ODC affecting users in Europe (Frankfurt), Europe (London), and Israel (Central). Affected users may experience login failures when attempting to access their applications. Our team is currently working to address the situation.

2. investigating Jan 30, 2026, 01:28 AM UTC

   We have confirmed that no additional users are being impacted at this time. Our team is continuing to investigate the situation to determine the full scope and cause.

3. investigating Jan 30, 2026, 10:05 AM UTC

   We are continuing to investigate this incident. Our technical teams are actively working to identify the root cause, and we will provide further information as soon as it becomes available. We appreciate your patience as we work toward a resolution.

4. identified Jan 30, 2026, 12:21 PM UTC

   The cause of this issue has been identified and our team is currently working on a resolution. Users may continue to experience login failures while our team works on developing a fix.

5. resolved Jan 30, 2026, 12:43 PM UTC

   This incident has been fully resolved and the applications login is now operating as expected. Thank you for your patience.

6. postmortem Feb 06, 2026, 02:39 PM UTC

   On January 30th, several ODC customers experienced intermittent issues where the username attribute was missing data from the User entity within applications. The cause was identified as a bug in a recent release of an identity component. This issue prevented specific user and identity provider data from correctly populating the Username Attribute. The incident was resolved by rolling back the affected release. A corrected version has since been deployed to ensure consistent data availability and prevent future occurrences.

Read the full incident report →

Started Jan 27, 2026, 12:53 PM UTC· resolved Jan 27, 2026, 06:20 PM UTC

1. investigating Jan 27, 2026, 12:53 PM UTC

   We are currently investigating an issue where Mentor is unavailable for users in Asia Pacific (Singapore) and Europe (Frankfurt). This disruption is due to an underlying service outage with an external provider and may also impact users in other regions that rely on these services. Our team is actively working to address the situation.

2. investigating Jan 27, 2026, 01:23 PM UTC

   As per additional investigation from our team, we detected that Mentor is unavailable for users in EMEA and APAC-based regions. We are continuing to investigate this issue.

3. investigating Jan 27, 2026, 02:53 PM UTC

   We continue to investigate Mentor's unavailability for users in EMEA and APAC-based regions. We will provide an update as soon as more details are available.

4. investigating Jan 27, 2026, 03:22 PM UTC

   While we await updates from our infrastructure provider, our teams are actively developing a fallback plan to mitigate the impact, through a non-affected region to restore functionality.

5. resolved Jan 27, 2026, 06:20 PM UTC

   The incident affecting the ODC Mentor has been resolved, and all services are now operating normally. On January 27th, ODC Mentor experienced a service disruption. This was caused by an outage with an external cloud provider. We mitigated the impact by implementing infrastructure changes to bypass the affected provider services.

6. postmortem Jan 30, 2026, 09:03 AM UTC

   On January 27th, we experienced a service disruption in Mentor affecting APAC and EMEA regions. Users encountered elevated error rates and a loss of functionality for Mentor features. The incident was triggered by a third-party service outage, which hosts the models supporting our Data & AI services. While a fallback system was in place, it also became unavailable during the outage. Furthermore, the impact of the external service disruption also prevented our team from implementing a manual configuration fix immediately. We are also working toward an automated fallback mechanism to minimize the need for manual intervention. Additionally, we are implementing agent-level fallbacks to different models at the product level.

Read the full incident report →

Started Jan 22, 2026, 03:29 PM UTC· resolved Jan 22, 2026, 04:52 PM UTC

1. investigating Jan 22, 2026, 03:29 PM UTC

   We are aware of an issue affecting 1-Click Publish feature in Europe Central region (Frankfurt). Customers in this region may experience a build timeout in publish operations. Our team is currently investigating its cause. We will provide an update as soon as more details are available

2. monitoring Jan 22, 2026, 04:19 PM UTC

   A solution has been applied to resolve this issue. We are now monitoring to ensure full recovery.

3. resolved Jan 22, 2026, 04:52 PM UTC

   This incident has been fully resolved and the 1-Click Publish feature is now operating as expected. Thank you for your patience.

4. postmortem Jan 27, 2026, 11:30 AM UTC

   On January 22nd, between 15:00 UTC and 17:00 UTC, an incident affected ODC in the Europe \(Frankfurt\) region. Users experienced issues with One-Click Publish, specifically resulting in build timeouts and publish failures. The issue was caused by a communication failure between the internal queuing system and the Build Service, which prevented build processes from completing. Our team resolved the incident by restarting the Build Service and restoring communication. Normal service has been restored, and we are evaluating measures to improve system resilience moving forward.

Read the full incident report →

Started Jan 16, 2026, 10:13 AM UTC· resolved Jan 16, 2026, 02:35 PM UTC

1. investigating Jan 16, 2026, 10:13 AM UTC

   We are aware of an issue where customers are unable to log into applications. Customers may encounter an “invalid redirect URI” error when attempting to log in to an application using a newly configured custom domain. Our team is currently investigating the cause of this issue and will provide updates as more information becomes available.

2. identified Jan 16, 2026, 11:46 AM UTC

   The cause of the issue has been identified, and a solution is being applied. Customers may still experience an “invalid redirect URI” error when attempting to log in to an application using a newly configured custom domain. Our team is actively working on the solution. We will provide an update once more details are available.

3. monitoring Jan 16, 2026, 12:37 PM UTC

   A solution has been applied to resolve the issue. Customers who are still experiencing problems with newly configured custom domains should follow these steps: 1. Delete the affected custom domain in the ODC Portal. 2. Remove the corresponding CNAME entries from your DNS provider and wait ~5 minutes. 3. Recreate the custom domain in ODC Portal and add the new CNAME records. 4. Once the status shows Active, try logging in again. If you continue to experience issues after following these steps, please contact us via Support Portal. We will continue monitoring the situation to ensure full recovery and will provide updates if any further action is required.

4. resolved Jan 16, 2026, 02:35 PM UTC

   This incident is now fully resolved. If you continue to experience issues, please follow the steps shared in our previous communication. Thank you for your patience and understanding.

5. postmortem Jan 27, 2026, 11:43 AM UTC

   On January 16th, a service change related to an ongoing migration caused a temporary issue where customers were unable to log in using their custom domains. Our engineering team immediately identified the cause and implemented a mitigation to resolve the issue quickly by temporarily disabling the custom domain redirection feature. A controlled restart of system deployments was performed to expedite this fix. To ensure stability and prevent recurrence, a technical recommendation has been made to enhance the system. This improvement will increase resilience to future updates and configuration changes, helping maintain continuous operation without service interruptions.

Read the full incident report →

Started Dec 08, 2025, 01:36 PM UTC· resolved Dec 08, 2025, 03:46 PM UTC

1. investigating Dec 08, 2025, 01:36 PM UTC

   We are aware that the issue affecting application deployments continues for deployments to stages other than Development. Customers may experience failed application deployments when deploying to these stages. Our team is currently investigating its cause. We will provide an update as soon as more details are available.

2. resolved Dec 08, 2025, 03:46 PM UTC

   This incident has been fully resolved, and Application Publishing is now operating as expected. Thank you for your patience.

3. postmortem Dec 11, 2025, 04:46 PM UTC

   On December 8th, we experienced an issue affecting application deployments, resulting in application promotion failures to test and production stages. The incident was caused by an issue related to connection limits on an internal message mechanism. A high volume of retries from a specific Data Services Execution Job, which lacked retry limits, escalated the problem into a connection exhaustion situation. To resolve the issue, a configuration change was implemented to increase the connection limit on the internal message mechanism, and deployments recovered quickly thereafter. To prevent new occurrences, we are creating an action item to limit retries on the offending job to mitigate future connection escalations.

Read the full incident report →

Started Dec 08, 2025, 10:15 AM UTC· resolved Dec 08, 2025, 11:12 AM UTC

1. investigating Dec 08, 2025, 10:15 AM UTC

   We are aware of an issue impacting the 1-Click Publish (1CP) functionality. Customers may be experiencing error "OS-DPL-40802". This issue is affecting our customers in all regions. Our team is currently investigating the cause. We will provide an update as soon as more details are available.

2. resolved Dec 08, 2025, 11:12 AM UTC

   This incident has been fully resolved and application deployments are now operating as expected. Our team will continue to investigate the root cause. Thank you for your patience.

3. postmortem Dec 11, 2025, 04:25 PM UTC

   On December 8th, we experienced an issue that affected application publishing. This resulted in users being unable to publish any applications in the Development stage across all regions, encountering the error code OS-DPL-40802 \(Deployment timeout\). The root cause of the incident was a new version of an internal service that was deployed around the same time the problem started. This new version contained changes that caused application deployments to fail. The issue was resolved by reverting the internal service to the previous stable version.

Read the full incident report →

Started Nov 26, 2025, 10:07 AM UTC· resolved Nov 26, 2025, 09:01 PM UTC

1. investigating Nov 26, 2025, 11:19 AM UTC

   We are currently investigating an issue affecting a subset of Personal Edition users. Some users are seeing a “no permissions” message after signing in. Our team is actively working to identify the cause, apply mitigation for impacted users, and continue monitoring the situation closely. We will share an update as soon as more information becomes available.

2. identified Nov 26, 2025, 02:43 PM UTC

   We have identified the root cause of the issue affecting Post-Login Permissions for Personal Edition users. Some customers may still experience a “no permissions” message after signing in. Our team is actively working on a solution, and we will provide an update as soon as more details are available

3. resolved Nov 26, 2025, 09:01 PM UTC

   We have successfully applied a manual fix for the Personal Edition users who reported the “no permissions” error; access for these accounts has been restored. Regarding other affected users who did not submit a report, we have sent a dedicated communication to your registered email address with further details. We will continue to monitor the system to ensure stability.

4. postmortem Dec 10, 2025, 11:17 AM UTC

   On November 26th, an issue was experienced affecting Personal Editions users, resulting in users seeing a “no permissions” page and being unable to use their Personal Edition environments. Normal service was restored at 21:00 UTC. The incident was caused by the reconfiguration step used to fix an earlier issue. This step correctly re-applied the Identity Provider \(IdP\) but also unintentionally made the affected Personal Editions environments available for re-assignment. As a result, many of the previously fixed Personal Editions were re-assigned to "second" users who were created without any permissions upon first login, leading to the “no permissions” screen. To prevent new occurrences, all Personal Editions environments created during the faulty period that had gone through the reconfiguration were discarded. Impacted users were proactively informed and instructed to request a new Personal Edition.

Read the full incident report →

Started Nov 25, 2025, 12:37 PM UTC· resolved Nov 25, 2025, 05:06 PM UTC

1. identified Nov 25, 2025, 12:37 PM UTC

   We are currently investigating an issue preventing some ODC Personal Edition users from logging in. Affected users may see the error message “Incorrect username or password (OS-UAUC-60004)” even when using their correct community credentials. Our team is actively working to identify the cause. We will share an update as soon as more information becomes available.

2. resolved Nov 25, 2025, 05:06 PM UTC

   We experienced an issue that prevented some users from logging in to their Personal Editions across multiple regions. This affected tenants created between November 17 and 18 and assigned on November 22. The problem was caused by an incomplete internal configuration during setup, which blocked the login process. Our team has corrected the configuration for all affected tenants, and access has now been fully restored. Thank you for your patience while we resolved this issue.

3. postmortem Dec 10, 2025, 11:11 AM UTC

   On November 25th, around 11:15 UTC, we experienced an issue affecting Personal Editions, resulting in users being unable to log in and consistently seeing the error “Incorrect username or password \(OS-UAUC-60004\)” despite using valid credentials in the regions of US East \(Ohio\), Europe \(Ireland\), and Asia Pacific \(Singapore\). Normal service was restored by approximately 17:00 UTC the same day. The incident was caused by an issue in provisioning that led Personal Editions to not have the built-in community provider configured as an Identity Provider. This resulted in the login failures when users attempted to access their Personal Editions. To prevent new occurrences, the provisioning logic was updated to treat a similar empty response as an error, triggering an internal alert and preventing affected environments from being handed out as ready-to-use. Additionally, a targeted reconfiguration job was run to correctly apply the required identity provider to all impacted Personal Editions, which restored normal login functionality

Read the full incident report →

Started Nov 24, 2025, 11:46 AM UTC· resolved Nov 24, 2025, 12:09 PM UTC

1. identified Nov 24, 2025, 11:46 AM UTC

   We are aware of an issue where deploying an app with an external library to other stages results in a timeout. Our team is currently investigating the cause. We will provide an update as soon as more details are available.

2. resolved Nov 24, 2025, 12:09 PM UTC

   This incident has been fully resolved, and the Publish/Promote of External Libraries is now fully operating as expected. Thank you for your patience.

3. postmortem Dec 03, 2025, 03:18 PM UTC

   On November 24, 2025, a new version of our deployment service was released, including an internal library update intended to optimize the processing of external libraries. This update inadvertently caused a logic error that made deployments hang during certain operations, leading to intermittent timeouts for customers deploying external libraries or applications that depend on them. Not all deployments were affected, and the impact varied by region and library volume. We immediately reverted the service to the previous stable version, restoring normal deployment operations. We are working to correct the issue in the internal library and will reintroduce the optimization after thorough validation to prevent future disruptions. We apologize for the inconvenience and appreciate your patience.

Read the full incident report →

Started Nov 18, 2025, 09:56 AM UTC· resolved Nov 18, 2025, 11:28 AM UTC

1. investigating Nov 18, 2025, 09:56 AM UTC

   We are aware of an issue affecting ODC Personal Edition access globally. Users may experience login issues on their Personal Editions. Our team is actively investigating the cause. We will provide an update as soon as more details are available.

2. identified Nov 18, 2025, 10:45 AM UTC

   We have identified the cause of this issue. Customers may still experience login issues on their Personal Editions. Our team is actively working on a solution. We will provide an update once more details are available.

3. resolved Nov 18, 2025, 11:28 AM UTC

   This incident has been fully resolved and the login on Personal Edition is now operating as expected. Thank you for your patience.

4. postmortem Nov 20, 2025, 04:20 PM UTC

   On November 18th, we experienced an issue that prevented users with Personal Editions from accessing the ODC Portal login page. Customers who were affected saw the error message: "Something unexpected happened during login. Please try logging in again using a new tab or a different browser". Normal service was restored at 11:09 AM UTC. The incident was caused by a recent system update that introduced an error in how login data was processed. Full access was restored after we reverted the affected system component to its previous version. We apologize for the inconvenience this caused.

Read the full incident report →

Started Nov 14, 2025, 02:26 PM UTC· resolved Nov 17, 2025, 05:45 PM UTC

1. investigating Nov 14, 2025, 02:26 PM UTC

   We are aware of an issue concerning LogMessage entries not appearing in the ODC Portal when executed inside timers. This is affecting Europe (Frankfurt) and Asia Pacific (Tokyo) regions. Our team is currently investigating its cause. We will provide an update as soon as more details are available.

2. identified Nov 14, 2025, 02:44 PM UTC

   We have identified the cause of this issue. Our team is actively working on implementing a solution and we will provide an update once more details are available.

3. monitoring Nov 14, 2025, 04:54 PM UTC

   We have identified the cause of the issue. The fix is now in deployment, and a full resolution is expected by Tuesday, November 18th. We will continue monitoring this situation to ensure full recovery.

4. resolved Nov 17, 2025, 05:45 PM UTC

   We have successfully deployed a fix for the LogMessage issue that affected timers in the Europe (Frankfurt) and Asia Pacific (Tokyo) regions. Our monitoring confirms that the issue is fully resolved and all services are operating normally. Thank you for your patience.

5. postmortem Nov 19, 2025, 09:04 AM UTC

   A platform-wide issue was identified where log messages generated within successful Timers were inconsistently or completely missing from the monitoring interface. The root cause was a technical race condition during a critical component startup, which prevented logs from reaching the central logging system. Engineering team developed and deployed an update that resolved the issue, and extensive monitoring has confirmed the platform is now stable, with all Timer-originated log entries appearing correctly.

Read the full incident report →

Started Nov 11, 2025, 09:36 AM UTC· resolved Nov 11, 2025, 10:50 AM UTC

1. investigating Nov 11, 2025, 09:36 AM UTC

   We are aware of an issue in Europe (Frankfurt) region that is affecting core functionalities in ODC, including timers, deployments to production, and login processes. Our team is currently investigating its cause. We will provide an update as soon as more details are available.

2. identified Nov 11, 2025, 09:59 AM UTC

   We have identified the cause of this issue. Our team is actively working on a solution and we will provide an update once more details are available.

3. monitoring Nov 11, 2025, 10:28 AM UTC

   A fix has been implemented and our team is currently monitoring the results.

4. resolved Nov 11, 2025, 10:50 AM UTC

   The issue affecting multiple ODC functionalities in Europe (Frankfurt) region has been resolved and services are now operating as expected. Thank you for your patience.

5. postmortem Nov 13, 2025, 12:21 PM UTC

   Customers experienced intermittent service issues with core operations, including deployments and authentication, between 2:58 and 10:40 UTC. The disruption was caused by a core system component reaching its maximum connection limit. Our engineering team successfully identified the issue, implemented a configuration update to increase connection capacity, and fully restored service by 10:40 UTC. We are also conducting a full analysis to understand the unexpected usage increase and are enhancing our monitoring for earlier detection of similar events in the future. We apologize for the inconvenience this may have caused.

Read the full incident report →

Started Nov 10, 2025, 01:16 PM UTC· resolved Nov 10, 2025, 03:16 PM UTC

1. investigating Nov 10, 2025, 01:16 PM UTC

   We are aware of an issue regarding user authentication on the ODC platform, affecting Personal Edition. Users might experience HTTP: 401 error. Our team is currently investigating its cause. We will provide an update as soon as more details are available.

2. identified Nov 10, 2025, 01:28 PM UTC

   We have identified the cause of this issue. Our team is actively working on a solution. We will provide an update once more details are available.

3. resolved Nov 10, 2025, 03:16 PM UTC

   The issue affecting user authentication on the ODC platform, causing some users to encounter HTTP 401 errors, has been resolved. The service is now fully operational. Thank you for your patience.

4. postmortem Nov 19, 2025, 09:17 AM UTC

   On November 10th, a system optimization deployment led to a two-hour unavailability of core platform services due to a missing technical dependency. Although quickly resolved, the incident underscored the critical importance of strictly adhering to comprehensive quality assurance gates to ensure platform stability and prevent service disruption.

Read the full incident report →

Started Nov 06, 2025, 09:41 AM UTC· resolved Nov 07, 2025, 12:38 PM UTC

1. investigating Nov 06, 2025, 09:41 AM UTC

   We are aware of an issue affecting Timer logs in Asia Pacific (Singapore) and US East (N. Virginia). While the timers are running correctly, the logs may not be present. Our team is currently investigating its cause. We will provide an update in as soon as more details are available.

2. identified Nov 06, 2025, 05:30 PM UTC

   The support teams have identified factors contributing to the incomplete log data and are actively working on a fix. Monitoring and further analysis are ongoing, and updates will be provided as progress continues.

3. monitoring Nov 06, 2025, 07:59 PM UTC

   Upon investigation, our team has identified the root cause of the issue, and a fix is already being implemented. We will continue to monitor the situation closely and post a final update once we confirm that all services are operating normally.

4. resolved Nov 07, 2025, 12:38 PM UTC

   This incident has been fully resolved. Our teams identified an issue that was affecting timer logs. A fix was developed, tested, and successfully applied to all environments. Monitoring confirms that the issue is now fully resolved. Thank you for your patience and understanding.

5. postmortem Nov 10, 2025, 11:47 AM UTC

   On October 20, some customers noticed duplicate timer execution logs appearing in the console. A fix was implemented to address this issue. On November 3, another issue occurred in which parts of the timer log display were missing in the console. The investigation determined that the problem originated from a faulty service version introduced in a recent update. The affected version was identified and fixed. The issue was fully resolved on November 7 at 13:07 UTC, and normal log visibility is now available for all customers. We sincerely apologize for the inconvenience and appreciate your patience while we worked to restore full functionality.

Read the full incident report →

Started Oct 30, 2025, 08:46 PM UTC· resolved Oct 30, 2025, 09:24 PM UTC

1. investigating Oct 30, 2025, 08:46 PM UTC

   We are aware of an issue affecting the 1-Click Publish service in the eu-central-1 (Frankfurt) region. Customers performing application deployments may experience build timeouts or failures. Our team is currently investigating its cause. We will provide an update as soon as more details are available.

2. resolved Oct 30, 2025, 09:24 PM UTC

   We have confirmed that all services in the eu-central-1(Frankfurt) region are now fully operational. Our team applied a fix by restarting an underlying service, which has restored normal performance. We will continue to investigate the root cause to prevent a recurrence.

3. postmortem Nov 13, 2025, 03:47 PM UTC

   On October 30th, between 18:55 UTC and 21:22 UTC, customers experienced degraded success rates and timeouts when using the 1-Click Publish functionality. The issue, caused by an internal system component, was identified and resolved by our engineering team through a service restart, which immediately restored normal operation by 9:22 PM WET.

Read the full incident report →

Started Oct 29, 2025, 11:49 AM UTC· resolved Oct 29, 2025, 02:23 PM UTC

1. investigating Oct 29, 2025, 11:49 AM UTC

   We are aware of an issue affecting 1-Click-Publish. Personal Edition users may experience issues in publishing their apps. Our team is currently investigating its cause. We will provide an update in as soon as more details are available.

2. resolved Oct 29, 2025, 02:23 PM UTC

   This incident has been fully resolved. OutSystems Support identified that today, between 08:15 UTC and 11:30 UTC, some customers experienced service disruptions. The issue began around 08:15 UTC and recovery was observed by 11:30 UTC. Any remaining errors after that time were related to earlier requests made during the affected period. Our team determined that a system update deployed at 08:19 UTC was the likely cause of the disruption. The update was reverted at 11:41 UTC, after which services stabilised and have since been operating as expected. Thank you for your patience and understanding.

3. postmortem Nov 05, 2025, 08:24 AM UTC

   On October 29th, at approximately 08:15 AM UTC, we observed a significant drop in service success rate primarily affecting Personal Edition instances. Users may have experienced timeout errors. An immediate investigation traced the issue to a recent deployment. Reverting to the previous version resolved the problem, and all affected environments were restored to a healthy condition.

Read the full incident report →

Started Oct 20, 2025, 02:57 PM UTC· resolved Oct 20, 2025, 04:21 PM UTC

1. investigating Oct 20, 2025, 02:57 PM UTC

   We are investigating an issue affecting external authentication. Customers in US (Virginia) and Asia Pacific (Tokyo) regions may encounter errors or may not be redirected to the External IdP page to complete the authentication flow as expected. Our team is actively working on a solution and will provide an update as soon as more information becomes available.

2. resolved Oct 20, 2025, 04:21 PM UTC

   The fix has been deployed in all regions. Our team reverted the service version that was causing authentication errors, and the process was successfully completed across all regions. All services have been fully restored, and this incident is now resolved.

3. postmortem Oct 22, 2025, 07:31 AM UTC

   On October 20, some customers across all regions experienced issues logging in using external Identity Providers \(IdPs\), receiving an error or not being redirected to complete authentication. A temporary workaround was provided while the root cause, a faulty service version introduced in recent updates, was identified and reverted. The issue was fully resolved on October 20 at 18:15 UTC, restoring normal login functionality for all customers. The incident duration was extended due to an unrelated AWS outage that impacted service rollback times. We apologize for the inconvenience and appreciate your patience while we restored full functionality.

Read the full incident report →

Started Oct 20, 2025, 09:43 AM UTC· resolved Oct 20, 2025, 01:06 PM UTC

1. identified Oct 20, 2025, 09:43 AM UTC

   We want to report an issue affecting multiple SaaS platforms globally. This is related to AWS service disruption in one of its regions (N. Virginia). We are currently monitoring the official AWS status page. At this point, AWS is reporting significant signs of recovery. Most requests should now be succeeding.

2. identified Oct 20, 2025, 09:55 AM UTC

   We are continuing to monitoring the official AWS status page. At this point, AWS is reporting significant signs of recovery. Most requests should now be succeeding.

3. monitoring Oct 20, 2025, 10:34 AM UTC

   AWS Team has already identified a potential root cause and are observing recovery. During this time, requests may continue to fail as the team works towards full resolution. We will continue monitoring this situation to ensure full recovery.

4. monitoring Oct 20, 2025, 11:19 AM UTC

   We are continuing to monitor for any further issues.

5. resolved Oct 20, 2025, 01:06 PM UTC

   We are pleased to inform you that the issue has been resolved and the reported concerns from our customers earlier today have been successfully addressed.

6. postmortem Oct 23, 2025, 07:53 AM UTC

   On October 20th, our cloud service provider experienced a high error rate and latency in the N. Virginia Region, which temporarily affected some of our internal tools and caused service disruption for O11 and ODC customers. The issue was first reported at 08:37 UTC\+1 for ODC, affecting access to ODC Studio and running applications in ODC Portal. O11 had the first report at 08:54 UTC\+1. Cloud customers weren't able to access their Service Centers, IdP Authentication started to present some failures, CloudWatch started to fail, and several other symptoms were felt, since it affected several networking resources, including 503 error messages. Customers also experienced delays or interruptions using our services, including Forge, MABs, Licensing Registration, and accessing our Portals and telephony services. Our Support and Operations teams closely monitored the situation throughout the day, providing continuous updates to affected customers and coordinating internally to restore full functionality as quickly as possible. By 14:06 UTC\+1, it was reported that a full recovery of services had been achieved, and customers began confirming that their services were operating normally. However, later in the afternoon, around 16h32 UTC\+1, we started again receiving reports of connectivity issues, affecting O11 customers. During the recovery process, due to latency errors, several customers experienced network connectivity issues. Our teams continued providing updates and ensured all systems remained stable. AWS confirmed that all its services returned to normal operations by 23:01 UTC\+1. This disruption affected 142 AWS services, causing a direct impact on OutSystems services. They determined that the incident was caused by DNS resolution issues affecting DynamoDB. Following this, EC2 instance launches and Network Load Balancer health checks were also impacted, which in turn affected connectivity for Lambda, DynamoDB, and CloudWatch. We apologize for any inconvenience caused and thank you for your patience.

Read the full incident report →

Started Oct 15, 2025, 05:25 PM UTC· resolved Oct 15, 2025, 11:26 PM UTC

1. investigating Oct 15, 2025, 05:25 PM UTC

   We are aware of an issue affecting ODC Studio Login in the US East, Canada Central, South america, and Europe regions. Customers may receive an error message stating "Our server is experiencing some issues" and be unable to log in to ODC Studio. Our team is currently investigating the cause. We will provide an update as soon as more details are available.

2. investigating Oct 15, 2025, 10:28 PM UTC

   We are continuing to investigate this issue.

3. resolved Oct 15, 2025, 11:26 PM UTC

   We have identified the issue as a client-side issue, and the suggested workaround has been shared with the affected customers for implementation. We have now confirmed that the workaround has fully resolved the issue, and our service is now operating as expected.

4. postmortem Oct 16, 2025, 11:22 AM UTC

   On October 15th, multiple customers reported being unable to log in to ODC Studio, temporarily interrupting their development work. Access through the ODC Portal remained available. The issue was caused by recent Microsoft Windows updates affecting certain users. A temporary workaround was provided, and uninstalling the updates restored normal access. Microsoft has since released an update to resolve the problem, and customers should now be able to run Windows Update and install it.

Read the full incident report →