Outsystems outage history

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.

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.

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.

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.

On September 16th, between approximately 14:05 and 18:17 UTC, users with environments in the Israel \(Tel Aviv\) region were unable to sign in to the ODC Portal and ODC Studio, and applications hosted in the region were unavailable to their end users. The incident was caused by an infrastructure disruption at our cloud provider that affected database availability in the region. Both our identity services, which handle user sign-in, and the applications hosted in the region rely on this database layer, which is why sign-in and application access failed at the same time. We engaged our cloud provider, who identified the cause on their side and worked to restore the affected service. Services began to recover from 17:43 UTC and were fully restored by 18:17 UTC. We monitored the platform and validated recovery with the affected customers before resolving the incident. We are reviewing this incident together with our cloud provider to understand the disruption in more detail and to assess how the resilience of our services in this region can be improved. We apologise for any disruption caused and thank you for your patience.

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.

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.

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.

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.

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.

On September 11th, 2026, following an update to the shared login for OutSystems Personal Edition and the OutSystems Community website, a number of accounts became unable to log in or reset their password, even with the correct credentials. Only Personal Edition and Community website accounts were affected; other OutSystems ODC tenants were not impacted. The cause was a mismatch, for a subset of accounts, between stored account email information and the identifier used during authentication, which the login flow surfaced to users as an incorrect verification code rather than pointing to the underlying account data. We published our first public update on September 14th, applied a data correction to the affected accounts in production later that day, and confirmed recovery directly with affected customers before marking the incident Resolved on September 15th. We are putting additional safeguards in place, including monitoring for authentication and password-reset failures on this login flow and extra validation ahead of future login changes, to catch and resolve issues like this more quickly going forward. We apologise for the disruption this caused and thank you for your patience.

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.

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.

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.

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.

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.

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.

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.

Between September 10th and September 11th, 2026, customers experienced an issue affecting the Logs page in ODC Portal, where browsing beyond the first page would still show logs from the first page of results. This issue affected every region and Stage. No log data was lost, the issue only affected the ability to browse beyond the first page of results. This issue was detected through customer reports, and our team reproduced the behaviour internally to confirm its scope. The root cause was identified as a defect introduced by a recent update to the Logs pagination logic, which caused the same set of results to be returned regardless of which page was requested. A fix was developed, tested, and rolled out across all affected regions, with full recovery confirmed on September 11th, 2026, at 11:56 UTC. Following this incident, we are working to reduce the time it takes for validated fixes to reach production for confirmed customer-impacting issues, and strengthening our testing and internal review processes to catch this type of defect before it reaches production. We apologise for any disruption caused and thank you for your patience.

We have identified an issue affecting npm audit actions during npm installations and are currently working on a fix.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

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.

We are continuing to investigate this issue.

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.

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.

_Between August 28th and August 31st, 2026, users in the Asia Pacific \(Sydney\) region were unable to use Mentor in ODC Studio. Connection attempts returned an error stating, "Mentor couldn't connect. Please go online and try again." Deployed applications and other ODC Studio functionality were not affected._ _As part of planned regional infrastructure work, Mentor connection requests from affected environments began being sent to a new regional destination. The services needed to handle those requests had not yet been deployed there, so every connection attempt failed. The change was applied ahead of those services becoming available._ _The issue was detected through customer reports. Automated monitoring did not alert on it, because connection requests were being sent to a destination where the supporting service was not yet running, so no failure signals were generated for our monitoring to detect._ _To restore service, we reversed the configuration change on a single environment and confirmed that Mentor connected successfully, then applied the same reversal across all affected environments. We verified recovery with each of the customers who had reported the issue._ _To prevent recurrence, the regional infrastructure work will not resume until all dependent services are available in the region. We are strengthening the validation applied before configuration updates of this kind, so that a change cannot be made ahead of the services it depends on. We are also reviewing our monitoring so that failures of this type are detected automatically rather than through customer reports._ _We apologise for any disruption caused and thank you for your patience._

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.

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.

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.

On August 26th, between 05:16 UTC and 16:26 UTC, some ODC users experienced delays in the execution of timers. Affected timers remained pending instead of running as scheduled, and subsequent runs did not start. Users in US East / Virginia and Asia Pacific / Singapore were affected. Applications themselves remained available throughout. The issue was caused by a recent platform update that changed how a timer's status is recorded once it has run. Under that update, a timer whose status needed to be recorded more than once in sequence failed to update correctly, leaving it pending and blocking later scheduled executions. To restore service, our team returned the affected part of the platform to its previous version, which stopped the issue recurring for affected users. A permanent correction was then developed, validated and deployed across the platform, and we confirmed that timers were executing normally before closing the incident. We are reviewing our monitoring of timer execution so that issues of this kind are detected automatically rather than through customer reports. We apologise for any disruption caused and thank you for your patience.

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.

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.

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.

