Oct <var data-var='date'> 6</var>, <var data-var='time'>08:37</var> UTC Resolved - The issue affecting application publishing in ODC in the Asia Pacific, Mumbai region has been resolved. A fix has been applied and publishing from ODC Studio is now working as expected. We apologise for any disruption caused and thank you for your patience. Oct <var data-var='date'> 5</var>, <var data-var='time'>11:55</var> UTC Monitoring - We have identified the cause of the issue affecting application publishing in ODC in the Asia Pacific, Mumbai region. The issue was linked to a fault in a supporting service involved in retrieving application configurations, and corrective action has now been applied. Error rates have returned to normal, and users should now be able to publish applications from ODC Studio. We are closely monitoring the platform and confirming full recovery with affected users, and will provide a further update once the incident is fully resolved. Oct <var data-var='date'> 5</var>, <var data-var='time'>10:26</var> UTC Investigating - We are investigating an issue affecting application publishing in ODC in the Asia Pacific, Mumbai region. Users may experience intermittent failures when publishing applications from ODC Studio, with an error related to fetching application configurations. Our team is actively investigating the cause and will provide updates as more information becomes available.

Issue Affecting Application Publishing in Asia Pacific, Mumbai region

Sep <var data-var='date'>30</var>, <var data-var='time'>13:40</var> UTC Resolved - The issue affecting login to Personal Environments in the Asia Pacific (Singapore) region has been resolved. The fix has now been applied to all affected accounts, and users are able to log in again without encountering the "Login with external provider failed" error. We apologise for any disruption caused and thank you for your patience. Sep <var data-var='date'>29</var>, <var data-var='time'>18:23</var> UTC Update - We have applied the fix to a first set of affected accounts in the Asia Pacific (Singapore) region and confirmed that users on those accounts are able to log in to their Personal Environments again. The remaining affected accounts have not yet been updated, and users on those accounts will continue to see the "Login with external provider failed" error until the fix is applied. We will provide a further update as more information becomes available. Sep <var data-var='date'>29</var>, <var data-var='time'>11:41</var> UTC Identified - We have identified the cause of the issue affecting login to Personal Environments in the Asia Pacific (Singapore) region. The problem is related to a configuration issue with the external login provider for affected accounts. Some users may still experience the previously reported "Login with external provider failed" error while the fix is completed across all affected accounts. Our team is actively working to finish the resolution and will provide a further update once more information is available. Sep <var data-var='date'>29</var>, <var data-var='time'>09:00</var> UTC Investigating - We are investigating an issue impacting ODC Personal Editions in the Asia Pacific (Singapore) region. Users may be unable to log in to their personal environments and may encounter the error message "Login with external provider failed." Our team is actively investigating the issue and will provide further updates as soon as more information becomes available.

Incident affecting Personal Edition login in Asia Pacific (Singapore)

Sep <var data-var='date'>30</var>, <var data-var='time'>11:32</var> UTC Resolved - The issue that prevented ODC users across multiple regions from previewing data in ODC Studio, and that may also have caused errors in application runtime, has been resolved. A fix was applied and our team has monitored the platform to confirm full recovery. Data preview is working as expected and all services are operating normally. We apologise for any disruption caused and thank you for your patience. Sep <var data-var='date'>29</var>, <var data-var='time'>16:52</var> UTC Monitoring - The fix has now been fully applied across all affected regions, and error rates have returned to normal levels. Users should once again be able to preview data in ODC Studio and access their applications as expected. We are continuing to monitor the platform closely and are confirming full recovery with affected users. We will provide a further update once we have confirmed the incident is fully resolved. Sep <var data-var='date'>29</var>, <var data-var='time'>11:36</var> UTC Identified - We have identified the cause of this issue as a recent database authentication update that failed validation during rollout. The update has been reverted, and a fix is currently being deployed. As the fix is applied across affected regions, users may still experience difficulty previewing application data in ODC Studio or encounter errors when accessing their applications. We will provide an update as soon as more information becomes available. Sep <var data-var='date'>29</var>, <var data-var='time'>10:49</var> UTC Investigating - We are investigating an issue affecting ODC users across multiple regions. Users are currently unable to preview data in ODC Studio and may also encounter errors in application runtime. The issue is associated with the error message: "FATAL: PAM authentication failed for user "osruntime"". Our engineering team is actively investigating the issue, and we will provide an update as soon as more information is available.

