OutSystems Status

Identified: Most affected O11 Cloud customers in the Middle East (Bahrain) region have been mitigated, and overall stability has improved. The AWS outage remains ongoing. We are continuing to actively monitor AWS updates to ensure full service recovery. Further updates will be provided directly to affected users via their individual support tickets. Customers requiring additional assistance are encouraged to contact OutSystems Support by raising a new ticket or following their existing cases through the Support Portal.

Identified: We are investigating reports of service disruption affecting O11 Cloud customer in the Middle East (Bahrain) region. We are currently reaching out to impacted customers directly and will provide further updates as more information becomes available.

Identified: Recovery efforts for the Middle East (UAE) remain ongoing as cloud infrastructure providers work to restore impacted services. ODC organizations remain unavailable while these restoration efforts continue. We are continuing tracking the recovery process of this incident to ensure a complete recovery. Going forward, updates will be delivered directly to affected users through their individual support tickets. Users who require further assistance with this event are encouraged to contact OutSystems Support by raising a new ticket or following their existing cases through the Support Portal.

Identified: Recovery efforts for the Middle East (UAE) remain ongoing as cloud infrastructure providers work to restore impacted services. ODC organizations remain unavailable while these restoration efforts continue. We are closely tracking the progress and will provide further updates as more information becomes available.

Identified: Recovery efforts for the Middle East (UAE) region remain ongoing as cloud infrastructure providers work to restore impacted services. We continue to track the recovery progress and will provide further updates as more information becomes available.

Identified: Recovery efforts are still underway for the Middle East (UAE) as cloud services work to restore one of the affected areas. We are continuing to track the progress and will provide further updates as more information becomes available.

Identified: We are continuing to monitor the recovery of ODC services in the Middle East (UAE) as the underlying infrastructure issues are being addressed. We will provide further updates as soon as more information becomes available.

Identified: Update - We are continuing to monitor the progress of recovery efforts in the affected region. We will provide further information as soon as more details become available.

Monitoring: Update - We are continuing to monitor the progress of recovery efforts in the affected region. We will provide further information as soon as more details become available.

Identified: Recovery efforts are still being prioritized by AWS for this region, focusing on restoration of the impacted AWS Services. We are closely monitoring the situation and will provide further updates once they become available.

Identified: The cause has been identified as a widespread infrastructure failure in the Middle East (UAE) affecting foundational AWS services. While recovery efforts are underway, ODC and other services in this region will remain unavailable until the underlying infrastructure is fully restored.

We are closely monitoring the situation as it recovers and will provide further information once it becomes available.

Investigating: We are still continuing to monitor the investigation with AWS, as the recovery towards the impaired AWS Middle East (UAE) Region is still ongoing. While there have been significant improvements made so far, the estimated recovery time will take at least another day before power and connectivity can be restored.

Investigating: We continue to follow closely the investigation in partnership with AWS, towards the recovery of the Middle East (UAE) Region. At this point, we are expecting recovery to take at least a day given the significant efforts required. Until then, ODC and other services in this region will continue experiencing a total service outage. We continue to monitor the situation closely and will provide updates as more information becomes available.

Investigating: We are investigating an issue affecting Outsystems Products in the Middle East (UAE) region. This disruption is related to the ongoing AWS service incident reported on March 1st.

Users in this region are currently experiencing a total service outage in ODC, and all services are unavailable. We are monitoring the situation closely and will provide updates as more information becomes available.

Investigating: We are currently investigating this issue.

Monitoring: Our services have been fully restored, and the issue affecting our OutSystems customers has been mitigated. While the ongoing disruption reported by AWS continues, it is not expected to impact our customers at this time. We will continue to closely monitor the situation. If you experience any issues, please contact our Support team.

For updates directly from AWS, please visit: https://health.aws.amazon.com/health/status

Identified: We are continuing to monitor the official AWS status page. At this time, AWS has informed customers that some may experience errors when performing certain network-related actions.

AWS is actively implementing mitigation measures, and recovery is expected within the next few hours.

Identified: AWS Team has identified the cause of the disruption affecting one availability zone in the Middle East (UAE) region. Power was temporarily shut down at the facility as a safety precaution.

Restoration of power and connectivity may take several hours. Other availability zones in the region remain operational.

We will provide further updates as more information becomes available.

Investigating: We are currently experiencing service degradation in the Middle East (UAE) region due to connectivity and power issues within a major cloud provider (AWS).

We are actively monitoring the situation and following updates from the official AWS status page. Our team is closely tracking recovery progress. We will provide further updates as more information becomes available.

Identified: Most affected O11 Cloud customers in the Middle East (Bahrain) region have been mitigated, and overall stability has improved. The AWS outage remains ongoing. We are continuing to actively monitor AWS updates to ensure full service recovery. Further updates will be provided directly to affected users via their individual support tickets. Customers requiring additional assistance are encouraged to contact OutSystems Support by raising a new ticket or following their existing cases through the Support Portal.

