Is OutSystems Down?

Our team continues to work on mitigation measures for the issue affecting the performance of applications running on ODC across multiple regions. We are coordinating next steps with the affected customers, while a long-term solution is still being worked on. We will provide updates as more information becomes available. --- [2026-11-09T16:16:13.975Z] (identified) We have identified the cause of an issue affecting the performance of applications running on ODC across multiple regions. The issue is not caused by customers’ applications or data. Users may continue to experience intermittent slowness, in some cases affecting several screens at the same time, and in some cases requests that do not complete. The issue should only happen after database inactivity periods. Our team is actively implementing mitigation measures to reduce the impact, and a longer-term solution is also being worked on. Customers may continue to see these symptoms while the measures are rolled out. We will provide updates as more information becomes available.

On November 3rd, between approximately 09:00 UTC and 13:44 UTC, some ODC users in the Asia Pacific / Sydney region experienced slower performance and even timeout errors when publishing applications. The disruption was traced to a transient fault in the cloud provider’s underlying infrastructure, affecting a small part of the capacity used for publishing in the region. The fault intermittently delayed network traffic, preventing some publishing operations from completing within the standard timeframe. Normal service was restored at 13:44 UTC, and publishing operations have been completing successfully within expected periods of time since that time. We apologize for any disruption caused and thank you for your patience. --- [2026-11-03T21:20:04.046Z] (resolved) This incident has been resolved. Publish operations on ODC in the Asia Pacific / Sydney region have been operating normally since 13:44 UTC, and users should no longer encounter intermittent Deployment Timeout errors (OS-DPL-40802) when publishing. Our team is continuing to investigate the underlying cause and will share further details in a post-mortem. We apologize for any disruption caused and thank you for your patience. --- [2026-11-03T21:18:07.981Z] (monitoring) This incident has been resolved. Publish operations on ODC in the Asia Pacific / Sydney region have been operating normally since 13:44 UTC, and users should no longer encounter intermittent Deployment Timeout errors (OS-DPL-40802) when publishing. Our team is continuing to investigate the underlying cause and will share further details in a post-mortem. We apologize for any disruption caused and thank you for your patience. --- [2026-11-03T15:56:50.392Z] (monitoring) We have observed Publish Operations on ODC in the Asia Pacific / Sydney region returning to normal, and publishing attempts are now completing as expected. We are continuing to monitor the platform closely to confirm that the service remains stable, and will provide updates as more information becomes available. --- [2026-11-03T14:16:29.898Z] (investigating) We are investigating an issue affecting Publish Operations on ODC in the Asia Pacific / Sydney region. Users in this region may experience intermittent Deployment Timeout errors (OS-DPL-40802) when publishing, while reattempts to publish may then finish successfully in a short amount of time. Other regions are not affected by this. Our team is actively investigating and will provide updates as more information becomes available.

On October 23rd, 2026, between 06:40 and 09:50 UTC, users in the EMEA and APAC regions experienced an issue affecting Forge in ODC Portal, which was unavailable and displayed an error when accessed. Other areas of ODC Portal that depend on communication between regions were also affected, with users experiencing errors or slower performance in those areas as well. The cause was routine maintenance on underlying servers, during which a traffic-routing setting directed most traffic to a single server that could not keep up with the load. This disrupted communication between regions. The issue was first reported by customers. Once our team returned the affected part of our internal messaging infrastructure to normal operation at 9:50 UTC, normal service was restored. To prevent a recurrence, we are correcting the routing setting so that traffic is always spread across all available servers, and adding monitoring that alerts us within minutes if a similar situation occurs. We apologise for any disruption caused and thank you for your patience. --- [2026-10-23T15:06:50.819Z] (resolved) The issue affecting Forge and other components of the ODC Portal in the EMEA and APAC regions has been resolved. Users may have experienced errors or slower performance when accessing certain areas of ODC Portal. The cause was a maintenance-related configuration issue in our underlying infrastructure, and all services are now operating as expected. Our team is continuing to work on measures to help prevent future recurrences. We apologise for any disruption caused and thank you for your patience. --- [2026-10-23T10:40:08.824Z] (monitoring) A fix has been applied to address the issue affecting Forge in the ODC Portal. Upon applying the fix, we confirmed this was also affecting other components in ODC Portal, such as the configuration of custom domains. Users may have experienced slowness or errors when accessing these areas of ODC Portal. This is no longer occurring and we are closely monitoring the platform to confirm full recovery. We will provide updates as more information becomes available. --- [2026-10-23T08:25:46.527Z] (identified) We are currently investigating an issue affecting Forge in the ODC portal. Users in the EMEA and APAC regions may experience errors when accessing Forge in ODC Portal, displaying the message: "Sorry, something went wrong. Try refreshing the page. If the problem persists, let us know. (OS-FRGE-GEN-60028)". The Public Forge and Forge in O11 are working as expected. Our team is actively working on a solution. We will provide an update once more details are available.