Incident affecting data preview in ODC Studio and runtime applications

Sep <var data-var='date'>16</var>, <var data-var='time'>19:22</var> UTC Resolved - This incident has been resolved. Our cloud provider has confirmed that the infrastructure disruption in the underlying cloud region is fully resolved, and we have verified that services in the Israel (Tel Aviv) region are operating normally, including sign-in to the ODC Portal and access to applications. We apologise for any disruption caused and thank you for your patience. Sep <var data-var='date'>16</var>, <var data-var='time'>18:51</var> UTC Monitoring - Our cloud provider has resolved the infrastructure disruption in the underlying cloud region, and our services in the Israel (Tel Aviv) region have recovered. Users should now be able to sign in to the ODC Portal and access their applications. We are monitoring the platform closely to confirm it remains stable and will provide a further update once we have confirmed full resolution. Sep <var data-var='date'>16</var>, <var data-var='time'>16:20</var> UTC Update - The issue has been traced to an infrastructure disruption in the underlying cloud region, which is affecting our services in the Israel (Tel Aviv) region. Users remain unable to sign in to the ODC Portal. We are working closely with our cloud provider, who is actively working to mitigate the disruption. We will provide updates as more information becomes available. Sep <var data-var='date'>16</var>, <var data-var='time'>15:50</var> UTC Investigating - We are aware of authentication issues affecting users in the Israel (Tel Aviv) region. Users are currently unable to sign in to both the ODC Portal and runtime applications in all Stages. Our team is actively investigating and will provide updates as more information becomes available.

Authentication Issues Affecting ODC in the Israel (Tel Aviv) Region

Sep <var data-var='date'>15</var>, <var data-var='time'>12:56</var> UTC Resolved - The issue affecting logins with the error "wrong credentials and password resets with "incorrect verification code" on OutSystems Personal Edition and the Community website has been fully resolved. The fix has been confirmed effective for all affected accounts, and password resets are now completing successfully. We apologise for any disruption this may have caused and thank you for your patience. Sep <var data-var='date'>14</var>, <var data-var='time'>22:08</var> UTC Monitoring - A fix has been applied to all accounts affected by the password reset issue on ODC Personal Edition and the Community website. We are now closely monitoring the platform to confirm that password resets are completing as expected and that all affected accounts have fully recovered. If you continue to experience issues resetting your password, please contact our Global Support team. Sep <var data-var='date'>14</var>, <var data-var='time'>19:51</var> UTC Update - The fix for the issue affecting password resets on ODC Personal Edition and the Community website is now being applied to all affected accounts. This process is progressing as expected, though some users may continue to experience issues until it completes over the coming hours. In the meantime, if you receive an "invalid verification code" error when resetting your password despite using the correct code, please contact our Global Support team to have the mitigation applied to your account. We will provide a further update as more information becomes available. Sep <var data-var='date'>14</var>, <var data-var='time'>13:29</var> UTC Identified - We have identified the cause of the issue preventing some users from resetting their password on their ODC Personal Editions or the Community website. This issue affects only a subset of emails. If you receive an "invalid verification code" error when resetting your community/ODC PE password despite using the correct verification code, please contact our Global Support for the mitigation to be applied to your account. In the meantime, our teams are actively working on applying a global fix to all affected accounts. We will provide an update once more details are available. Sep <var data-var='date'>14</var>, <var data-var='time'>11:07</var> UTC Investigating - We are currently investigating an issue where users are unable to reset their passwords. When attempting to use the password reset flow, the process fails with the error message "incorrect verification code", despite entering the correct code. This is currently preventing users from logging in if they require a password reset. Our team is actively investigating the issue to determine the cause and will provide further updates as soon as more information becomes available.

Incident affecting password reset functionality

