Salesforce: Feature Service Disruption: Core Service
Affected components: Core Service21 instances
Timeline of updates
- update
The fix roll out has completed and the issue is resolved. Previous notifications regarding this issue via a broader trust posting here: https://status.salesforce.com/incidents/20003860 (opens in new tab). We've removed this instance from the broader post, and have created this specific post to provide the accurate impact end time for your instance.
We'll perform a full investigation into this incident to confirm the technical trigger and implement preventive measures to avoid a recurrence. We apologize for the impact this has had on you and your business.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-18 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
0851b6933cf67148…
Impact, status and times are the vendor’s own, as last archived. View on status.salesforce.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Salesforce, started 2026-03-23 00:00 UTC, resolved after 3 d, 1 update(s).
- Title
- Feature Service Disruption: Core Service
- Vendor
- Salesforce
- Date
- URL
- https://rewindex.com/company/salesforce/incidents/20003878
Salesforce profileRecent Salesforce incidentsAll outages on March 23, 2026Salesforce in March 2026MarkdownJSON