OutSystems Incident History

1. postmortemSep 16 · 19:22 UTC

   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.

Reported by OutSystems on their status page.

1. postmortemSep 16 · 16:06 UTC

   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.

Reported by OutSystems on their status page.

1. ResolvedSep 15 · 12:56 UTC

   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.

Reported by OutSystems on their status page.

1. resolvedSep 11 · 16:43 UTC

   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.

Reported by OutSystems on their status page.

1. ResolvedSep 11 · 16:43 UTC

   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.

Reported by OutSystems on their status page.

1. postmortemSep 14 · 17:00 UTC

   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.

Reported by OutSystems on their status page.

1. ResolvedSep 11 · 11:56 UTC

   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.

Reported by OutSystems on their status page.

1. resolvedSep 4 · 12:47 UTC

   This incident has been resolved.

Reported by OutSystems on their status page.

1. ResolvedSep 4 · 12:47 UTC

   This incident has been resolved.

Reported by OutSystems on their status page.

1. postmortemAug 31 · 18:59 UTC

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

Reported by OutSystems on their status page.

1. postmortemAug 27 · 04:56 UTC

   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.

Reported by OutSystems on their status page.

1. postmortemAug 25 · 11:39 UTC

   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.

Reported by OutSystems on their status page.

1. postmortemAug 21 · 16:21 UTC

   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.

Reported by OutSystems on their status page.