Performance Degradation

Storefronts are no longer in impact. Non-disruptive rolling restarts continue to complete the revert of the runtime environment to the previous version. Granular Data Replication remains temporarily unavailable, this will be re-enabled after validation of restart completion.

We will provide an update once the restarts are complete, or sooner if additional information becomes available.

Storefronts were confirmed out of impact at 13:41 UTC. Granular Data Replication remains temporarily unavailable. Non-disruptive rolling restarts are now in progress on affected PODs to complete the revert of the runtime environment to the previous version.

We'll provide an update in 30 minutes or sooner if additional information becomes available.

We’re reverting the runtime environment to its previous version across all impacted PODs via a fix that is estimated to take 45 minutes to complete, which will be followed by a non-disruptive rolling restart. As a temporary measure, we have proactively disabled the Granular Data Replication feature to reduce further Storefront impact for affected customers

We'll provide our next update in 30 minutes, or sooner if new information becomes available.

The cause has been identified as a behavior change introduced by a recent runtime upgrade. To reduce further impact, we've disabled a replication feature for affected customers., We're now preparing a fix to revert the runtime environment to its previous version, which will take approximately 90 minutes to deploy and will be followed by a non-disruptive rolling restart across the impacted PODs.

We'll provide an update in 30 minutes, or sooner if new information becomes available.

We're aware of an issue impacting Commerce Cloud customers on some pods. As a result, customers are experiencing intermittent Storefront unavailability, with sites going down for periods ranging from 30 minutes to an hour. We've deactivated a replication feature on impacted pods as an interim measure to reduce further Storefront impact. We're also working to revert the runtime environment on impacted pods back to a previous version, and have begun updating pod configuration files and restarting application servers to validate this change.

We'll provide an update in 30 minutes or sooner if additional information becomes available.