Outsystems Outage History

On Wednesday, August 20, between 18:09 UTC and 21:58 UTC, some customers experienced intermittent errors in the DEV environment in US East \(Virginia\) and Europe \(Frankfurt\). Support teams identified a configuration issue that reduced service availability. A workaround was shared, and service was fully restored by 21:58 UTC. A permanent fix has since been applied to prevent similar issues in the future.

On August 14th, a system update caused a critical service to restart with a faulty configuration, leading to connectivity issues for some applications. The issue was addressed and resolved on the same day by correcting the configuration.

On July 25th, Global Support received multiple reports of unexpected changes in environment order, which disrupted customers’ deployment pipelines and revision numbers. The issue was caused by a backend process that unintentionally triggered environment reordering following renaming actions. Immediate mitigation steps were taken, including pausing the renaming function and correcting affected cases. A long-term solution is being planned, involving improved API controls and a self-service feature.

On July 14th, customers in the Europe region experienced intermittent errors when publishing applications in ODC Studio, along with issues accessing Organization roles in the ODC Portal. While publishing actions generally succeeded, the sporadic nature of the errors disrupted development workflows and prevented role management for some users. The issue was caused by an internal service component that was not processing updates as expected, resulting in permission and communication errors on ODC Studio and Portal. The problem was quickly identified and mitigated through targeted corrective actions. The system is now stable, and a long-term fix is being implemented to prevent recurrence.

Between July 3rd and July 5th, 2025, customers in multiple regions experienced intermittent issues with Mentor features. The disruptions stemmed from a failure during a service deployment that impacted the stability of the underlying infrastructure. While the overall incident duration was approximately 30 hours, customer-facing impact was limited and sporadic, with most functionality remaining available during the affected period. The root cause was a combination of deployment inconsistencies and environment misalignments that surfaced during the release process. Recovery was achieved by deploying a revised and stabilized version of the service. To prevent future occurrences, work is underway to improve deployment validation processes, refine rollback mechanisms, and accelerate the implementation of a multi-region pre-production testing environment to catch region-specific issues earlier in the release cycle.

On July 1, 2025, customers from multiple regions, mainly APAC, Europe and the Middle East. experienced difficulties accessing Mentor's Workflow and App Editors, encountering “502 Bad Gateway” errors. The disruption was caused by a routing misconfiguration affecting access to specific Mentor assets in certain regions. The root cause was promptly identified, and a rollback process was initiated at 14:45 UTC to address the issue. The remediation was successfully completed by 23:05 UTC, and full functionality has been restored for all impacted customers.

On April 1st, 2025, a critical incident affected 1CP operations. Users encountered an error code, which was traced to a misconfiguration. The issue originated from a deployment on March 31st. To resolve the incident, the team promptly rolled back the affected deployment.

At 12:05 PM UTC, our monitoring detected the first signs of this issue. The first customer report was received at 12:53 PM UTC. The issue prevented timers from running in portions of two regions, affecting both customer applications and applications generated by Mentor. Further investigation revealed that a rare pattern in timer triggers was responsible. Corrective actions were applied, and by 6:30 PM UTC, all timers were confirmed operational. A permanent fix is being deployed to eliminate the risk of recurrence. In the meantime, enhanced monitoring is in place to detect this pattern early and enable rapid response if it reoccurs.

On February 6, 2025, at 11:41 UTC, we experienced an issue affecting App promotion / Promote and Portal visibility in multiple regions, preventing customers from tenants created after January 30th, from developing applications as they're unable to edit or deploy them. Normal service was restored at 17:19 UTC. The incident was caused by the implementation of new features in ODC, where changes to an underlying feature on a service introduced some inconsistencies in the Platform Data Model. To prevent new occurrences, the offending changes to the platform data model were reverted, which resolved the issue and enabled the customers to resume their operations.