Who is down right now

26 down now · 292 this week

OutSystems · Apps and SaaSSep 29, 2026, 09:00 UTC 7 weeks ago

Incident affecting Personal Edition login in Asia Pacific (Singapore)

MajorConfig changeUpdated 4d ago
Sep 29, 09:00 UTCSep 30, 13:40 UTC
Duration
28h 39m
Impact
Major
Root cause
Config change
OutSystems, 90 days
16 incidents
Affected
Identity & Access ManagementOutSystems Personal Edition - Identity & Access Management
Status page

Final update

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.

Timeline

  1. Postmortem · Sep 30, 13:56 UTC
    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.
  2. Resolved · Sep 30, 13:40 UTC
    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.
  3. Identified · Sep 29, 18:23 UTC
    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.
  4. Identified · Sep 29, 11:41 UTC
    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.
  5. Investigating · Sep 29, 09:00 UTC
    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.

More from OutSystems

Full history

Also caused by configuration change

All