https://approjects-vendor-status-watch.static.hf.space/v/outsystems.htmlIncidents from Outsystems's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://stspg.io/h51gqpqqc9zhoutsystems:2026-09-14T11:07:42.121ZMon, 14 Sep 2026 11:07:42 +0000The 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.https://stspg.io/hmg0b09knzc6outsystems:2026-09-11T12:47:15.000ZFri, 11 Sep 2026 12:47:15 +0000The 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.https://stspg.io/7ssr1zclzrs8outsystems:2026-09-11T06:23:17.198ZFri, 11 Sep 2026 06:23:17 +0000Between 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, https://stspg.io/c5xghzgxc8lyoutsystems:2026-09-04T11:15:06.692ZFri, 04 Sep 2026 11:15:06 +0000This incident has been resolved.https://stspg.io/5rx4z4hz5p9youtsystems:2026-08-31T15:28:49.850ZMon, 31 Aug 2026 15:28:49 +0000_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 destinatihttps://stspg.io/tkcdgqxgq4nzoutsystems:2026-08-26T05:16:49.409ZWed, 26 Aug 2026 05:16:49 +0000On 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 correctihttps://stspg.io/khdrc2zlc3s4outsystems:2026-08-24T14:57:08.453ZMon, 24 Aug 2026 14:57:08 +0000On 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 phttps://stspg.io/ntdjqnjrrlhroutsystems:2026-08-21T10:54:59.659ZFri, 21 Aug 2026 10:54:59 +0000Between 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.https://stspg.io/45rnhzv390cgoutsystems:2026-08-12T16:56:12.323ZWed, 12 Aug 2026 16:56:12 +0000This incident has been resolved.https://stspg.io/wcwk8z12j21youtsystems:2026-08-12T05:41:29.472ZWed, 12 Aug 2026 05:41:29 +0000On 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 idehttps://stspg.io/kb0jdx8tj3yboutsystems:2026-08-10T20:48:01.967ZMon, 10 Aug 2026 20:48:01 +0000On 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 https://stspg.io/qyc01hd3t73moutsystems:2026-07-31T08:31:58.000ZFri, 31 Jul 2026 08:31:58 +0000On 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 https://stspg.io/p13qwvwtmc3noutsystems:2026-07-30T18:39:10.882ZThu, 30 Jul 2026 18:39:10 +0000On 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 wohttps://stspg.io/hk3hjs3s5ssmoutsystems:2026-07-21T02:13:51.671ZTue, 21 Jul 2026 02:13:51 +0000On 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 'hhttps://stspg.io/1zs69723rtxmoutsystems:2026-07-20T11:46:15.940ZMon, 20 Jul 2026 11:46:15 +0000This 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.https://stspg.io/thsy1h69sgw2outsystems:2026-06-30T08:56:27.789ZTue, 30 Jun 2026 08:56:27 +0000On 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.https://stspg.io/wh6y61qnc6zfoutsystems:2026-06-29T04:28:44.715ZMon, 29 Jun 2026 04:28:44 +0000On 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.https://stspg.io/ks3lkjzz0wymoutsystems:2026-06-25T08:44:37.103ZThu, 25 Jun 2026 08:44:37 +0000On 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 occurrhttps://stspg.io/y3cytpywx6dmoutsystems:2026-06-22T11:37:51.203ZMon, 22 Jun 2026 11:37:51 +0000On 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.https://stspg.io/2pvnc4dsgk7qoutsystems:2026-05-22T14:58:38.280ZFri, 22 May 2026 14:58:38 +0000On May 22, 2026, we deployed an update intended to improve internal diagnostics. This update added automatic comments to generated SQL statements. In a specific edge case, where count-based queries were used inside nested SQL statements, these added comments disrupted the structure of the query and caused it to fail. Affected applications returned runtime errors and certain database queries could not complete successfully. After deploying a fix for this, services were restored and all affected queries are now functioning normally. We appreciate your patience while this was being resolved and remain committed to continuously improving the stability and reliability of the platform.https://stspg.io/vzdrnh3344nqoutsystems:2026-05-08T11:56:03.115ZFri, 08 May 2026 11:56:03 +0000On May 8, 2026, at 12:03 AM UTC, ODC and O11 Personal Environments in the N. Virginia region experienced a service disruption caused by an AWS infrastructure event affecting a single Availability Zone. The disruption was related to an external power and cooling issue that impacted the availability of underlying AWS services. Customers experienced service unavailability, including issues with logging in and publishing applications.The impact was limited to O11 Personal Environments and a small subset of users, while impact on ODC remained contained. As AWS services recovered, many OutSystems environments resumed normal operation automatically. Some environments required additional recovery actions to fully restore service availability. For ODC, the incident was fully resolved on May 9https://stspg.io/ryg03swwwm4soutsystems:2026-04-21T02:36:07.374ZTue, 21 Apr 2026 02:36:07 +0000This incident has been resolved.https://stspg.io/1qgrp5z7cl8loutsystems:2026-04-13T02:24:21.692ZMon, 13 Apr 2026 02:24:21 +0000On April 13,2026 between 1:13 and 3:07 AM UTC, an incident occurred that prevented users from logging in to the ODC Portal across multiple regions. The issue was caused by a deployment of a Identity Service that required a database schema change that had not yet been applied, resulting in authentication failures. Service was restored after the team initiated a rollback to the previous stable version. Validation confirmed that login functionality was restored for all users. The incident is fully resolved, and all services are operating as expected.https://stspg.io/nrj6s3sx1598outsystems:2026-03-29T01:06:32.583ZSun, 29 Mar 2026 01:06:32 +0000The issues affecting our services have been resolved, and all systems are now operating normally. We apologize for any disruption this may have caused to your workflows.https://stspg.io/dk0zwwqlzsr0outsystems:2026-03-19T09:35:30.445ZThu, 19 Mar 2026 09:35:30 +0000On March 19th, 2026, at approximately 06:43 UTC, an issue was identified affecting ODC, where some users were unable to complete the login process for the ODC Portal and ODC Studio when using external Identity Providers. Affected users encountered an error message stating "Email verification not supported" or were blocked from accessing their accounts because the system could not verify their email addresses via the external provider's claims. The incident was caused by a configuration change intended to strictly enforce email verification from external providers. This change inadvertently bypassed a native fallback verification process that certain users relied upon when their external providers did not share specific verification data. The issue was resolved by 11:00 UTC on March 19th https://stspg.io/5lzx2hk4ny46outsystems:2026-03-04T09:09:44.870ZWed, 04 Mar 2026 09:09:44 +0000On March 4th, 2026, between 2:39 am and 10:29 am UTC, ODC experienced an incident that prevented users from accessing the App Detail screen and performing app configurations across all stages. The runtime of existing applications was not affected by this issue. The root cause was a subscription validation misalignment between internal APIs and ODC Portal, which resulted in errors for customers without the ODC Sentry add-on. To prevent future occurrences, we are updating ODC Portal to verify subscription status in alignment with these APIs and improving UI error handling to ensure failures like this do not obstruct the overall page experience.https://stspg.io/4242zfq5sgr1outsystems:2026-03-01T16:33:04.355ZSun, 01 Mar 2026 16:33:04 +0000All 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.https://stspg.io/5qpcjnf89y3goutsystems:2026-01-29T20:00:44.115ZThu, 29 Jan 2026 20:00:44 +0000On January 30th, several ODC customers experienced intermittent issues where the username attribute was missing data from the User entity within applications. The cause was identified as a bug in a recent release of an identity component. This issue prevented specific user and identity provider data from correctly populating the Username Attribute. The incident was resolved by rolling back the affected release. A corrected version has since been deployed to ensure consistent data availability and prevent future occurrences.https://stspg.io/slyjjtjmn2rroutsystems:2026-01-27T12:53:02.416ZTue, 27 Jan 2026 12:53:02 +0000On January 27th, we experienced a service disruption in Mentor affecting APAC and EMEA regions. Users encountered elevated error rates and a loss of functionality for Mentor features. The incident was triggered by a third-party service outage, which hosts the models supporting our Data & AI services. While a fallback system was in place, it also became unavailable during the outage. Furthermore, the impact of the external service disruption also prevented our team from implementing a manual configuration fix immediately. We are also working toward an automated fallback mechanism to minimize the need for manual intervention. Additionally, we are implementing agent-level fallbacks to different models at the product level.https://stspg.io/xww82jbr7zdgoutsystems:2026-01-22T15:29:09.888ZThu, 22 Jan 2026 15:29:09 +0000On January 22nd, between 15:00 UTC and 17:00 UTC, an incident affected ODC in the Europe \(Frankfurt\) region. Users experienced issues with One-Click Publish, specifically resulting in build timeouts and publish failures. The issue was caused by a communication failure between the internal queuing system and the Build Service, which prevented build processes from completing. Our team resolved the incident by restarting the Build Service and restoring communication. Normal service has been restored, and we are evaluating measures to improve system resilience moving forward.