Episerver incident

Configured Commerce - Mission Control service degredation

Resolved after 2 days 21 hours, affecting Configured Commerce - Mission Control, on November 13, 2026.

resolved Nov 16, 2026, 03:11 PM UTC

The Mission Control service degradation has been resolved, but two longer-term disruptions remain in place. Ongoing disruptions: - Database credentials remain disabled. The “Generate Database Credentials” action in Mission Control will stay disabled. If you need access to a database, use the Database Backup action to download a copy and review it. See the following URL: https://docs.optimizely.com/configured-commerce/mission-control/database-backup. Log a support ticket with Optimizely Support if additional assistance is needed. - Build Service v1 will not be fixed. v1 builds and deployments remain non-operational. The v1 build service reached end of life on September 30, 2026, and will not receive a fix. Customers must move to build service v2 to restore builds and deployments. See the following URL for the Build service v2: Upgrade existing instances: https://docs.optimizely.com/configured-commerce/docs/build-service-v2#upgrade-existing-instances All other Mission Control actions, including build service v2 builds and deployments, are fully operational.

Started
Nov 13, 2026, 05:19 PM UTC
Resolved
Nov 16, 2026, 03:11 PM UTC
Duration
2d 21h
Detected by Pingoru
Nov 13, 2026, 05:19 PM UTC

Affected components

Configured Commerce - Mission Control

Update timeline

  1. investigating Nov 13, 2026, 05:19 PM UTC

    Mission Control and the v1 Build Service are currently experiencing degraded performance due to an ongoing incident. Some Mission Control actions may fail, and all builds/deployments for customers using the v1 build service will fail. Action required for v1 build service customers If you are on the v1 build service, you must upgrade to v2 to continue processing builds and deployments. The v1 build service reached end of life on September 30, 2026, so it will not receive a fix for this incident. Upgrading to v2 is the way to restore your builds and deployments. See Build service v2: Upgrade existing instances for steps: https://docs.optimizely.com/configured-commerce/docs/build-service-v2#upgrade-existing-instances

  2. identified Nov 13, 2026, 09:56 PM UTC

    Efforts remains ongoing to restore full functionality to the service. - The "Generate Database Credentials" action in Mission Control is not operational and we are looking into remediation - Configured Commerce Build Service v1 builds and deployments are not operational; customers must move to build service v2 to remediate All other Mission Control actions, including build service v2 builds and deployments are operational

  3. resolved Nov 16, 2026, 03:11 PM UTC

    The Mission Control service degradation has been resolved, but two longer-term disruptions remain in place. Ongoing disruptions: - Database credentials remain disabled. The “Generate Database Credentials” action in Mission Control will stay disabled. If you need access to a database, use the Database Backup action to download a copy and review it. See the following URL: https://docs.optimizely.com/configured-commerce/mission-control/database-backup. Log a support ticket with Optimizely Support if additional assistance is needed. - Build Service v1 will not be fixed. v1 builds and deployments remain non-operational. The v1 build service reached end of life on September 30, 2026, and will not receive a fix. Customers must move to build service v2 to restore builds and deployments. See the following URL for the Build service v2: Upgrade existing instances: https://docs.optimizely.com/configured-commerce/docs/build-service-v2#upgrade-existing-instances All other Mission Control actions, including build service v2 builds and deployments, are fully operational.

Your product runs on more than Episerver

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →