Search

Changes / Salesforce / B2 B2 CCommerce Service Disruption: B2 CCore

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

Summary

Summary pending. The diff below shows exactly what changed.

Major incidentLabel: outage (model (Jev), 100%)Changed Detected Source: status.salesforce.com (opens in new tab)

Incident page: full timeline of updates →

What changed

AddedTitle#1
Before: not present
After: B2 B2 CCommerce Service Disruption: B2 CCore
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-02-04 21:20 UTC
AddedResolved time#5
Before: not present
After: 2026-02-04 21:30 UTC
AddedAffected components#6
Before: not present
After: 1 instance, B2 CCore
AddedUpdateupdate#7
Before: not present
After: On 4-Feb-2026, a limited number of customers may have experienced a service disruption on pod349. During impact, customers would not have been able to access storefronts or place orders. The Salesforce Technical team resolved the issue, and will investigate solutions to prevent a reoccurrence in the future.
AddedUpdateupdate#8
Before: not present
After: Update

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

History of this incident

When (UTC)ChangeKind
Major incident: B2 B2 CCommerce Service Disruption: B2 CCore (this change)Major incident

All Salesforce changes → · Salesforce profile · Markdown · JSON