On August 24th, 2026, some users experienced an issue affecting application deployments in ODC Portal. Affected users intermittently saw the error message: "An error occurred while getting the generated code from revision. \(OS-STGC-60005\)". The issue was caused by an internal scaling tool that interfered with a backend service used to prepare deployment packages, causing delays and errors for some deployment requests. We fixed the scaling configuration to restore normal behavior. To prevent a recurrence, we are working with the provider of the automated scaling tool to correct the underlying behavior, and have put a permanent safeguard in place to stop the affected service from being mismanaged by that tool going forward. We apologize for any disruption caused and thank you for your patience.

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.

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.

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.

Between 20 August 9:52 UTC and 21 August 13:22 UTC, some users were unable to generate or edit applications using Mentor in the ODC Portal, and received the error OS-IDE-CONVERSATIONAL-50035. The issue was caused by an outdated permission check that remained in place after a recent change to how the service communicates internally. We removed the outdated check and confirmed that the Mentor App Generator App Editor recovered across the affected regions. We apologise for the disruption this caused.

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.

This incident has been resolved.

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.

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.

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.

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.

On August 12th, 2026, at approximately 02:56 UTC, we received our first customer report regarding an issue that affected the Application Configuration and IP Filter List features, resulting in these areas failing to load for a number of customers. Application publishing and runtime were not affected. Customers saw the error codes OS-APPC-60043 and OS-CFGC-GEN-60030. This prevented some users from completing required application configuration changes. Normal service was restored at 08:00 UTC. It was caused by a recent update to an internal service that provides configuration data. The update unintentionally changed how requests were routed between instances of that service, so most requests for IP filter information reached an instance that could not answer them and timed out. Our team identified the faulty update and rolled it back across all environments to restore normal behavior. We are improving our pre-release testing and monitoring so that this type of issue is caught before it reaches production, and adding monitoring coverage specifically for this failure mode.

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.

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.

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.

On August 10th, 2026, from 20:31 to 22:19 UTC, users in the South America / São Paulo region experienced errors when signing in to ODC. This prevented affected users from accessing their Production applications and also affected the ODC Portal and ODC Studio. The issue was detected through customer reports and monitoring. Our investigation found that a fault in an internal caching component of our identity service was preventing it from issuing sign-in tokens, even though the service otherwise appeared to be running normally. To restore service, our team restarted the affected identity service, which cleared the fault and allowed token issuance to resume. We confirmed with affected customers that sign-in and application access had returned to normal before closing the incident. We have identified additional monitoring and preventive improvements for this component and are prioritising their rollout to help reduce the risk of similar issues recurring. We apologise for any disruption caused and thank you for your patience.

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.

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 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 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.

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.

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.

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 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.

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.

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 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 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 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.

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 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.

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.

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.

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.

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.

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.

On June 26, 2026, a code deployment intended to improve our system's infrastructure inadvertently introduced a sorting issue that affected the deployment stage ordering on the ODC platform. This issue prevented several customers from deploying applications through their expected deployment stages. We identified the root cause on June 29 and immediately implemented a fast-track fix. When further investigation revealed the issue persisted for additional customers due to a deeper underlying cause, we deployed a comprehensive fix on June 30 that fully resolved the problem across all affected tenants. All impacted customers have been verified as fully operational, and their applications can now be deployed normally through all stages.

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.

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.

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.

We are continuing to work on a fix for this issue.

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.

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.

On June 26, 2026, a code deployment intended to improve our system's infrastructure inadvertently introduced a sorting issue that affected the deployment stage ordering on the ODC platform. This issue prevented several customers from deploying applications through their expected deployment stages. We identified the root cause on June 29 and immediately implemented a fast-track fix. When further investigation revealed the issue persisted for additional customers due to a deeper underlying cause, we deployed a comprehensive fix on June 30 that fully resolved the problem across all affected tenants. All impacted customers have been verified as fully operational, and their applications can now be deployed normally through all stages.

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.

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.

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.

This incident has been fully resolved. Services are now operating as expected, and users can successfully deploy their apps without encountering the previous error.

On June 24th, an issue occurred that impacted ODC application deployments for non-administrator users across multiple regions, including Asia Pacific and Europe. Affected users experienced failures when attempting to deploy applications to higher stages and received an error during the build preparation step. Administrator accounts were not affected. The issue was caused by a configuration change deployed on June 23rd, which introduced a technical mismatch in how permission roles were validated within the build pipeline, preventing non-admin users from initiating deployments. The engineering team identified the root cause and reversed the change. Deployments are now functioning normally for all affected users. We are conducting a post-incident review to prevent similar issues from occurring in the future.

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.

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.

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.

On June 22nd, an incident affected ODC users in the US East \(N. Virginia\) region. Users were unable to access any applications in the Development stage, receiving an "Upstream Request Timeout" error. Production and Test stages, as well as all other regions, were unaffected. The incident was caused by a platform configuration change that prevented the component responsible for starting idle Development-stage applications on demand from functioning. As a result, when a request arrived, the application failed to start, causing the connection to time out at the gateway. The issue was resolved by reverting the configuration change. The component fully recovered, app startup resumed, and normal service operation was verified.