OutSystems Status

Postmortem: On August 10th, 2026, from 20:31 to 22:19 UTC, users in the South America / São Paulo region experienced errors when signing in to ODC. This prevented affected users from accessing their Production applications and also affected the ODC Portal and ODC Studio.

The issue was detected through customer reports and monitoring. Our investigation found that a fault in an internal caching component of our identity service was preventing it from issuing sign-in tokens, even though the service otherwise appeared to be running normally.

To restore service, our team restarted the affected identity service, which cleared the fault and allowed token issuance to resume. We confirmed with affected customers that sign-in and application access had returned to normal before closing the incident.

We have identified additional monitoring and preventive improvements for this component and are prioritising their rollout to help reduce the risk of similar issues recurring. We apologise for any disruption caused and thank you for your patience.

Resolved: The incident affecting sign-in and application access in the South America / São Paulo region has been resolved. All services are now fully operational.

Monitoring: A fix has been applied to address the issue affecting sign-in and application access for ODC in the South America / São Paulo region. Initial checks with affected users confirm that sign-in and application access have been restored.

We are now monitoring the platform to ensure full recovery across all affected services, including ODC Studio and the ODC Portal.

Investigating: We are aware of an issue affecting ODC in the South America / São Paulo region. Users may be unable to sign in, and applications in production may be unavailable to end users. Access to ODC Studio and the ODC Portal may also be affected.

Our team is currently investigating the cause and will provide updates as more information becomes available.

Postmortem: On August 12th, 2026, at approximately 02:56 UTC, we received our first customer report regarding an issue that affected the Application Configuration and IP Filter List features, resulting in these areas failing to load for a number of customers. Application publishing and runtime were not affected. Customers saw the error codes OS-APPC-60043 and OS-CFGC-GEN-60030. This prevented some users from completing required application configuration changes. Normal service was restored at 08:00 UTC.

It was caused by a recent update to an internal service that provides configuration data. The update unintentionally changed how requests were routed between instances of that service, so most requests for IP filter information reached an instance that could not answer them and timed out. Our team identified the faulty update and rolled it back across all environments to restore normal behavior.

We are improving our pre-release testing and monitoring so that this type of issue is caught before it reaches production, and adding monitoring coverage specifically for this failure mode.

Resolved: This incident has been resolved. The issue affecting the ODC Portal in the Asia Pacific (Singapore), Europe (Frankfurt), and US East (N. Virginia) regions has been fully addressed, and all services are now operating as expected.

Monitoring: A fix has been implemented to address the configuration issue affecting the ODC Portal in the Asia Pacific (Singapore), Europe (Frankfurt), and US East (Virginia) regions. We are now closely monitoring the platform to ensure application configurations are loading as expected and to confirm that all systems have fully recovered.

Investigating: We continue to investigate the issue affecting ODC in the Asia Pacific (Singapore, Sydney), Europe (Frankfurt), and US East (Virginia) regions. Customers continue to report errors when opening the Configuration tab. Our team is actively working to identify the root cause and will provide updates as more information becomes available.

Investigating: We are aware of an issue affecting ODC in the Asia Pacific (Singapore, Sydney), Europe (Frankfurt), and US East (Virginia) regions. Users impacted may see the application load and then fail when opening the Configuration tab, along with an error message: "Couldn't get IP filter group" (OS-APPC-60043). Our team is actively investigating and will provide updates as more information becomes available.

Postmortem: On August 10th, 2026, from 20:31 to 22:19 UTC, users in the South America / São Paulo region experienced errors when signing in to ODC. This prevented affected users from accessing their Production applications and also affected the ODC Portal and ODC Studio.

The issue was detected through customer reports and monitoring. Our investigation found that a fault in an internal caching component of our identity service was preventing it from issuing sign-in tokens, even though the service otherwise appeared to be running normally.

To restore service, our team restarted the affected identity service, which cleared the fault and allowed token issuance to resume. We confirmed with affected customers that sign-in and application access had returned to normal before closing the incident.