Identified: We are investigating reports of service disruption affecting O11 Cloud customer in the Middle East (Bahrain) region. We are currently reaching out to impacted customers directly and will provide further updates as more information becomes available.

Identified: Recovery efforts for the Middle East (UAE) remain ongoing as cloud infrastructure providers work to restore impacted services. ODC organizations remain unavailable while these restoration efforts continue. We are continuing tracking the recovery process of this incident to ensure a complete recovery. Going forward, updates will be delivered directly to affected users through their individual support tickets. Users who require further assistance with this event are encouraged to contact OutSystems Support by raising a new ticket or following their existing cases through the Support Portal.

Identified: Recovery efforts for the Middle East (UAE) remain ongoing as cloud infrastructure providers work to restore impacted services. ODC organizations remain unavailable while these restoration efforts continue. We are closely tracking the progress and will provide further updates as more information becomes available.

Identified: Recovery efforts for the Middle East (UAE) region remain ongoing as cloud infrastructure providers work to restore impacted services. We continue to track the recovery progress and will provide further updates as more information becomes available.

Identified: Recovery efforts are still underway for the Middle East (UAE) as cloud services work to restore one of the affected areas. We are continuing to track the progress and will provide further updates as more information becomes available.

Identified: We are continuing to monitor the recovery of ODC services in the Middle East (UAE) as the underlying infrastructure issues are being addressed. We will provide further updates as soon as more information becomes available.

Identified: Update - We are continuing to monitor the progress of recovery efforts in the affected region. We will provide further information as soon as more details become available.

Monitoring: Update - We are continuing to monitor the progress of recovery efforts in the affected region. We will provide further information as soon as more details become available.

Identified: Recovery efforts are still being prioritized by AWS for this region, focusing on restoration of the impacted AWS Services. We are closely monitoring the situation and will provide further updates once they become available.

Identified: The cause has been identified as a widespread infrastructure failure in the Middle East (UAE) affecting foundational AWS services. While recovery efforts are underway, ODC and other services in this region will remain unavailable until the underlying infrastructure is fully restored.

We are closely monitoring the situation as it recovers and will provide further information once it becomes available.

Investigating: We are still continuing to monitor the investigation with AWS, as the recovery towards the impaired AWS Middle East (UAE) Region is still ongoing. While there have been significant improvements made so far, the estimated recovery time will take at least another day before power and connectivity can be restored.

Investigating: We continue to follow closely the investigation in partnership with AWS, towards the recovery of the Middle East (UAE) Region. At this point, we are expecting recovery to take at least a day given the significant efforts required. Until then, ODC and other services in this region will continue experiencing a total service outage. We continue to monitor the situation closely and will provide updates as more information becomes available.

Investigating: We are investigating an issue affecting Outsystems Products in the Middle East (UAE) region. This disruption is related to the ongoing AWS service incident reported on March 1st.

Users in this region are currently experiencing a total service outage in ODC, and all services are unavailable. We are monitoring the situation closely and will provide updates as more information becomes available.

Investigating: We are currently investigating this issue.

Monitoring: Our services have been fully restored, and the issue affecting our OutSystems customers has been mitigated. While the ongoing disruption reported by AWS continues, it is not expected to impact our customers at this time. We will continue to closely monitor the situation. If you experience any issues, please contact our Support team.

For updates directly from AWS, please visit: https://health.aws.amazon.com/health/status

Identified: We are continuing to monitor the official AWS status page. At this time, AWS has informed customers that some may experience errors when performing certain network-related actions.

AWS is actively implementing mitigation measures, and recovery is expected within the next few hours.

Identified: AWS Team has identified the cause of the disruption affecting one availability zone in the Middle East (UAE) region. Power was temporarily shut down at the facility as a safety precaution.

Restoration of power and connectivity may take several hours. Other availability zones in the region remain operational.

We will provide further updates as more information becomes available.

Investigating: We are currently experiencing service degradation in the Middle East (UAE) region due to connectivity and power issues within a major cloud provider (AWS).

We are actively monitoring the situation and following updates from the official AWS status page. Our team is closely tracking recovery progress. We will provide further updates as more information becomes available.

Postmortem: 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.

Resolved: 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.

Investigating: 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.

Postmortem: 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.

Resolved: 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.

Investigating: 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.

Postmortem: 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.

Resolved: 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.

Investigating: 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.

Postmortem: 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.

Resolved: 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.

Investigating: 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.

Postmortem: 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.

Resolved: 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.

Investigating: 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.

Postmortem: 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.

Resolved: 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.

Investigating: 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.

Postmortem: 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.

Resolved: 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.

Investigating: 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.

Postmortem: 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.

Resolved: 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.

Investigating: 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.

Postmortem: 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.

Resolved: 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.

Investigating: 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.

