OutSystems Incident History

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.

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.

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.

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.

On the 20th of July 2026, there was an issue with the wake-up functionality affecting Personal Editions. This occurred in all three regions \(US East, Europe and Asia Pacific\). Users were unable to wake up their environments from hibernation. When attempting to wake up the environments, they either remained in hibernation or moved to a "waking up" state indefinitely, preventing access to applications. This was caused by an issue in how our backend systems processed environment status updates. Due to messages being processed out of order, some environments' internal state was incorrectly reverted to 'hibernated' after they had already woken up successfully, even though the environment itself remained accessible on the backend. This caused the ODC Portal to keep showing an inaccurate 'hibernated' or 'waking up' status, and repeated wake-up attempts did not resolve it since the underlying state kept getting overwritten. We identified the root cause on the 21st of July and deployed a code fix to correct the state synchronization. The fix started to be rolled out to all regions on 22nd of July and completed by the 23rd of July. All affected environments were woken up successfully. We are implementing additional state verification checks to ensure the ODC Portal and backend systems remain in sync. A full technical review is underway to identify similar synchronization gaps across other features. We apologize for any disruption caused and thank you for your patience.

We have successfully resolved the issue affecting ODC Personal Editions across multiple regions. Environments that were unable to wake from hibernation are now fully operational. All known affected customers have now been restored to service, and we confirm that services are operating as expected across all regions. We apologize for any disruption caused and thank you for your patience.

Our team has deployed an automated fix to systematically restore affected Personal Edition environments. Recovery is now in progress across all regions. The fix should handle recovery automatically. We are actively monitoring restoration progress and will confirm full resolution once the process completes. We will provide updates as more information becomes available.

We have identified a temporary workaround that may help affected users restore access while the fix continues to roll out: publishing an application in your Personal Edition may temporarily help wake it up. If you are currently unable to wake your environment, please try publishing an application. We will provide further updates as the deployment progresses.

Our team has identified a resolution and is actively rolling out a fix. During the deployment, symptoms may persist while the fix reaches all affected regions. We will provide updates as more information becomes available.

We are aware of a recurrence of issues affecting Personal Editions on ODC in several regions (US East, Europe, and Asia Pacific). Following the resolution we announced yesterday, some users have reported that they are still experiencing difficulties waking their environments from hibernation. Our team is actively investigating this recurrence and working to identify the cause. We will provide updates as more information becomes available.

This incident has been resolved. ODC Personal Editions are now operating normally. If you have not yet done so, please access your Personal Edition by clicking "Wake Up" in the ODC Portal. If you experience any issues, our support team is available to assist. Thank you for your patience.

The issue has been identified. There is a bug in the synchronization between internal systems that operate the wake-up process. We are now working on correcting this to allow Personal Editions to be woken up successfully.

We are aware of an issue affecting Personal Editions on ODC in at least three different regions (US East (Ohio), Asia Pacific (Singapore) and Europe (Ireland). Users are experiencing difficulties waking their environments from hibernation, with environments either returning to hibernated state or remaining indefinitely in the wake-up process. Our team is currently investigating its cause. We will provide an update as soon as more details are available.