We have identified additional monitoring and preventive improvements for this component and are prioritising their rollout to help reduce the risk of similar issues recurring. We apologise for any disruption caused and thank you for your patience.

Resolved: The incident affecting sign-in and application access in the South America / São Paulo region has been resolved. All services are now fully operational.

Monitoring: A fix has been applied to address the issue affecting sign-in and application access for ODC in the South America / São Paulo region. Initial checks with affected users confirm that sign-in and application access have been restored.

We are now monitoring the platform to ensure full recovery across all affected services, including ODC Studio and the ODC Portal.

Investigating: We are aware of an issue affecting ODC in the South America / São Paulo region. Users may be unable to sign in, and applications in production may be unavailable to end users. Access to ODC Studio and the ODC Portal may also be affected.

Our team is currently investigating the cause and will provide updates as more information becomes available.

Postmortem: On August 12th, 2026, at approximately 02:56 UTC, we received our first customer report regarding an issue that affected the Application Configuration and IP Filter List features, resulting in these areas failing to load for a number of customers. Application publishing and runtime were not affected. Customers saw the error codes OS-APPC-60043 and OS-CFGC-GEN-60030. This prevented some users from completing required application configuration changes. Normal service was restored at 08:00 UTC.

It was caused by a recent update to an internal service that provides configuration data. The update unintentionally changed how requests were routed between instances of that service, so most requests for IP filter information reached an instance that could not answer them and timed out. Our team identified the faulty update and rolled it back across all environments to restore normal behavior.

We are improving our pre-release testing and monitoring so that this type of issue is caught before it reaches production, and adding monitoring coverage specifically for this failure mode.

Resolved: This incident has been resolved. The issue affecting the ODC Portal in the Asia Pacific (Singapore), Europe (Frankfurt), and US East (N. Virginia) regions has been fully addressed, and all services are now operating as expected.

Monitoring: A fix has been implemented to address the configuration issue affecting the ODC Portal in the Asia Pacific (Singapore), Europe (Frankfurt), and US East (Virginia) regions. We are now closely monitoring the platform to ensure application configurations are loading as expected and to confirm that all systems have fully recovered.

Investigating: We continue to investigate the issue affecting ODC in the Asia Pacific (Singapore, Sydney), Europe (Frankfurt), and US East (Virginia) regions. Customers continue to report errors when opening the Configuration tab. Our team is actively working to identify the root cause and will provide updates as more information becomes available.

Investigating: We are aware of an issue affecting ODC in the Asia Pacific (Singapore, Sydney), Europe (Frankfurt), and US East (Virginia) regions. Users impacted may see the application load and then fail when opening the Configuration tab, along with an error message: "Couldn't get IP filter group" (OS-APPC-60043). Our team is actively investigating and will provide updates as more information becomes available.

Postmortem: On August 12th, 2026, at approximately 02:56 UTC, we received our first customer report regarding an issue that affected the Application Configuration and IP Filter List features, resulting in these areas failing to load for a number of customers. Application publishing and runtime were not affected. Customers saw the error codes OS-APPC-60043 and OS-CFGC-GEN-60030. This prevented some users from completing required application configuration changes. Normal service was restored at 08:00 UTC.

It was caused by a recent update to an internal service that provides configuration data. The update unintentionally changed how requests were routed between instances of that service, so most requests for IP filter information reached an instance that could not answer them and timed out. Our team identified the faulty update and rolled it back across all environments to restore normal behavior.

We are improving our pre-release testing and monitoring so that this type of issue is caught before it reaches production, and adding monitoring coverage specifically for this failure mode.

Resolved: This incident has been resolved. The issue affecting the ODC Portal in the Asia Pacific (Singapore), Europe (Frankfurt), and US East (N. Virginia) regions has been fully addressed, and all services are now operating as expected.

Monitoring: A fix has been implemented to address the configuration issue affecting the ODC Portal in the Asia Pacific (Singapore), Europe (Frankfurt), and US East (Virginia) regions. We are now closely monitoring the platform to ensure application configurations are loading as expected and to confirm that all systems have fully recovered.