Identified: Most affected O11 Cloud customers in the Middle East (Bahrain) region have been mitigated, and overall stability has improved. The AWS outage remains ongoing. We are continuing to actively monitor AWS updates to ensure full service recovery. Further updates will be provided directly to affected users via their individual support tickets. Customers requiring additional assistance are encouraged to contact OutSystems Support by raising a new ticket or following their existing cases through the Support Portal.

Identified: We are investigating reports of service disruption affecting O11 Cloud customer in the Middle East (Bahrain) region. We are currently reaching out to impacted customers directly and will provide further updates as more information becomes available.

Identified: Recovery efforts for the Middle East (UAE) remain ongoing as cloud infrastructure providers work to restore impacted services. ODC organizations remain unavailable while these restoration efforts continue. We are continuing tracking the recovery process of this incident to ensure a complete recovery. Going forward, updates will be delivered directly to affected users through their individual support tickets. Users who require further assistance with this event are encouraged to contact OutSystems Support by raising a new ticket or following their existing cases through the Support Portal.

Identified: Recovery efforts for the Middle East (UAE) remain ongoing as cloud infrastructure providers work to restore impacted services. ODC organizations remain unavailable while these restoration efforts continue. We are closely tracking the progress and will provide further updates as more information becomes available.

Identified: Recovery efforts for the Middle East (UAE) region remain ongoing as cloud infrastructure providers work to restore impacted services. We continue to track the recovery progress and will provide further updates as more information becomes available.

Identified: Recovery efforts are still underway for the Middle East (UAE) as cloud services work to restore one of the affected areas. We are continuing to track the progress and will provide further updates as more information becomes available.

Identified: We are continuing to monitor the recovery of ODC services in the Middle East (UAE) as the underlying infrastructure issues are being addressed. We will provide further updates as soon as more information becomes available.

Identified: Update - We are continuing to monitor the progress of recovery efforts in the affected region. We will provide further information as soon as more details become available.

Monitoring: Update - We are continuing to monitor the progress of recovery efforts in the affected region. We will provide further information as soon as more details become available.

Identified: Recovery efforts are still being prioritized by AWS for this region, focusing on restoration of the impacted AWS Services. We are closely monitoring the situation and will provide further updates once they become available.

Identified: The cause has been identified as a widespread infrastructure failure in the Middle East (UAE) affecting foundational AWS services. While recovery efforts are underway, ODC and other services in this region will remain unavailable until the underlying infrastructure is fully restored.

We are closely monitoring the situation as it recovers and will provide further information once it becomes available.

Investigating: We are still continuing to monitor the investigation with AWS, as the recovery towards the impaired AWS Middle East (UAE) Region is still ongoing. While there have been significant improvements made so far, the estimated recovery time will take at least another day before power and connectivity can be restored.

Investigating: We continue to follow closely the investigation in partnership with AWS, towards the recovery of the Middle East (UAE) Region. At this point, we are expecting recovery to take at least a day given the significant efforts required. Until then, ODC and other services in this region will continue experiencing a total service outage. We continue to monitor the situation closely and will provide updates as more information becomes available.

Investigating: We are investigating an issue affecting Outsystems Products in the Middle East (UAE) region. This disruption is related to the ongoing AWS service incident reported on March 1st.

Users in this region are currently experiencing a total service outage in ODC, and all services are unavailable. We are monitoring the situation closely and will provide updates as more information becomes available.

Investigating: We are currently investigating this issue.

Monitoring: Our services have been fully restored, and the issue affecting our OutSystems customers has been mitigated. While the ongoing disruption reported by AWS continues, it is not expected to impact our customers at this time. We will continue to closely monitor the situation. If you experience any issues, please contact our Support team.

For updates directly from AWS, please visit: https://health.aws.amazon.com/health/status

Identified: We are continuing to monitor the official AWS status page. At this time, AWS has informed customers that some may experience errors when performing certain network-related actions.

AWS is actively implementing mitigation measures, and recovery is expected within the next few hours.

Identified: AWS Team has identified the cause of the disruption affecting one availability zone in the Middle East (UAE) region. Power was temporarily shut down at the facility as a safety precaution.

Restoration of power and connectivity may take several hours. Other availability zones in the region remain operational.

We will provide further updates as more information becomes available.

Investigating: We are currently experiencing service degradation in the Middle East (UAE) region due to connectivity and power issues within a major cloud provider (AWS).

We are actively monitoring the situation and following updates from the official AWS status page. Our team is closely tracking recovery progress. We will provide further updates as more information becomes available.

Postmortem: 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.

Resolved: 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.

Investigating: 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.

Postmortem: 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.

Resolved: 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.

Investigating: 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.

Postmortem: 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.

Resolved: 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.

Investigating: 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.

Postmortem: 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.

Resolved: 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.

Investigating: 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.

Postmortem: 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.

Resolved: 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.

Investigating: 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.

Postmortem: 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.

Resolved: 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.

Investigating: 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.

Postmortem: 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.

Resolved: 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.

Investigating: 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.