# Salesforce: Service Disruption: B2 CCore - Impact (vendor’s label): major - Status: resolved - Started: 2026-04-27 10:57 UTC · Resolved: 2026-04-27 15:35 UTC · Duration: 4.6 h - Updates: 10 · Affected components: B2 CCore, 12 instances - [Vendor status page: https://status.salesforce.com/incidents/20003968](https://status.salesforce.com/incidents/20003968) - [Company: Salesforce](https://rewindex.com/company/salesforce.md) ## Timeline of updates - **update** 2026-04-27 11:41 UTC: Investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward. - **update** 2026-04-27 11:53 UTC: We're investigating a widespread service disruption impacting Commerce Cloud and Core Services in the France region. Customers are currently experiencing a full disruption and are unable to log in to or access their services. Initial investigations show that the issue is due to a power failure in the data center. We'll provide an update in 30 minutes or sooner if additional information becomes available. - **update** 2026-04-27 12:05 UTC: Investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward. - **update** 2026-04-27 12:41 UTC: We continue to investigate an issue impacting customers using Commerce Cloud and Core services in our France-based infrastructure. Network connectivity began restoring at 11:22 UTC following a power event at our data center. While network links have come back online, services remain in recovery. We'll provide an update in 30 minutes or sooner if additional information becomes available. - **update** 2026-04-27 13:11 UTC: All Core services are recovered and available as of approximately 11:45 UTC. These instances will now be removed from this posting and will receive their own dedicated posting for this incident. Monitoring for recovery of Commerce Cloud services is still ongoing. We'll provide an update in 30 minutes or sooner if additional information becomes available. - **update** 2026-04-27 13:40 UTC: We continue to work to fully restore Commerce Cloud services following the power issue at our data center in France. The majority of PODs are fully back online and under monitoring, and we're restarting services on PODs 248, 258 and 356 as they're still experiencing some latent impact. We'll provide an update in 30 minutes or sooner if additional information becomes available. - **update** 2026-04-27 14:46 UTC: We've determined that a site-switch for PODs 248, 258, and 356 is the most appropriate action to get customers out of impact and we're proceeding with this action now. All other PODs remain out of impact. We'll provide an update in 30 minutes or sooner if additional information becomes available. - **update** 2026-04-27 15:31 UTC: We have determined that restarting services in place is the most effective path to resolution, and we are proceeding with this action now. A site-switch was not performed as we are resolving the issue through these in-place restarts. During this process, customers will see services begin to return in a staggered phase, often before the full restart is complete. The current status of the remaining instances is as follows: PODs 313 and 356: These instances have been confirmed as restored and are under monitoring. POD 248: The restart is currently in progress. Customers may begin to see service recovery on this instance shortly.All other PODs remain stable. We’ll provide an update in 30 minutes or sooner if additional information becomes available. - **update** 2026-04-27 15:49 UTC: We have confirmed that service has been restored for all remaining instances as of 15:35 UTC. Following the successful completion of in-place restarts, monitoring confirms that performance has normalized across the region. We apologize for how you and your business may have been affected by this incident. We will thoroughly investigate the incident, confirming the technical trigger, the underlying cause, and preventive actions to avoid a recurrence. - **update** 2026-04-27 16:04 UTC: Upon further investigation, we've determined that the start time of impact is different than initially understood. We've 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. ## Rewindex changes for this incident - 2026-04-27 10:57 UTC: [Major incident: Service Disruption: B2 CCore](https://rewindex.com/change/ica48206e9def5e.md) --- Canonical: https://rewindex.com/company/salesforce/incidents/20003968 · Markdown: https://rewindex.com/company/salesforce/incidents/20003968.md · JSON: https://rewindex.com/api/v1/companies/salesforce/incidents/20003968 · Generated 2026-10-18T11:26:49.652Z