Investigating: We continue to investigate the issue affecting ODC in the Asia Pacific (Singapore, Sydney), Europe (Frankfurt), and US East (Virginia) regions. Customers continue to report errors when opening the Configuration tab. Our team is actively working to identify the root cause and will provide updates as more information becomes available.

Investigating: We are aware of an issue affecting ODC in the Asia Pacific (Singapore, Sydney), Europe (Frankfurt), and US East (Virginia) regions. Users impacted may see the application load and then fail when opening the Configuration tab, along with an error message: "Couldn't get IP filter group" (OS-APPC-60043). Our team is actively investigating and will provide updates as more information becomes available.

Postmortem: On August 12th, 2026, at approximately 02:56 UTC, we received our first customer report regarding an issue that affected the Application Configuration and IP Filter List features, resulting in these areas failing to load for a number of customers. Application publishing and runtime were not affected. Customers saw the error codes OS-APPC-60043 and OS-CFGC-GEN-60030. This prevented some users from completing required application configuration changes. Normal service was restored at 08:00 UTC.

It was caused by a recent update to an internal service that provides configuration data. The update unintentionally changed how requests were routed between instances of that service, so most requests for IP filter information reached an instance that could not answer them and timed out. Our team identified the faulty update and rolled it back across all environments to restore normal behavior.

We are improving our pre-release testing and monitoring so that this type of issue is caught before it reaches production, and adding monitoring coverage specifically for this failure mode.

Resolved: This incident has been resolved. The issue affecting the ODC Portal in the Asia Pacific (Singapore), Europe (Frankfurt), and US East (N. Virginia) regions has been fully addressed, and all services are now operating as expected.

Monitoring: A fix has been implemented to address the configuration issue affecting the ODC Portal in the Asia Pacific (Singapore), Europe (Frankfurt), and US East (Virginia) regions. We are now closely monitoring the platform to ensure application configurations are loading as expected and to confirm that all systems have fully recovered.

Investigating: We continue to investigate the issue affecting ODC in the Asia Pacific (Singapore, Sydney), Europe (Frankfurt), and US East (Virginia) regions. Customers continue to report errors when opening the Configuration tab. Our team is actively working to identify the root cause and will provide updates as more information becomes available.

Investigating: We are aware of an issue affecting ODC in the Asia Pacific (Singapore, Sydney), Europe (Frankfurt), and US East (Virginia) regions. Users impacted may see the application load and then fail when opening the Configuration tab, along with an error message: "Couldn't get IP filter group" (OS-APPC-60043). Our team is actively investigating and will provide updates as more information becomes available.

Postmortem: On August 10th, 2026, from 20:31 to 22:19 UTC, users in the South America / São Paulo region experienced errors when signing in to ODC. This prevented affected users from accessing their Production applications and also affected the ODC Portal and ODC Studio.

The issue was detected through customer reports and monitoring. Our investigation found that a fault in an internal caching component of our identity service was preventing it from issuing sign-in tokens, even though the service otherwise appeared to be running normally.

To restore service, our team restarted the affected identity service, which cleared the fault and allowed token issuance to resume. We confirmed with affected customers that sign-in and application access had returned to normal before closing the incident.

We have identified additional monitoring and preventive improvements for this component and are prioritising their rollout to help reduce the risk of similar issues recurring. We apologise for any disruption caused and thank you for your patience.

Resolved: The incident affecting sign-in and application access in the South America / São Paulo region has been resolved. All services are now fully operational.

Monitoring: A fix has been applied to address the issue affecting sign-in and application access for ODC in the South America / São Paulo region. Initial checks with affected users confirm that sign-in and application access have been restored.

We are now monitoring the platform to ensure full recovery across all affected services, including ODC Studio and the ODC Portal.

Investigating: We are aware of an issue affecting ODC in the South America / São Paulo region. Users may be unable to sign in, and applications in production may be unavailable to end users. Access to ODC Studio and the ODC Portal may also be affected.

Our team is currently investigating the cause and will provide updates as more information becomes available.

Resolved: This incident has been resolved.

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