Companies / Salesforce / incidents

Salesforce: Cc Storefront SAnd Or Business Manager Unavailable: B2 CCore

Impact: majorStatus: resolvedStarted Resolved (3.4 h)7 updatesSource: status.salesforce.com (opens in new tab)

Affected components: B2 CCore34 instances

Timeline of updates

  1. update

    We are aware of a service disruption that began impacting B2C Commerce Cloud. As a result, customers may be unable to access their Commerce Cloud Storefronts and services. We're actively working to restore full service availability. We'll provide an update in 30 minutes or sooner if additional information becomes available.

  2. update

    We've identified an infrastructure configuration issue impacting a subset of our PODs. We are actively working to restore affected services. We're currently validating our recovery approach on a subset of environments before applying the fix more broadly. We'll provide an update in 30 minutes or sooner if additional information becomes available.

  3. update

    We're continuing to make progress in restoring services. Infrastructure configuration issue prevented a subset of PODs from completing a planned update, which caused those PODs to enter an unhealthy state. We’ve successfully restored a subset of affected PODs and are actively working through the remaining impacted PODs. We're executing the restoration process in parallel to bring all affected services back online as quickly as possible. We'll provide an update in 60 minutes or sooner if additional information becomes available.

  4. update

    We are continuing to make progress in restoring services. We have successfully restored services on a subset of PODs, and we're actively working through the remaining impacted environments. We are executing the restoration process in parallel to bring all affected services back online as quickly as possible. As PODs are restored, we are publishing individual Trust posts for each instance to accurately capture the service restoration time. Customers on restored instances should refer to their instance-specific post for the end time of this disruption and confirmation that services have been restored. We'll provide an update in 60 minutes or sooner if additional information becomes available.

  5. update

    We have completed the restoration of services across all affected B2C Commerce Cloud PODs. Our teams are continuing to monitor the environments to confirm full stability. Additionally, we want to make customers aware that as a result of this incident, some instances may not have been updated to the latest planned software release version. Reschedule information for the release update will be provided as soon as feasible. Customers who notice they remain on the previous version should expect to receive further communication with updated timings. We apologize for how this incident may have affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.

  6. update

    We have completed the restoration of services across all affected B2C Commerce Cloud PODs. Our teams are continuing to monitor the environments to confirm full stability. Additionally, we want to make customers aware that because of this incident, some PODs may not have been updated to the latest planned software release version. Reschedule information for the release update will be provided as soon as feasible. Customers who notice they remain on the previous version should expect to receive further communication with updated timings. We apologize for how this incident may have affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.

  7. update

    We have completed the restoration of services across all affected PODs and are actively monitoring all environments to confirm continued stability. At 03:43 UTC on June 18, 2026, full service was restored across all impacted PODs following a manual, phased recovery process executed . Due to this incident, some PODs may not have completed the planned software release update. We'll provide rescheduling details once they are confirmed. Customers on earlier versions will receive a separate communication with updated timelines. We apologize for the disruption and any impact to your business operations. We will conduct a full investigation to identify the technical trigger, understand the root cause, and implement preventive actions to prevent recurrence.

Rewindex changes for this incident

Impact, status and times are the vendor’s own, as last archived. View on status.salesforce.com (opens in new tab). Salesforce profile · Recent Salesforce incidents · Markdown · JSON