# Salesforce: Major incident: B2 B2 CCommerce Service Disruption: B2 CCore

**Summary:** _summary pending_
- Kind: Major incident · Label: outage (model (Jev))
- Changed: 2025-09-06 16:24 UTC · Detected: 2026-10-18 05:11 UTC
- [Source: https://status.salesforce.com/incidents/20003211](https://status.salesforce.com/incidents/20003211)
- [Company: Salesforce](https://rewindex.com/company/salesforce.md)
- Versions: before (none: first archived) → after incident\_version:130/20003211@408b779197d9
- Change 1 of 1 for this incident

Incident page (full timeline): [B2 B2 CCommerce Service Disruption: B2 CCore](https://rewindex.com/company/salesforce/incidents/20003211.md)
## What changed

**1. Added: Title**

```diff
+ B2 B2 CCommerce Service Disruption: B2 CCore
```

**2. Added: Impact**

```diff
+ major
```

**3. Added: Status**

```diff
+ resolved
```

**4. Added: Start time**

```diff
+ 2025-09-06 16:24 UTC
```

**5. Added: Resolved time**

```diff
+ 2025-09-06 20:11 UTC
```

**6. Added: Affected components**

```diff
+ 1 instance, B2 CCore
```

**7. Added: Update** (update) · 2025-09-06 17:38 UTC

```diff
+ 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. Added: Update** (update) · 2025-09-06 17:46 UTC

```diff
+ At 16:24 UTC on September 6, 2025, a service disruption began impacting Commerce Cloud B2C Core. As a result, users may experience issues while accessing storefront sites and the business manager. The Salesforce Technology team is investigating the issue, and an update will be provided in 30 minutes or sooner if we have more information.
```

**9. Added: Update** (investigating) · 2025-09-06 19:01 UTC

```diff
+ We’re investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information.
```

**10. Added: Update** (update) · 2025-09-06 19:46 UTC

```diff
+ We're still actively investigating this issue and appreciate your patience as we work towards a resolution. We do not have any new information to share at this moment, but we will keep you updated as soon as we have more details. We'll provide an update in the next 60 minutes, or sooner if new information becomes available.
```

**11. Added: Update** (resolved) · 2025-09-06 20:16 UTC

```diff
+ The Salesforce Technology team has observed that instance stability and performance are now at expected levels and declared the incident resolved. We will thoroughly investigate the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.
```

## History of this incident

| When (UTC) | Change | Label |
| --- | --- | --- |
| 2025-09-06 16:24 UTC | Major incident: B2 B2 CCommerce Service Disruption: B2 CCore (this change) | outage |

All Salesforce changes: [timeline](https://rewindex.com/company/salesforce/changes.md)
_Diff excerpts are shown on normalized text: dates, counters and tokens appear as ‹date›, ‹count›, ‹tok›; noise-only edits are hidden. Rewindex shows the changed passages, not a copy of the page._


---
Canonical: https://rewindex.com/change/ic1bfddb2379161 · Markdown: https://rewindex.com/change/ic1bfddb2379161.md · JSON: https://rewindex.com/api/v1/changes/ic1bfddb2379161 · Generated 2026-10-18T12:19:05.399Z