Sep <var data-var='date'>11</var>, <var data-var='time'>16:43</var> UTC Resolved - The migration to the new Community unified login system has been completed. Sign-in and account operations are now available again across the Community, the Support Portal, O11 Personal Environments and the ODC Personal Edition. All services are operating as expected. We apologise for any disruption caused and thank you for your patience. Sep <var data-var='date'>11</var>, <var data-var='time'>15:09</var> UTC Identified - Maintenance work on the new Community unified login system is still underway. Our team is finalizing the transition tasks to ensure a smooth migration across the Community, O11 Personal Environments, and the ODC Personal Edition. Account operations and login access remain temporarily restricted while this work completes. We apologize for the extended downtime and will provide our next update shortly. Sep <var data-var='date'>11</var>, <var data-var='time'>13:24</var> UTC Update - Maintenance work on the new Community unified login system is still underway. Our team is finalizing the transition tasks to ensure a smooth migration across the Community, O11 Personal Environments, and the ODC Personal Edition. Account operations and login access remain temporarily restricted while this work completes. We apologize for the extended downtime and will provide our next update shortly. Sep <var data-var='date'>11</var>, <var data-var='time'>12:47</var> UTC Update - Maintenance work on the new Community unified login system is still underway. Our team is finalizing the transition tasks to ensure a smooth migration across the Community, O11 Personal Environments, and the ODC Personal Edition. Account operations and login access remain temporarily restricted while this work completes. We apologize for the extended downtime and will provide our next update shortly. Sep <var data-var='date'>11</var>, <var data-var='time'>12:47</var> UTC Investigating - We are updating the OutSystems Community to a single, unified login system between September 8th and September 11th. This change creates one stable identity across the Community, O11 Personal Environments (PE), and ODC Personal Editions, eliminating the need to re-authenticate when navigating between platforms. Between September 8th and 11th, certain account operations—such as updating profile details, merging accounts, or requesting new PEs—will be temporarily restricted. Additionally, login access on both the Community and the Support Portal will experience a short outage on September 11th while the final switch completes.

Ongoing authentication maintenance

Sep <var data-var='date'>11</var>, <var data-var='time'>11:56</var> UTC Resolved - Our team has completed the fix and confirmed that the pagination of Logs in ODC Portal is now working as expected. We apologize for any disruption caused and thank you for your patience. Sep <var data-var='date'>11</var>, <var data-var='time'>07:55</var> UTC Identified - We have identified the cause of the issue and confirmed that it is impacting every region. A fix is being finalized and rolled out. The issue will persist until the fix is fully deployed. As a temporary workaround, we suggest applying stricter filters to limit the amount of logs to a single page as much as possible. We will provide updates as more information becomes available. Sep <var data-var='date'>11</var>, <var data-var='time'>06:23</var> UTC Investigating - We are aware of an issue affecting the Logs page in ODC Portal Monitor across multiple regions. Users may be unable to view log entries beyond the first page — later pages can show entries that have already been seen. Our team is currently investigating the cause. We will provide updates as more information becomes available.

Issue Affecting Log Pagination in ODC Portal Monitor

Sep <var data-var='date'> 4</var>, <var data-var='time'>12:47</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'> 4</var>, <var data-var='time'>12:28</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Sep <var data-var='date'> 4</var>, <var data-var='time'>11:15</var> UTC Identified - We have identified an issue affecting npm audit actions during npm installations and are currently working on a fix.

MABS Android and iOS builds timming out

Aug <var data-var='date'>31</var>, <var data-var='time'>18:00</var> UTC Resolved - The issue affecting Mentor in ODC Studio in the Asia Pacific (Sydney) region has been resolved. A configuration change caused Mentor connection requests to be directed incorrectly, which produced the connection error. That change has been reversed across all affected environments, and our team has confirmed that Mentor is working as expected again. We apologise for any disruption caused and thank you for your patience. Aug <var data-var='date'>31</var>, <var data-var='time'>17:02</var> UTC Identified - We have identified the cause of the issue affecting Mentor in ODC Studio in the Asia Pacific (Sydney) region, and a fix is being applied. Users may continue to see the connection error while the fix is rolled out across all affected environments. We will provide updates as more information becomes available. Aug <var data-var='date'>31</var>, <var data-var='time'>15:34</var> UTC Update - We are continuing to investigate this issue. Aug <var data-var='date'>31</var>, <var data-var='time'>15:30</var> UTC Update - We are continuing to investigate this issue. Aug <var data-var='date'>31</var>, <var data-var='time'>15:28</var> UTC Investigating - We are aware of an issue affecting ODC in the Sydney Region. Developers using Mentor Studio will run into an error stating, "Mentor couldn't connect. Please go online and try again." Our team is actively investigating and will provide updates as more information becomes available.

Connection issue in Mentor Studio

