Changes / Salesforce / Service Disruption: Core Service
Salesforce: Critical incident: Service Disruption: Core Service
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
Before: not present
After: Service Disruption: Core Service
Before: not present
After: critical
Before: not present
After: resolved
Before: not present
After: 2026-03-16 15:53 UTC
Before: not present
After: 2026-03-17 06:34 UTC
Before: not present
After: 495 instances, Core Service
Before: not present
After: At 15:53 UTC, on March 16, 2026, we noted a service disruption causing a subset of customers to be unable to log into their environments when attempting to access their services. Customers were out of impact at 06:34 UTC, on March 17, 2026, following the successful rollback of the change that was identified as the trigger for the disruption.
The original Trust Message posting for this issue can be found here: https://status.salesforce.com/incidents/20003819.
We will perform a full investigation of the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.We apologize for how you and your business may have been affected by this incident.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: Service Disruption: Core Service (this change) | Major incident |
All Salesforce changes → · Salesforce profile · Markdown · JSON