- Level
- confirmed
- Worst impact
- Major outage
- Components
- B2CCore
- Regions
- ods-ap01, ods-eu01, ods-us01, ods-us02, ods-us03, ods-us04
What to do
Check whether you use Salesforce B2CCore in ods-ap01, ods-eu01, ods-us01, ods-us02. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2h 26m it lasted.
Anything that failed between 2026-10-29 09:31 UTC and 2026-10-29 11:57 UTC may need a replay.Subscribe to Salesforce's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=salesforce works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Root cause
We've identified an expired certificate as the cause and are renewing certificates across all affected environments.
Category: Certificate expiry
Read the postmortemUpdates from Salesforce 5
- update
We're aware of an issue impacting Commerce Cloud On-Demand Sandboxes in all regions. Affected sandboxes are stuck in a Starting state, and customers can't access or restart them. We've identified an expired certificate as the cause and are renewing certificates across all affected environments. Once renewal completes, we'll restart all affected sandboxes. We'll provide an update in 30 minutes or sooner if additional information becomes available.
provider
- update
We created a new certificate and this certificate is going through an automated approval process. Once approved, we'll apply it across all affected environments and restart the affected sandboxes. We'll provide an update in 30 minutes or sooner if additional information becomes available.
provider
- update
The system rejected the automated approval for the new certificate due to a missing configuration. We manually approved the request and are now reviewing it before we apply it to the affected environments. Once the review is complete, we'll restart the affected sandboxes. We'll provide an update in 30 minutes or sooner if additional information becomes available.
provider
- update
We're deploying the new certificate to a test environment first, then to the live production environments, and expect each stage to take approximately 30 minutes. Once the certificate is in place, we'll restart the affected sandboxes. We'll provide an update in 30 minutes or sooner if additional information becomes available.
provider
- update
We resolved the issue that left Commerce Cloud On-Demand Sandboxes stuck in a starting state. A new certificate was applied to all affected environments followed by cluster restart. Customers can now access and restart their sandboxes, and we've confirmed that service is restored. We apologise for how this incident 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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-f82c4d81be
Is Salesforce still down?
No, this incident was resolved 2026-10-29 11:57 UTC. For Salesforce's live state, see https://down.guide/salesforce.
How long did it last?
2h 26m, from 2026-10-29 09:31 UTC to 2026-10-29 11:57 UTC, by the times Salesforce posted.
What was affected?
Salesforce named B2CCore in ods-ap01, ods-eu01, ods-us01, ods-us02.
What caused it?
Certificate expiry. Salesforce wrote: "We've identified an expired certificate as the cause and are renewing certificates across all affected environments." The postmortem: https://status.salesforce.com/incidents/20004543
Where does this come from?
Salesforce's official status page, https://status.salesforce.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.