Outsystems incident

Login Access Issue with ODC Portal

Critical Resolved View vendor source →

Outsystems experienced a critical incident on April 13, 2026 affecting US East / Virginia and Canada / Central and 1 more component, lasting 1h 6m. The incident has been resolved; the full update timeline is below.

Started
Apr 13, 2026, 02:24 AM UTC
Resolved
Apr 13, 2026, 03:30 AM UTC
Duration
1h 6m
Detected by Pingoru
Apr 13, 2026, 02:24 AM UTC

Affected components

US East / VirginiaCanada / CentralSouth America / São PauloEurope / IrelandEurope / LondonEurope / FrankfurtAfrica / Cape TownIsrael / Tel AvivMiddle East / UAEAsia Pacific / Mumbai

Update timeline

  1. investigating Apr 13, 2026, 02:24 AM UTC

    We are investigating an issue where users are unable to log into the ODC Portal. This issue is also impacting some functionality within ODC Studio. Affected users may encounter an error message stating they do not have the necessary permissions to see the content or that they cannot access the page. This incident is currently confirmed to be affecting all regions. We are working to identify the cause and will provide further updates as they become available.

  2. resolved Apr 13, 2026, 03:30 AM UTC

    The cause of this incident has been found. A new deployment of the Identity Services relied on a database schema that had not yet been updated, resulting in service unavailability and authentication failures, affecting all ODC regions. A solution has been applied by rolling back the deployment. The incident is now resolved, and services are operating as expected. We have confirmed that user applications were not affected during this time.

  3. postmortem Apr 13, 2026, 07:17 AM UTC

    On April 13,2026 between 1:13 and 3:07 AM UTC, an incident occurred that prevented users from logging in to the ODC Portal across multiple regions. The issue was caused by a deployment of a Identity Service that required a database schema change that had not yet been applied, resulting in authentication failures. Service was restored after the team initiated a rollback to the previous stable version. Validation confirmed that login functionality was restored for all users. The incident is fully resolved, and all services are operating as expected.