Outsystems incident

Incident Affecting ODC Personal Edition User Logins

Major Resolved View vendor source →

Outsystems experienced a major incident on November 25, 2025 affecting Europe / Ireland and Asia Pacific / Singapore, lasting 4h 29m. The incident has been resolved; the full update timeline is below.

Started
Nov 25, 2025, 12:37 PM UTC
Resolved
Nov 25, 2025, 05:06 PM UTC
Duration
4h 29m
Detected by Pingoru
Nov 25, 2025, 12:37 PM UTC

Affected components

Europe / IrelandAsia Pacific / Singapore

Update timeline

  1. identified Nov 25, 2025, 12:37 PM UTC

    We are currently investigating an issue preventing some ODC Personal Edition users from logging in. Affected users may see the error message “Incorrect username or password (OS-UAUC-60004)” even when using their correct community credentials. Our team is actively working to identify the cause. We will share an update as soon as more information becomes available.

  2. resolved Nov 25, 2025, 05:06 PM UTC

    We experienced an issue that prevented some users from logging in to their Personal Editions across multiple regions. This affected tenants created between November 17 and 18 and assigned on November 22. The problem was caused by an incomplete internal configuration during setup, which blocked the login process. Our team has corrected the configuration for all affected tenants, and access has now been fully restored. Thank you for your patience while we resolved this issue.

  3. postmortem Dec 10, 2025, 11:11 AM UTC

    On November 25th, around 11:15 UTC, we experienced an issue affecting Personal Editions, resulting in users being unable to log in and consistently seeing the error “Incorrect username or password \(OS-UAUC-60004\)” despite using valid credentials in the regions of US East \(Ohio\), Europe \(Ireland\), and Asia Pacific \(Singapore\). Normal service was restored by approximately 17:00 UTC the same day. The incident was caused by an issue in provisioning that led Personal Editions to not have the built-in community provider configured as an Identity Provider. This resulted in the login failures when users attempted to access their Personal Editions. To prevent new occurrences, the provisioning logic was updated to treat a similar empty response as an error, triggering an internal alert and preventing affected environments from being handed out as ready-to-use. Additionally, a targeted reconfiguration job was run to correctly apply the required identity provider to all impacted Personal Editions, which restored normal login functionality