Aug <var data-var='date'>26</var>, <var data-var='time'>16:33</var> UTC Resolved - This incident has been resolved. The issue was caused by a recent platform update that could prevent a timer's status from being recorded correctly after it ran, leaving it in a pending state. Our team has corrected this and confirmed that timers are executing as expected across the affected regions. We apologise for any disruption caused and thank you for your patience. Aug <var data-var='date'>26</var>, <var data-var='time'>06:56</var> UTC Monitoring - A solution has been applied to resolve this issue. We will continue monitoring this situation to ensure full recovery. We will provide updates as more information becomes available. Aug <var data-var='date'>26</var>, <var data-var='time'>05:16</var> UTC Investigating - We are currently investigating an issue that may cause delays in the execution of timers for some applications. Some timers may remain pending longer than expected. We will provide an update as soon as we have more information.

Issue with delayed timer execution in ODC

Aug <var data-var='date'>24</var>, <var data-var='time'>19:12</var> UTC Resolved - This incident has been resolved. The issue affecting application deployments in ODC Portal has been mitigated, and deployments are operating normally. Users attempting to deploy an application to another stage should no longer encounter the error OS-STGC-60005. Our monitoring shows no further occurrences of this error since 16:23 UTC. We apologise for the disruption this caused to deployment activities. Aug <var data-var='date'>24</var>, <var data-var='time'>18:07</var> UTC Monitoring - A fix has been applied to address the issue affecting application deployments in ODC Portal, and we are seeing initial signs of recovery. Users attempting to deploy an application to another stage should progressively stop encountering the error OS-STGC-60005. We are now monitoring the platform across the affected regions to confirm full recovery. We will provide updates as more information becomes available. Aug <var data-var='date'>24</var>, <var data-var='time'>14:57</var> UTC Investigating - We are investigating an issue affecting application deployments in ODC Portal. Some users attempting to deploy an application to another stage may see the error message: "An error occurred while getting the generated code from revision. (OS-STGC-60005)". The issue may be intermittent and is currently affecting users across multiple regions. Our team is actively investigating the cause. We will provide an update as soon as more information is available.

Issue affecting application deployments in ODC

Aug <var data-var='date'>21</var>, <var data-var='time'>16:20</var> UTC Resolved - This incident has been resolved. The issue affecting Mentor in the ODC Portal was caused by an outdated permission check that remained in place after a recent change to how the service communicates internally. Our team has removed that check and confirmed that generating and editing applications using Mentor is working as expected across the affected regions. We apologise for any inconvenience caused. Aug <var data-var='date'>21</var>, <var data-var='time'>14:03</var> UTC Monitoring - Our team has implemented a fix for the issue affecting Mentor in the ODC Portal, which was caused by a recent change to the service. We have confirmed that generating and editing applications using Mentor is working again across the affected regions, and we are continuing to monitor. We will provide a further update once monitoring is complete. Aug <var data-var='date'>21</var>, <var data-var='time'>10:54</var> UTC Investigating - We are currently investigating an issue where users are unable to generate and edit applications using Mentor in the ODC Portal, due to the error OS-IDE-CONVERSATIONAL-50035. This issue is impacting multiple regions. Mentor in Studio remains functional. Our team is actively investigating the issue, and we will provide updates as more information becomes available.

Incident affecting Mentor in ODC Portal

Aug <var data-var='date'>13</var>, <var data-var='time'>11:21</var> UTC Resolved - This incident has been resolved. Aug <var data-var='date'>12</var>, <var data-var='time'>16:56</var> UTC Identified - We are experiencing some partial infrastructure outage which is causing connection issues with some of our online tools. We will update you as soon as we have the website up and running.

Partial System outage

Aug <var data-var='date'>12</var>, <var data-var='time'>10:38</var> UTC Resolved - This incident has been resolved. The issue affecting the ODC Portal in the Asia Pacific (Singapore), Europe (Frankfurt), and US East (N. Virginia) regions has been fully addressed, and all services are now operating as expected. Aug <var data-var='date'>12</var>, <var data-var='time'>08:30</var> UTC Monitoring - A fix has been implemented to address the configuration issue affecting the ODC Portal in the Asia Pacific (Singapore), Europe (Frankfurt), and US East (Virginia) regions. We are now closely monitoring the platform to ensure application configurations are loading as expected and to confirm that all systems have fully recovered. Aug <var data-var='date'>12</var>, <var data-var='time'>07:37</var> UTC Update - We continue to investigate the issue affecting ODC in the Asia Pacific (Singapore, Sydney), Europe (Frankfurt), and US East (Virginia) regions. Customers continue to report errors when opening the Configuration tab. Our team is actively working to identify the root cause and will provide updates as more information becomes available. Aug <var data-var='date'>12</var>, <var data-var='time'>05:41</var> UTC Investigating - We are aware of an issue affecting ODC in the Asia Pacific (Singapore, Sydney), Europe (Frankfurt), and US East (Virginia) regions. Users impacted may see the application load and then fail when opening the Configuration tab, along with an error message: "Couldn't get IP filter group" (OS-APPC-60043). Our team is actively investigating and will provide updates as more information becomes available.

