Outsystems incident
Incident affecting logins in Europe (Frankfurt), Europe (London), and Israel (Central)
Outsystems experienced a major incident on January 29, 2026 affecting Europe / London and Europe / Frankfurt and 1 more component, lasting 16h 42m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jan 29, 2026, 08:00 PM UTC
We are investigating an issue in ODC affecting users in Europe (Frankfurt), Europe (London), and Israel (Central). Affected users may experience login failures when attempting to access their applications. Our team is currently working to address the situation.
- investigating Jan 30, 2026, 01:28 AM UTC
We have confirmed that no additional users are being impacted at this time. Our team is continuing to investigate the situation to determine the full scope and cause.
- investigating Jan 30, 2026, 10:05 AM UTC
We are continuing to investigate this incident. Our technical teams are actively working to identify the root cause, and we will provide further information as soon as it becomes available. We appreciate your patience as we work toward a resolution.
- identified Jan 30, 2026, 12:21 PM UTC
The cause of this issue has been identified and our team is currently working on a resolution. Users may continue to experience login failures while our team works on developing a fix.
- resolved Jan 30, 2026, 12:43 PM UTC
This incident has been fully resolved and the applications login is now operating as expected. Thank you for your patience.
- postmortem Feb 06, 2026, 02:39 PM UTC
On January 30th, several ODC customers experienced intermittent issues where the username attribute was missing data from the User entity within applications. The cause was identified as a bug in a recent release of an identity component. This issue prevented specific user and identity provider data from correctly populating the Username Attribute. The incident was resolved by rolling back the affected release. A corrected version has since been deployed to ensure consistent data availability and prevent future occurrences.