Is Outsystems down?

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.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

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.

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