Outsystems Outage History

Outsystems major outage View live status →

There were 4 Outsystems outages since March 4, 2026 totaling 12h 18m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.outsystems.com

Major April 21, 2026

Partial System outage

Detected by Pingoru
Apr 21, 2026, 02:36 AM UTC
Resolved
Apr 21, 2026, 10:19 AM UTC
Duration
7h 43m
Affected: Support Portal
Timeline · 5 updates
  1. investigating Apr 21, 2026, 02:36 AM UTC

    We are experiencing some partial infrastructure outage which is causing connection issues with some of our online tools. We will update you as soon as we have the website up and running.

  2. investigating Apr 21, 2026, 03:37 AM UTC

    We are continuing to investigate this issue.

  3. identified Apr 21, 2026, 04:17 AM UTC

    The issue has been identified and a fix is being implemented.

  4. monitoring Apr 21, 2026, 05:38 AM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Apr 21, 2026, 10:19 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical April 13, 2026

Login Access Issue with ODC Portal

Detected by Pingoru
Apr 13, 2026, 02:24 AM UTC
Resolved
Apr 13, 2026, 03:30 AM UTC
Duration
1h 6m
Affected: US East / VirginiaCanada / CentralSouth America / São PauloEurope / IrelandEurope / LondonEurope / FrankfurtAfrica / Cape TownIsrael / Tel AvivMiddle East / UAEAsia Pacific / MumbaiAsia Pacific / SingaporeAsia Pacific / JakartaAsia Pacific / Hong KongAsia Pacific / SeoulAsia Pacific / TokyoAsia Pacific / Sydney
Timeline · 3 updates
  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.

Read the full incident report →

Major March 19, 2026

Incident affecting ODC Portal and ODC Studio

Detected by Pingoru
Mar 19, 2026, 09:35 AM UTC
Resolved
Mar 19, 2026, 11:32 AM UTC
Duration
1h 56m
Affected: US East / VirginiaCanada / CentralSouth America / São PauloEurope / IrelandEurope / LondonEurope / FrankfurtAfrica / Cape TownIsrael / Tel AvivMiddle East / UAEAsia Pacific / MumbaiAsia Pacific / SingaporeAsia Pacific / JakartaAsia Pacific / Hong KongAsia Pacific / SeoulAsia Pacific / TokyoAsia Pacific / Sydney
Timeline · 5 updates
  1. investigating Mar 19, 2026, 09:35 AM UTC

    We are currently investigating an issue affecting ODC. Users may experience errors when attempting to log into the ODC Portal and ODC Studio if they use External Identity Provider. Affected users are encountering the error message: "Email verification not supported / Email verification is not supported in the current Identity Provider. (OS-ID-BIZ-40302)". The current workaround is to reactivate the built-in identity provider. Please contact Support if you want to implement this option. Our team is actively working to identify the cause and restore full functionality.

  2. investigating Mar 19, 2026, 09:46 AM UTC

    We are continuing to investigate this issue.

  3. investigating Mar 19, 2026, 11:09 AM UTC

    A solution has been applied by rolling back a recent deployment of Identity Services, and our logs indicate that the errors have ceased. We are still investigating the root cause of this issue.

  4. resolved Mar 19, 2026, 11:32 AM UTC

    The incident is now resolved and login to ODC Portal and ODC Studio is operating as expected. The issue, which prevented a subset of users from logging in, was caused by a change intended to strengthen the email verification process. We have resolved the situation by rolling back to a previous version of the services and will perform a root cause analysis to prevent a recurrence in future releases.

  5. postmortem Mar 23, 2026, 01:46 PM UTC

    On March 19th, 2026, at approximately 06:43 UTC, an issue was identified affecting ODC, where some users were unable to complete the login process for the ODC Portal and ODC Studio when using external Identity Providers. Affected users encountered an error message stating "Email verification not supported" or were blocked from accessing their accounts because the system could not verify their email addresses via the external provider's claims. The incident was caused by a configuration change intended to strictly enforce email verification from external providers. This change inadvertently bypassed a native fallback verification process that certain users relied upon when their external providers did not share specific verification data. The issue was resolved by 11:00 UTC on March 19th following a rollback to the previous service versions. To prevent recurrence, future updates to this functionality will be implemented via a gradual rollout plan, including additional validation steps to ensure all identity provider configurations are fully supported.

Read the full incident report →

Major March 4, 2026

Incident affecting app access in ODC Portal

Detected by Pingoru
Mar 04, 2026, 09:09 AM UTC
Resolved
Mar 04, 2026, 10:41 AM UTC
Duration
1h 31m
Affected: US East / VirginiaCanada / CentralSouth America / São PauloEurope / IrelandEurope / LondonEurope / FrankfurtAfrica / Cape TownIsrael / Tel AvivMiddle East / UAEAsia Pacific / MumbaiAsia Pacific / SingaporeAsia Pacific / JakartaAsia Pacific / Hong KongAsia Pacific / SeoulAsia Pacific / TokyoAsia Pacific / Sydney
Timeline · 4 updates
  1. investigating Mar 04, 2026, 09:09 AM UTC

    We are investigating an issue where users are experiencing errors when attempting to view application details within the ODC Portal. Specifically, users may encounter error code OS-CFGM-40060 during this process. Due to this behavior, users are unable to view or modify application configurations, which may prevent necessary updates or fixes to their applications. Our team is working to identify the cause and will provide further updates as they become available.

  2. identified Mar 04, 2026, 09:39 AM UTC

    We have identified the cause of the issue affecting the viewing of application details. A recent configuration update created a validation mismatch between the ODC Portal and the underlying service. We are now working to revert this change to restore normal functionality. While we apply this fix, users may still encounter error OS-CFGM-40060 when accessing the View App detail page. We will provide further updates as the resolution progresses.

  3. resolved Mar 04, 2026, 10:41 AM UTC

    This incident has been fully resolved and application access in ODC Portal is now operating as expected. Thank you for your patience.

  4. postmortem Mar 10, 2026, 11:01 AM UTC

    On March 4th, 2026, between 2:39 am and 10:29 am UTC, ODC experienced an incident that prevented users from accessing the App Detail screen and performing app configurations across all stages. The runtime of existing applications was not affected by this issue. The root cause was a subscription validation misalignment between internal APIs and ODC Portal, which resulted in errors for customers without the ODC Sentry add-on. To prevent future occurrences, we are updating ODC Portal to verify subscription status in alignment with these APIs and improving UI error handling to ensure failures like this do not obstruct the overall page experience.

Read the full incident report →

Looking to track Outsystems downtime and outages?

Pingoru polls Outsystems's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Outsystems reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Outsystems alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Outsystems for free

5 free monitors · No credit card required