Issue Affecting Application Configuration in ODC Portal

Aug <var data-var='date'>11</var>, <var data-var='time'>07:54</var> UTC Resolved - 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. Aug <var data-var='date'>10</var>, <var data-var='time'>22:23</var> UTC 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. Aug <var data-var='date'>10</var>, <var data-var='time'>20:48</var> UTC 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.

Incident affecting sign-in and application access on ODC

Aug <var data-var='date'> 7</var>, <var data-var='time'>08:34</var> UTC 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. Aug <var data-var='date'> 4</var>, <var data-var='time'>09:59</var> UTC Update - 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. Jul <var data-var='date'>31</var>, <var data-var='time'>15:53</var> UTC 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. Jul <var data-var='date'>31</var>, <var data-var='time'>10:43</var> UTC 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. Jul <var data-var='date'>31</var>, <var data-var='time'>08:31</var> UTC 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.

Incident affecting Applications in Development Stage in Europe Central

Jul <var data-var='date'>30</var>, <var data-var='time'>18:39</var> UTC 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.

502 Error Affecting ODC Portal Access Globally

Jul <var data-var='date'>23</var>, <var data-var='time'>09:06</var> UTC Resolved - 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. Jul <var data-var='date'>21</var>, <var data-var='time'>22:36</var> UTC Update - 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. Jul <var data-var='date'>21</var>, <var data-var='time'>09:31</var> UTC Update - 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. Jul <var data-var='date'>21</var>, <var data-var='time'>07:16</var> UTC Identified - 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. Jul <var data-var='date'>21</var>, <var data-var='time'>02:13</var> UTC Investigating - 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.

Recurrence of the incident affecting Personal Editions on ODC in several regions

Jul <var data-var='date'>20</var>, <var data-var='time'>17:37</var> UTC Resolved - 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. Jul <var data-var='date'>20</var>, <var data-var='time'>15:41</var> UTC Identified - 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. Jul <var data-var='date'>20</var>, <var data-var='time'>11:46</var> UTC Investigating - 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.

Incident affecting Personal Editions on ODC in several regions

