Issue Affecting Application Configuration in ODC Portal

Update timeline

1. investigating Aug 12, 2026, 05:41 AM UTC

   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.

2. investigating Aug 12, 2026, 07:37 AM UTC

   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.

3. monitoring Aug 12, 2026, 08:30 AM UTC

   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.

4. resolved Aug 12, 2026, 10:38 AM UTC

   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.

5. postmortem Aug 13, 2026, 10:58 AM UTC

   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.