Outsystems experienced a major incident on June 19, 2025 affecting Asia Pacific / Mumbai and Asia Pacific / Singapore and 1 more component, lasting 1h 8m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 19, 2025, 05:02 PM UTC
We are experiencing some partial infrastructure outage which is causing issues connecting with ODC Portal and ODC Studio in some Pacific regions. Our team is currently investigating its cause. We will provide an update in as soon as more details are available.
- investigating Jun 19, 2025, 05:25 PM UTC
We are continuing to investigate this issue.
- monitoring Jun 19, 2025, 05:29 PM UTC
We are now observing successful logins and a restoration of functionalities, our teams are actively monitoring the situation to ensure full and stable recovery across all affected services and tenants.
- resolved Jun 19, 2025, 06:10 PM UTC
This incident has been fully resolved. ODC Platform and ODC Studio are now operating as expected in all regions. Thank you for your patience.
- postmortem Jun 23, 2025, 03:39 PM UTC
Users in the Asia-Pacific region experienced login issues with the ODC Portal and Studio, which temporarily disrupted access. The issue was identified through both customer reports and internal monitoring and was traced to performance problems within the system’s internal messaging component. Initial recovery involved restarting services in affected regions, which restored access for users. Further investigation revealed that one of the background components had a faulty instance, and a full service restart was required to stabilize performance. A follow-up issue occurred the next day, again impacting login functionality. This time, analysis showed that the problem was not due to network issues, but to the way the system handled message compression and memory usage. A temporary fix was applied, significantly reducing memory consumption and resolving the performance degradation. The root cause has been confirmed as inefficiencies in the internal messaging layer, which handles coordination across regions. A deeper investigation is ongoing, and preventive measures are being implemented to avoid similar incidents in the future.