Jul <var data-var='date'> 3</var>, <var data-var='time'>14:41</var> UTC Resolved - All customers impacted by this incident have been contacted and supported individually. While the Middle East region continues to be affected by the ongoing geopolitical situation and AWS continues to report the region as impacted, OutSystems has completed its direct response to every affected organization. The affected services remain flagged as a major outage while these conditions persist. Customers who need further assistance can contact OutSystems Support by raising a new ticket or continuing their existing case through Support Services. Apr <var data-var='date'> 6</var>, <var data-var='time'>11:51</var> UTC Update - Most affected O11 Cloud customers in the Middle East (Bahrain) region have been mitigated, and overall stability has improved. The AWS outage remains ongoing. We are continuing to actively monitor AWS updates to ensure full service recovery. Further updates will be provided directly to affected users via their individual support tickets. Customers requiring additional assistance are encouraged to contact OutSystems Support by raising a new ticket or following their existing cases through the Support Portal. Mar <var data-var='date'>24</var>, <var data-var='time'>08:20</var> UTC Update - We are investigating reports of service disruption affecting O11 Cloud customer in the Middle East (Bahrain) region. We are currently reaching out to impacted customers directly and will provide further updates as more information becomes available. Mar <var data-var='date'>13</var>, <var data-var='time'>17:00</var> UTC Update - Recovery efforts for the Middle East (UAE) remain ongoing as cloud infrastructure providers work to restore impacted services. ODC organizations remain unavailable while these restoration efforts continue. We are continuing tracking the recovery process of this incident to ensure a complete recovery. Going forward, updates will be delivered directly to affected users through their individual support tickets. Users who require further assistance with this event are encouraged to contact OutSystems Support by raising a new ticket or following their existing cases through the Support Portal. Mar <var data-var='date'>11</var>, <var data-var='time'>17:11</var> UTC Update - Recovery efforts for the Middle East (UAE) remain ongoing as cloud infrastructure providers work to restore impacted services. ODC organizations remain unavailable while these restoration efforts continue. We are closely tracking the progress and will provide further updates as more information becomes available. Mar <var data-var='date'>10</var>, <var data-var='time'>14:36</var> UTC Update - Recovery efforts for the Middle East (UAE) region remain ongoing as cloud infrastructure providers work to restore impacted services. We continue to track the recovery progress and will provide further updates as more information becomes available. Mar <var data-var='date'> 9</var>, <var data-var='time'>11:34</var> UTC Update - Recovery efforts are still underway for the Middle East (UAE) as cloud services work to restore one of the affected areas. We are continuing to track the progress and will provide further updates as more information becomes available. Mar <var data-var='date'> 6</var>, <var data-var='time'>13:14</var> UTC Update - We are continuing to monitor the recovery of ODC services in the Middle East (UAE) as the underlying infrastructure issues are being addressed. We will provide further updates as soon as more information becomes available. Mar <var data-var='date'> 4</var>, <var data-var='time'>17:48</var> UTC Identified - Update - We are continuing to monitor the progress of recovery efforts in the affected region. We will provide further information as soon as more details become available. Mar <var data-var='date'> 4</var>, <var data-var='time'>16:03</var> UTC Monitoring - Update - We are continuing to monitor the progress of recovery efforts in the affected region. We will provide further information as soon as more details become available. Mar <var data-var='date'> 4</var>, <var data-var='time'>07:08</var> UTC Update - Recovery efforts are still being prioritized by AWS for this region, focusing on restoration of the impacted AWS Services. We are closely monitoring the situation and will provide further updates once they become available. Mar <var data-var='date'> 3</var>, <var data-var='time'>17:10</var> UTC Identified - The cause has been identified as a widespread infrastructure failure in the Middle East (UAE) affecting foundational AWS services. While recovery efforts are underway, ODC and other services in this region will remain unavailable until the underlying infrastructure is fully restored. We are closely monitoring the situation as it recovers and will provide further information once it becomes available. Mar <var data-var='date'> 3</var>, <var data-var='time'>08:50</var> UTC Update - We are still continuing to monitor the investigation with AWS, as the recovery towards the impaired AWS Middle East (UAE) Region is still ongoing. While there have been significant improvements made so far, the estimated recovery time will take at least another day before power and connectivity can be restored. Mar <var data-var='date'> 2</var>, <var data-var='time'>15:12</var> UTC Update - We continue to follow closely the investigation in partnership with AWS, towards the recovery of the Middle East (UAE) Region. At this point, we are expecting recovery to take at least a day given the significant efforts required. Until then, ODC and other services in this region will continue experiencing a total service outage. We continue to monitor the situation closely and will provide updates as more information becomes available. Mar <var data-var='date'> 2</var>, <var data-var='time'>09:31</var> UTC Update - We are investigating an issue affecting Outsystems Products in the Middle East (UAE) region. This disruption is related to the ongoing AWS service incident reported on March 1st. Users in this region are currently experiencing a total service outage in ODC, and all services are unavailable. We are monitoring the situation closely and will provide updates as more information becomes available. Mar <var data-var='date'> 2</var>, <var data-var='time'>08:59</var> UTC Investigating - We are currently investigating this issue. Mar <var data-var='date'> 1</var>, <var data-var='time'>21:43</var> UTC Monitoring - Our services have been fully restored, and the issue affecting our OutSystems customers has been mitigated. While the ongoing disruption reported by AWS continues, it is not expected to impact our customers at this time. We will continue to closely monitor the situation. If you experience any issues, please contact our Support team. For updates directly from AWS, please visit: https://health.aws.amazon.com/health/status Mar <var data-var='date'> 1</var>, <var data-var='time'>20:32</var> UTC Update - We are continuing to monitor the official AWS status page. At this time, AWS has informed customers that some may experience errors when performing certain network-related actions. AWS is actively implementing mitigation measures, and recovery is expected within the next few hours. Mar <var data-var='date'> 1</var>, <var data-var='time'>18:43</var> UTC Identified - AWS Team has identified the cause of the disruption affecting one availability zone in the Middle East (UAE) region. Power was temporarily shut down at the facility as a safety precaution. Restoration of power and connectivity may take several hours. Other availability zones in the region remain operational. We will provide further updates as more information becomes available. Mar <var data-var='date'> 1</var>, <var data-var='time'>16:33</var> UTC Investigating - We are currently experiencing service degradation in the Middle East (UAE) region due to connectivity and power issues within a major cloud provider (AWS). We are actively monitoring the situation and following updates from the official AWS status page. Our team is closely tracking recovery progress. We will provide further updates as more information becomes available.

