# Salesforce: Service Disruption: B2 CCore - Impact (vendor’s label): critical - Status: resolved - Started: 2025-11-18 10:20 UTC · Resolved: 2025-11-18 15:00 UTC · Duration: 4.7 h - Updates: 6 · Affected components: B2 CCore, 153 instances - [Vendor status page: https://status.salesforce.com/incidents/20003465](https://status.salesforce.com/incidents/20003465) - [Company: Salesforce](https://rewindex.com/company/salesforce.md) ## Timeline of updates - **update** 2025-11-18 12:44 UTC: A subset of customers is currently experiencing a service disruption affecting Storefront services. Customers and their end users may encounter HTTP 500 errors when accessing online stores or attempting to complete transactions. Initial investigations indicate that Commerce Cloud platform systems are operating normally. The issue appears to be related to connectivity disruption with our third-party Content Delivery Network (CDN) provider. We are actively engaged and collaborating with the CDN provider to restore full functionality. We will provide an update in 30 minutes, or sooner if additional information becomes available. - **update** 2025-11-18 13:16 UTC: Further investigation indicates that the impact is intermittent, with periods of recovery followed by brief service interruptions. We have verified that the Salesforce platform and network systems are operating normally, and the connectivity issues do not originate from our infrastructure. In parallel, we are reviewing additional network-related factors that may be contributing to the disruption and are working closely with our third-party Content Delivery Network (CDN) provider to identify the root cause and restore full service. We will provide the next update within 30 minutes, or sooner if additional information becomes available. - **update** 2025-11-18 13:44 UTC: Further investigation has confirmed an earlier start time for the impact, now identified as 11:29 UTC, based on aligned metrics from both Salesforce monitoring and our third-party Content Delivery Network (CDN). The Content Delivery Network (CDN) provider has identified a configuration issue and is actively deploying a fix. We are beginning to see early signs of recovery for some PODs, but the impact remains intermittent, and our teams continue to monitor closely. We will provide the next update within 60 minutes, or sooner if additional information becomes available. - **update** 2025-11-18 14:25 UTC: We continue to see improvements in service recovery. The Content Delivery Network (CDN) provider has implemented recovery steps for some of its services, and we are collaborating on a traffic redirection strategy to direct affected customer domains to functioning network locations. For customers opening support cases related to this issue, please include all affected domain names to assist with our remediation efforts. We will provide the next update within 60 minutes, or sooner if additional information becomes available. - **update** 2025-11-18 14:51 UTC: Our Content Delivery Network (CDN) provider has identified the trigger as an issue introduced during a recent configuration update They are performing a rollback to the last known stable working configuration. We have also provided them with a prioritised list of affected customer domains to expedite traffic rerouting to functioning edge locations. Some customers may now be able to access their Storefronts, though a small subset of customers may still experience intermittent issues until the rollback is complete. We will provide the next update within 60 minutes, or sooner if additional information becomes available. - **update** 2025-11-18 15:42 UTC: The incident affecting Commerce Cloud Storefronts has now been successfully resolved at 15:00 UTC. Customer Storefronts are now fully operational and transacting normally. Our Content Delivery Network (CDN) provider completed the rollback to a stable working configuration, monitored the performance for a brief period, and confirmed restoration of services. Additionally, further investigations have now highlighted an earlier start time for the impact, now identified as 10:20 UTC We apologize for how this incident affected you and your business. We will conduct a thorough investigation of the incident, identifying the technical trigger and the underlying cause, and implementing preventive actions to prevent recurrence in the future. ## Rewindex changes for this incident - 2025-11-18 10:20 UTC: [Critical incident: Service Disruption: B2 CCore](https://rewindex.com/change/i16a0443d680d20.md) --- Canonical: https://rewindex.com/company/salesforce/incidents/20003465 · Markdown: https://rewindex.com/company/salesforce/incidents/20003465.md · JSON: https://rewindex.com/api/v1/companies/salesforce/incidents/20003465 · Generated 2026-10-18T11:26:56.151Z