Companies / Salesforce / incidents

Salesforce: C Storefront SAnd Or Business Manager Impacted: B2 CCore

Impact: minorStatus: resolvedStarted Resolved (13 h)9 updatesSource: status.salesforce.com (opens in new tab)

Affected components: B2 CCore20 instances

Timeline of updates

  1. update

    A subset of customers are experiencing slowness in Business Manager and Storefront performance. Initial investigations indicate that Commerce Cloud systems are performing normally, and the issue appears to be related to content delivery affecting page load times. We are actively investigating the issue to identify the cause and restore normal performance. 
 We appreciate your patience and will provide the next update within 30 minutes or sooner as more information becomes available.

  2. update

    We continue to investigate, and our ongoing analysis suggests the issue may be linked to how some parts of the site are loading through an external network service. We are working closely with the third-party network provider to validate this assessment.
 We’ve also identified that the impact is broader than initially understood. We’ve updated the posting to include additional impacted PODs, and customers in those PODs will receive related communications. We will share an update within 30 minutes or sooner as more information becomes available.

  3. update

    We have confirmed that the Salesforce system and network are performing as expected, and the slowness is not originating from our infrastructure. We are now focusing on other network-related factors that may be contributing to the issue, and continue to work closely with the third-party network provider resource to identify the cause. We will share the next update within 30 minutes or sooner as more information becomes available.

  4. update

    Investigations have highlighted that the impact radius is narrower than initially understood. We will now remove POD268, which has not experienced any impact, and this will no longer receive communications about this incident going forward. Impacted instances will continue to be updated. We apologize for any inconvenience caused.

  5. update

    Salesforce systems remain stable, and we are working closely with the third-party network provider to restore normal performance.
While we do not have a significant update at this time, current findings continue to indicate that the slowness is still linked to a third-party network service.
 We will share the next update within 60 minutes or sooner as more information becomes available.

  6. update

    We continue to work with the third-party network provider to restore normal performance.
 We’ve also identified that the impact is broader than initially understood. We’ve updated the posting to include additional impacted PODs, and customers in those PODs will receive related communications. We will provide an update in 60 minutes or sooner if additional information becomes available.

  7. update

    Upon further investigation, the Salesforce Technology team has determined that the start time of impact is different than initially understood. We have now revised the start time of the Trust post to more accurately reflect the time customers may have begun to experience impact. We apologize for any confusion caused by this.

  8. update

    Salesforce systems remain stable.
Some customers are seeing improvements; however, the issue seems to be intermittent. We are working closely with the third-party network provider to restore services. We will provide an update in 60 minutes or sooner if additional information becomes available.

  9. update

    After monitoring performance and completing health checks, the team confirmed that services were restored as of 14:26 UTC, following the implementation of a routing change by the third-party network provider. We will perform a full investigation of the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a recurrence in the future. We apologize for how you and your business may have been affected by 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