Connectivity and Power Issues Detected in Middle East

Jun <var data-var='date'>30</var>, <var data-var='time'>18:22</var> UTC Resolved - The configuration issue affecting deployment pipeline stage ordering across multiple regions for ODC has been resolved. The fix has fully addressed both the primary issue identified on June 29th and a secondary edge case affecting users with custom environment names. Our team has completed the monitoring period, and all services are now operating as expected. We apologise for any disruption caused and thank you for your patience. Jun <var data-var='date'>30</var>, <var data-var='time'>14:05</var> UTC Monitoring - A fix has been implemented to address the configuration issue affecting deployment pipelines across multiple regions. We are now closely monitoring the platform to ensure application promotions are proceeding as expected and to confirm that all systems have fully recovered. Jun <var data-var='date'>30</var>, <var data-var='time'>08:56</var> UTC Identified - We are investigating a recurring issue where users are experiencing difficulties promoting applications through their deployment pipelines due to an incorrect ordering of deployment stages. This issue is currently affecting users across several regions. Our team is actively working to resolve the problem as quickly as possible and will provide updates as more information becomes available.

Recurring issue Deployment Stage Incorrectly Ordered on ODC Platform

Jun <var data-var='date'>29</var>, <var data-var='time'>18:07</var> UTC Resolved - The incident has been resolved. The fix has been successfully applied across all affected regions, and we have verified that deployment pipelines are now operating with the correct stage ordering. We received direct confirmation from affected customers and have seen no further reports since the fix was implemented. We apologise for any disruption caused and thank you for your patience. Jun <var data-var='date'>29</var>, <var data-var='time'>13:52</var> UTC Monitoring - We have applied a solution to resolve the configuration issue affecting deployment pipelines across multiple regions. We are now monitoring the platform closely to ensure that application promotions are functioning correctly and that all systems have fully recovered. Jun <var data-var='date'>29</var>, <var data-var='time'>11:21</var> UTC Update - We are continuing to work on a fix for this issue. Jun <var data-var='date'>29</var>, <var data-var='time'>10:43</var> UTC Update - We are continuing to work on implementing the fix for the configuration issue affecting deployment pipelines across multiple regions. While the mitigation actions are being executed, users may still experience issues promoting applications or see incorrect ordering in their deployment stages. We remain focused on resolving this as quickly as possible and will provide another update once the solution has been fully rolled out. Jun <var data-var='date'>29</var>, <var data-var='time'>07:46</var> UTC Identified - The root cause has been found and linked to a misconfigured code that was deployed recently, which was then used to update the environment configuration orders. Mitigation actions will be implemented soon. We appreciate your patience while the fix is being fully rolled out. Jun <var data-var='date'>29</var>, <var data-var='time'>04:28</var> UTC Investigating - We are currently investigating an issue where users are experiencing difficulties promoting applications through their deployment pipelines due to an incorrect ordering of deployment stages. This issue is affecting users across several regions. We are working to resolve the problem as quickly as possible and will provide updates as more information becomes available.

Deployment Stage Incorrectly Ordered on ODC Platform

Jun <var data-var='date'>25</var>, <var data-var='time'>12:31</var> UTC Resolved - This incident has been fully resolved. Services are now operating as expected, and users can successfully deploy their apps without encountering the previous error. Jun <var data-var='date'>25</var>, <var data-var='time'>11:36</var> UTC Monitoring - We have applied a fix for the deployment issue and are currently monitoring the system to ensure full recovery. Users in Asia Pacific (Singapore) and Europe (Frankfurt) should see services returning to normal, and we will provide a final update once stability is confirmed. Jun <var data-var='date'>25</var>, <var data-var='time'>09:30</var> UTC Identified - We have identified the root cause of the issue preventing application deployments and are actively working on a fix. Users in Asia Pacific (Singapore) and Europe (Frankfurt) may continue to experience failed deployments and encounter error message OS-BLD-40303 while the solution is being implemented. Jun <var data-var='date'>25</var>, <var data-var='time'>08:44</var> UTC Investigating - We are currently investigating an issue affecting users in Asia Pacific (Singapore) and Europe (Frankfurt). Affected users are experiencing failed application deployments to higher stages, accompanied by the error message OS-BLD-40303. Our team is actively working to resolve the issue, and we will provide further updates as they become available.

