Is Outsystems down?

We are currently investigating an issue affecting Forge in the ODC portal. Users in the EMEA and APAC regions may experience errors when accessing Forge in ODC Portal, displaying the message: "Sorry, something went wrong. Try refreshing the page. If the problem persists, let us know. (OS-FRGE-GEN-60028)". The Public Forge and Forge in O11 are working as expected. Our team is actively working on a solution. We will provide an update once more details are available.

A fix has been applied to address the issue affecting Forge in the ODC Portal. Upon applying the fix, we confirmed this was also affecting other components in ODC Portal, such as the configuration of custom domains. Users may have experienced slowness or errors when accessing these areas of ODC Portal. This is no longer occurring and we are closely monitoring the platform to confirm full recovery. We will provide updates as more information becomes available.

The issue affecting Forge and other components of the ODC Portal in the EMEA and APAC regions has been resolved. Users may have experienced errors or slower performance when accessing certain areas of ODC Portal. The cause was a maintenance-related configuration issue in our underlying infrastructure, and all services are now operating as expected. Our team is continuing to work on measures to help prevent future recurrences. We apologise for any disruption caused and thank you for your patience.

On October 23rd, 2026, between 06:40 and 09:50 UTC, users in the EMEA and APAC regions experienced an issue affecting Forge in ODC Portal, which was unavailable and displayed an error when accessed. Other areas of ODC Portal that depend on communication between regions were also affected, with users experiencing errors or slower performance in those areas as well. The cause was routine maintenance on underlying servers, during which a traffic-routing setting directed most traffic to a single server that could not keep up with the load. This disrupted communication between regions. The issue was first reported by customers. Once our team returned the affected part of our internal messaging infrastructure to normal operation at 9:50 UTC, normal service was restored. To prevent a recurrence, we are correcting the routing setting so that traffic is always spread across all available servers, and adding monitoring that alerts us within minutes if a similar situation occurs. We apologise for any disruption caused and thank you for your patience.

We are investigating an issue where users are unable to sign in to ODC Portal, ODC Studio and applications in runtime. Users may receive an “Incorrect Username or password” error message when using seemingly valid credentials. This also prevents the successful reset of passwords. This issue is affecting multiple customers. As a workaround, affected users should sign in (or request a password reset if required) using an email address entirely in lowercase letters. This should completely mitigate the issue for that user. If these issues persist when using all-lowercase emails, it should not be related to this issue. Our team is actively working to resolve the problem as quickly as possible and will provide updates as more information becomes available.

We have identified the cause of the issue affecting user sign-in and password resets on ODC, and a fix has been developed and is now being rolled out. Until the fix has reached all affected users, sign-in problems may persist. In the meantime, affected users should continue to sign in (or request a password reset if required) using an email address entirely in lowercase letters. This should completely mitigate the issue for that user. We will provide updates as more information becomes available.

A fix has been applied for the issue affecting sign-in to ODC across multiple regions. Users of affected organisations should now be able to log in to ODC and to their applications using built-in authentication as normal, without needing to enter their email address in lowercase. We are monitoring the platform and confirming recovery with affected users.

This incident has been resolved. Sign-in and password resets on ODC are expected to work as normal since we applied the fix. If you continue to experience sign-in issues, please contact OutSystems Support. We apologize for any disruption caused and thank you for your patience.

On October 12th, we identified an issue where some users were unable to sign in to ODC, or to reset their passwords, despite using valid credentials. The issue affected users across multiple regions. The issue was caused by a defect in how email addresses were handled during sign-in, which caused sign-in and password reset attempts to fail for some users whose email address contained uppercase letters. To restore service, we communicated a workaround, which was to use their email address entirely in lowercase letters, and paused further related changes. A fix for this defect was deployed on October 12th, and service was confirmed as restored on October 13th. To prevent a recurrence, any further related changes will only proceed once they have been validated against the fix and formally approved. We are also improving our monitoring so that this type of sign-in issue is detected and escalated to the responsible teams sooner. We apologize for any disruption caused and thank you for your patience.

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.

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.

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.

On October 5th, 2026, we experienced an issue affecting application publishing in ODC in the Asia Pacific, Mumbai region. The issue was first reported at approximately 08:39 UTC. Users experienced intermittent failures when publishing applications from ODC Studio, with an error related to fetching application configurations. Some users also saw related errors when viewing application configurations in ODC Portal. Service was fully restored at approximately 11:22 UTC. The issue was caused by a fault in one of our internal platform components serving the region, which stopped it from responding to some of the requests needed to publish applications. Because only some requests were affected, failures were intermittent and did not impact every user at all times. The issue was detected through customer reports. Our team investigated, identified the affected component and restored it, after which publishing returned to normal. We apologise for any disruption caused and thank you for your patience.

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.

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.

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.

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.

On September 29th, starting at approximately 8:53 AM UTC, we experienced an issue affecting ODC users across multiple regions. Users were unable to preview data in ODC Studio. Despite early suspicions of impact in runtime, our investigation did not find evidence that running applications were actually affected. The issue was detected through customer reports. Our investigation identified a recent software update related to database authentication as the source of the issue. In certain circumstances, the update caused database authentication to fail when users previewed data in ODC Studio. The conditions that triggered the problem were not present in our earlier test environments, so it was not caught before the update reached production. Rolling the update back restored normal operation, and we are finalising confirmation of the precise mechanism as part of our post-incident review. Error rates fell sharply from approximately 11:24 UTC, once the fix was applied. Recovery was then confirmed with affected users later that day. We continued to monitor the platform and marked the incident as resolved on September 30th, with no further impact. To prevent a recurrence, a corrected version of the update has been developed and is being reviewed, and related changes will not proceed until it has been validated. We apologise for any disruption caused and thank you for your patience.

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.

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.

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.

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.

Between September 17th and September 30th, 2026, a limited number of ODC Personal Edition users in the Asia Pacific \(Singapore\) region were unable to log in to their Personal Editions and encountered the error message "Login with external provider failed." The issue was caused by a configuration update related to the external login provider that did not apply correctly for the affected Personal Editions, leaving them unable to complete the login process. It was detected through user reports. Once the cause was identified, our team restored the correct configuration for the affected Personal Editions, and users were able to log in again. Service was fully restored on September 30th. We are continuing to investigate why the configuration update did not apply correctly, so that we can prevent it from happening again. We apologise for any disruption caused and thank you for your patience.