Is OutSystems Down?

The incident affecting sign-in and application access in the South America / São Paulo region has been resolved. All services are now fully operational. --- [2026-08-10T22:23:23.359Z] (monitoring) A fix has been applied to address the issue affecting sign-in and application access for ODC in the South America / São Paulo region. Initial checks with affected users confirm that sign-in and application access have been restored. We are now monitoring the platform to ensure full recovery across all affected services, including ODC Studio and the ODC Portal. --- [2026-08-10T20:48:02.061Z] (investigating) We are aware of an issue affecting ODC in the South America / São Paulo region. Users may be unable to sign in, and applications in production may be unavailable to end users. Access to ODC Studio and the ODC Portal may also be affected. Our team is currently investigating the cause and will provide updates as more information becomes available.

On July 31st, 2026, an issue affected applications running in the Development Stage in Europe Central \(Frankfurt\). Applications experienced extended delays \(2–3 minutes\) and timeout errors when starting up from an idle state. The issue lasted approximately a few hours and was detected through customer reports and platform monitoring. During this time, several customers in the region reported difficulties launching their applications in the Development Stage's Runtime. Our investigation identified a memory issue in a critical component responsible for automatically scaling applications based on incoming traffic. This component was consuming excessive memory and restarting repeatedly, which prevented applications from scaling up when first accessed. Our team immediately implemented an operational workaround by increasing resource limits for this component. This mitigation immediately allowed applications to scale up as expected. In parallel, we developed a permanent code fix to address the root cause and deployed it on August 7th. The system remained stable, with no new occurrences during and after the deployment of the permanent fix. To prevent similar issues, OutSystems is improving how we monitor and validate infrastructure configuration to catch memory and resource issues earlier, and we are enhancing our automated scaling components to handle traffic pattern changes more gracefully. We apologise for any disruption caused and thank you for your patience. --- [2026-08-07T08:34:33.760Z] (resolved) This issue has been resolved. Following ongoing monitoring, no new occurrences of the issue have been reported. Applications in the Development Stage in Europe Central (Frankfurt) have been scaling up successfully without errors since our fix was implemented. --- [2026-08-04T09:59:12.946Z] (monitoring) We are continuing to monitor the implemented fix, and no new occurrences have been reported. We will share our next status update by the end of the week. --- [2026-07-31T15:53:47.108Z] (monitoring) We continue to monitor the fix implemented earlier this morning to ensure full recovery. Applications should scale up successfully with no errors now. Some latency (seconds) might still be noticed before they fully scale up. We will provide updates as more information becomes available. --- [2026-07-31T10:43:55.399Z] (identified) We have identified the cause of the "upstream request timeout" error. Our team has implemented a fix and apps should once again scale up succesfully without errors. We continue to investigate the issue to ensure full recovery. The previously mentioned workaround of republishing your applications remains available during this period. We will provide updates as more information becomes available. --- [2026-07-31T10:47:44.675Z] (investigating) We are aware of an issue affecting Applications in the Development Stage in Europe Central (Frankfurt). Applications may experience an "upstream request timeout" error, when scaling up. As a workaround, most applications will load after a few minutes. Republishing the application will also successfully scale it up within few minutes. Our team is currently investigating its cause. We will provide an update as soon as more details are available.

On July 30, 2026, between 15:19 and 15:59 UTC, customers in multiple regions experienced an outage affecting access to the OutSystems ODC Portal, preventing them from logging in or accessing their development environments. The incident was caused by the addition of a custom header, which prevented requests from reaching the portal. Following the code change rollback, service was restored by 15:59 UTC. To prevent similar incidents in the future, we are implementing additional automated testing to validate configuration changes before they are deployed to production and conducting a comprehensive review of our code review and testing procedures to catch such issues earlier in the development process. We appreciate your patience during this incident and apologize for any disruption to your work. --- [2026-07-30T18:39:10.991Z] (resolved) The 502 errors affecting the ODC Portal globally have been resolved. Between 15:19 and 15:59 UTC on July 30th, users experienced connectivity issues caused by a recent configuration change affecting header validation. The change has been reverted, and access to the ODC Portal has been fully restored. All services are now operating as expected. We apologise for any disruption caused and thank you for your patience.