Salesforce: Performance Degradation: Core Service
Affected components: Core Service3 instances
Timeline of updates
- update
At 22:00 UTC on September 23, 2025, we observed a performance degradation affecting a subset of customers with the Omni Studio “Salesforce Industries” managed package installed, resulting in limited access to certain features. A fix forward was deployed to impacted sandbox instances, and as of 12:10 UTC, the AUS18S, AUS22S and AUS26S sandbox instances have been out of impact.
This post follows delayed confirmation that these sandbox instances were impacted by a broader incident. For a detailed timeline and information on this incident, please refer to the Trust post: http://sfdc.co/P4KwY (opens in new tab)
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
877753a7af1b002b…
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 2025-09-23 22:00 UTC, resolved after 38 h, 1 update(s).
- Title
- Performance Degradation: Core Service
- Vendor
- Salesforce
- Date
- URL
- https://rewindex.com/company/salesforce/incidents/20003272
Salesforce profileRecent Salesforce incidentsAll outages on September 23, 2025Salesforce in September 2025MarkdownJSON