Incident affecting ODC app deployments

Jun <var data-var='date'>22</var>, <var data-var='time'>12:42</var> UTC Resolved - We are pleased to confirm that the incident has been resolved, and all services are now operating as expected. ODC users in the US East (N. Virginia) region should no longer experience issues accessing applications in the DEV stage or encounter "Upstream Request Timeout" errors. Jun <var data-var='date'>22</var>, <var data-var='time'>12:22</var> UTC Monitoring - We have applied a solution and are currently monitoring the situation to ensure a full recovery. ODC users in the US East (N. Virginia) region who were blocked from accessing applications in the DEV stage and encountering "Upstream Request Timeout" errors should see services returning to normal. Jun <var data-var='date'>22</var>, <var data-var='time'>11:37</var> UTC Investigating - We are currently investigating an issue affecting ODC users in the US East (N. Virginia) region. Users are experiencing issues accessing applications in the DEV stage and may encounter an "Upstream Request Timeout" error. Our team is actively working to resolve the issue, and we will provide updates as more information becomes available.

Incident affecting ODC applications in the DEV stage

May <var data-var='date'>25</var>, <var data-var='time'>13:37</var> UTC Resolved - This incident has been fully resolved, and the Count parameter in advanced SQL queries is now operating as expected. To ensure you benefit from this fix, please make sure you republish the affected application and deploy it to the affected stage if necessary. Thank you for your patience and understanding while we worked to resolve this matter. May <var data-var='date'>25</var>, <var data-var='time'>08:28</var> UTC Monitoring - A solution has been applied to resolve this issue. A republish of the application is required to fully apply the fix. We will continue monitoring this situation to ensure full recovery. May <var data-var='date'>23</var>, <var data-var='time'>08:07</var> UTC Update - We continue to make progress on the deployment of the fix affecting ODC services. During the final stages of the rollout and validation process, additional time was required before pipelines could be safely unfrozen and normal operations resumed. The updated estimated resolution time is now 11:00 UTC on May 25th. Users may continue to experience intermittent symptoms while mitigation and validation activities remain in progress. We are actively monitoring the situation and will continue to provide updates as additional information becomes available. May <var data-var='date'>22</var>, <var data-var='time'>23:31</var> UTC Update - We continue to deploy the fix for the issue affecting ODC and are seeing progress across the impacted services. Due to additional time required to complete the rollout safely and validate platform stability, the estimated resolution time has been updated to 07:00 UTC on May 23rd. Users may continue to experience intermittent symptoms while deployment activities are ongoing. We are closely monitoring the situation and will provide further updates as progress continues. May <var data-var='date'>22</var>, <var data-var='time'>18:58</var> UTC Update - We have identified the cause of the issue affecting ODC and a fix is currently being deployed. Users may continue to experience symptoms while the update is being implemented. We are monitoring the progress closely and aim to have the issue fully resolved by 00:00 UTC on May 23rd. May <var data-var='date'>22</var>, <var data-var='time'>14:58</var> UTC Identified - We have identified the cause of an issue affecting the Count parameter in advanced SQL queries. Customers may experience a runtime error (OS-BERT-60409 – Could not calculate the query count) and application crashes when using the Count parameter in advanced SQL queries. Additionally, we strongly recommend avoiding any redeployment or republishing of applications that use Advanced SQL in production until the issue is resolved, to prevent any potential unexpected behavior. Our team is actively working on a solution, and we will provide an update as soon as more details are available.

Is OutSystems down?

OutSystems status is DOWN

Components with issues

Lastest published events

Issue Affecting Application Publishing in Asia Pacific, Mumbai region

Incident affecting Personal Edition login in Asia Pacific (Singapore)

Incident affecting data preview in ODC Studio and runtime applications

OutSystems Services, Components and Regions

Recent OutSystems events

Issue Affecting Application Publishing in Asia Pacific, Mumbai region

Incident affecting Personal Edition login in Asia Pacific (Singapore)

Incident affecting data preview in ODC Studio and runtime applications

Authentication Issues Affecting ODC in the Israel (Tel Aviv) Region

Incident affecting password reset functionality

Ongoing authentication maintenance